CVE-2025-40205

btrfs: avoid potential out-of-bounds in btrfs_encode_fh()

HIGH
7.8
CVSS Score
Published: November 12, 2025 at 09:56 PM UTC
Updated: October 19, 2026 at 09:10 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: btrfs: avoid potential out-of-bounds in btrfs_encode_fh() The function btrfs_encode_fh() does not properly account for the three cases it handles. Before writing to the file handle (fh), the function only returns to the user BTRFS_FID_SIZE_NON_CONNECTABLE (5 dwords, 20 bytes) or BTRFS_FID_SIZE_CONNECTABLE (8 dwords, 32 bytes). However, when a parent exists and the root ID of the parent and the inode are different, the function writes BTRFS_FID_SIZE_CONNECTABLE_ROOT (10 dwords, 40 bytes). If *max_len is not large enough, this write goes out of bounds because BTRFS_FID_SIZE_CONNECTABLE_ROOT is greater than BTRFS_FID_SIZE_CONNECTABLE originally returned. This results in an 8-byte out-of-bounds write at fid->parent_root_objectid = parent_root_id. A previous attempt to fix this issue was made but was lost. https://lore.kernel.org/all/[email protected]/ Although this issue does not seem to be easily triggerable, it is a potential memory corruption bug that should be fixed. This patch resolves the issue by ensuring the function returns the appropriate size for all three cases and validates that *max_len is large enough before writing any data.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.29be6e8dc0ba84029997075a1ec77b4ddb863cbe15
Vendor states this is fixed in 0276c8582488022f057b4cec21975a5edf079f47 (fixed)
Vendor states this is fixed in 361d67276eb8ec6be8f27f4ad6c6090459438fee (fixed)
Vendor states this is fixed in 43143776b0a7604d873d1a6f3e552a00aa930224 (fixed)
Vendor states this is fixed in 60de2f55d2aca53e81b4ef2a67d7cc9e1eb677db (fixed)
Vendor states this is fixed in 742b44342204e5dfe3926433823623c1a0c581df (fixed)
Vendor states this is fixed in d3a9a8e1275eb9b87f006b5562a287aea3f6885f (fixed)
Vendor states this is fixed in d91f6626133698362bba08fbc04bd72c466806d3 (fixed)
Vendor states this is fixed in dff4f9ff5d7f289e4545cc936362e01ed3252742 (fixed)
Vendor states this is fixed in 2.6.29 (unaffected)
Vendor states this is fixed in 5.10.246 (unaffected)
Vendor states this is fixed in 5.15.195 (unaffected)
Vendor states this is fixed in 5.4.301 (unaffected)
Vendor states this is fixed in 6.1.157 (unaffected)
Vendor states this is fixed in 6.12.54 (unaffected)
Vendor states this is fixed in 6.17.4 (unaffected)
Vendor states this is fixed in 6.18 (unaffected)
Vendor states this is fixed in 6.6.113 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card