Vulnerability · CVE-2026-97415
btrfs: tree-checker: validate names in ROOT_REF and ROOT_BACKREF
Published Sep 24, 2026 · catalog updated Nov 4, 2026 · btrfs: tree-checker: validate names
Last checked Nov 7, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2026-97415. EPSS is 0.13%. Act only if a listed version of btrfs: tree-checker: validate names is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (btrfs: tree-checker: validate names).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- High7.8
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.13%
- Remediation
- Advisory link
- Affected products
- Linux Kernel
In the Linux kernel, the following vulnerability has been resolved: btrfs: tree-checker: validate names in ROOT_REF and ROOT_BACKREF ROOT_REF and ROOT_BACKREF items contain a struct btrfs_root_ref followed by the subvolume name. Several readers assume that this layout is already valid and then use the on-disk name length directly. A corrupted item can therefore make those readers address bytes outside the item, and BTRFS_IOC_GET_SUBVOL_INFO can copy too many bytes into its fixed-size UAPI name buffer. Validate ROOT_REF and ROOT_BACKREF items in tree-checker before any reader uses them. Reject records that do not contain a non-empty name, whose name_len does not exactly describe the remaining item payload, or whose name exceeds BTRFS_NAME_LEN. For BTRFS_IOC_GET_SUBVOL_INFO, copy only the validated on-disk name_len instead of deriving the copy length from the item size. The ioctl result is zeroed when allocated. That leaves the existing trailing zero byte untouched.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- Linux Kernel4.18.0 → 6.1.189; 6.2.0 → 6.6.158; 6.7.0 → 6.12.111
How to fix CVE-2026-97415
Upgrade
CVE-2026-97415 lists a fix boundary at 6.1.189. Compare the installed build with that boundary before you change production.
Version check
Seen in 4.18.0 → 6.1.189; 6.2.0 → 6.6.158; 6.7.0 → 6.12.111
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2026-97415. EPSS is 0.13%. Act only if a listed version of btrfs: tree-checker: validate names is installed.
Which versions are affected?
Compare what you have installed with Kernel 4.18.0 → 6.1.189; 6.2.0 → 6.6.158; 6.7.0 → 6.12.111. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS 0.13%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Sep 24, 2026 · OpenSSF OSV / OSV Scanner
Detected
In the Linux kernel, the following vulnerability has been resolved: btrfs: tree-checker: validate names in ROOT_REF and ROOT_BACKREF ROOT_REF and ROOT_BACKREF items contain a struct btrfs_root_ref followed by the subvolume name. Several readers assume that this layout is already valid and then use the on-disk name length directly. A corrupted item can therefore make those readers address bytes out
Nov 4, 2026 · OpenSSF OSV / OSV Scanner
Fix available
Kernel fixed in 6.1.189; Kernel fixed in 6.6.158; Kernel fixed in 6.12.111; Kernel fixed in 6.18.53
Nov 4, 2026 · OpenSSF OSV / OSV Scanner
Fix available
Kernel fixed in 6.1.189; 6.2.0
Nov 4, 2026 · OpenSSF OSV / OSV Scanner
Updated
In the Linux kernel, the following vulnerability has been resolved: btrfs: tree-checker: validate names in ROOT_REF and ROOT_BACKREF ROOT_REF and ROOT_BACKREF items contain a struct btrfs_root_ref followed by the subvolume name. Several readers assume that this layout is already valid and then use the on-disk name length directly. A corrupted item can therefore make those readers address bytes out
Sources
- CVE.orgVulnerability recordCVE-2026-97415
Official CVE identifier
cve.org - OpenSSF OSV / OSV ScannerPackage advisoryCVE-2026-97415
btrfs: tree-checker: validate names in ROOT_REF and ROOT_BACKREF
osv.dev
References
Freshness
Last verified in this catalog Nov 7, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- CVE.orgNov 4, 2026
- OpenSSF OSV / OSV ScannerNov 4, 2026