Linux Kernel up to 6.5.4 btrfs lookup_inline_extent_backref information disclosure

Summaryinfo

A vulnerability was found in Linux Kernel up to 6.5.4. It has been declared as critical. This affects the function lookup_inline_extent_backref of the component btrfs. The manipulation results in information disclosure. This vulnerability is reported as CVE-2023-53672. The attack requires a local approach. No exploit exists. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as problematic, was found in Linux Kernel up to 6.5.4. Affected is the function lookup_inline_extent_backref of the component btrfs. The manipulation with an unknown input leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality. CVE summarizes:

In the Linux kernel, the following vulnerability has been resolved: btrfs: output extra debug info if we failed to find an inline backref [BUG] Syzbot reported several warning triggered inside lookup_inline_extent_backref(). [CAUSE] As usual, the reproducer doesn't reliably trigger locally here, but at least we know the WARN_ON() is triggered when an inline backref can not be found, and it can only be triggered when @insert is true. (I.e. inserting a new inline backref, which means the backref should already exist) [ENHANCEMENT] After the WARN_ON(), dump all the parameters and the extent tree leaf to help debug.

The advisory is available at git.kernel.org. This vulnerability is traded as CVE-2023-53672 since 10/07/2025. The exploitability is told to be easy. Local access is required to approach this attack. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1592 by the MITRE ATT&CK project.

Upgrading to version 4.14.326, 4.19.295, 5.4.257, 5.10.197, 5.15.133, 6.1.55 or 6.5.5 eliminates this vulnerability. Applying the patch 376b41524b71e494514720bd6114325b0a2ed19c/400e08a16604b534fdd82c5a288fa150d04f5f79/7afbfde45d665953b4d5a42a721e15bf0315d89b/b7c3cf2f6c42e6688b1c37215a0b1663f982f915/6994f806c6d1ae8b59344d3700358547f3b3fe1d/28062cd6eda04035d8f6ded2001292ac8b496149/e70ba449b04b40584bdabb383d10455397cbf177/7f72f50547b7af4ddf985b07fc56600a4deba281 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at EUVD (EUVD-2025-31943) and CERT Bund (WID-SEC-2025-2229). If you want to get best quality of vulnerability data, you may have to visit VulDB.

Affected

• Amazon Linux 2
• Red Hat Enterprise Linux
• SUSE Linux
• Oracle Linux
• RESF Rocky Linux
• Open Source Linux Kernel
• IBM QRadar SIEM
• Dell NetWorker

Productinfo

Type

• Operating System

Vendor

• Linux

Name

• Kernel

Version

• 4.14.325
• 4.19.294
• 5.4.256
• 5.10.196
• 5.15.132
• 6.1.0
• 6.1.1
• 6.1.2
• 6.1.3
• 6.1.4
• 6.1.5
• 6.1.6
• 6.1.7
• 6.1.8
• 6.1.9
• 6.1.10
• 6.1.11
• 6.1.12
• 6.1.13
• 6.1.14
• 6.1.15
• 6.1.16
• 6.1.17
• 6.1.18
• 6.1.19
• 6.1.20
• 6.1.21
• 6.1.22
• 6.1.23
• 6.1.24
• 6.1.25
• 6.1.26
• 6.1.27
• 6.1.28
• 6.1.29
• 6.1.30
• 6.1.31
• 6.1.32
• 6.1.33
• 6.1.34
• 6.1.35
• 6.1.36
• 6.1.37
• 6.1.38
• 6.1.39
• 6.1.40
• 6.1.41
• 6.1.42
• 6.1.43
• 6.1.44
• 6.1.45
• 6.1.46
• 6.1.47
• 6.1.48
• 6.1.49
• 6.1.50
• 6.1.51
• 6.1.52
• 6.1.53
• 6.1.54
• 6.5.0
• 6.5.1
• 6.5.2
• 6.5.3
• 6.5.4

License

• open-source

Website

• Vendor: https://www.kernel.org/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion