CVE-2025-40205btrfs: avoid potential out-of-bounds in btrfs_encode_fh()
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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/4CADAEEC020000780001B32C@vpn.id2.novell.com/ 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.
- CVSS
- 7.8 HIGH (v3.1, CNA)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Deferred
- Record last updated
- Oct 15, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from be6e8dc0ba84029997075a1ec77b4ddb863cbe15 before 60de2f55d2aca53e81b4ef2a67d7cc9e1eb677db; from be6e8dc0ba84029997075a1ec77b4ddb863cbe15 before 742b44342204e5dfe3926433823623c1a0c581df; from be6e8dc0ba84029997075a1ec77b4ddb863cbe15 before d3a9a8e1275eb9b87f006b5562a287aea3f6885f; from be6e8dc0ba84029997075a1ec77b4ddb863cbe15 before d91f6626133698362bba08fbc04bd72c466806d3; from be6e8dc0ba84029997075a1ec77b4ddb863cbe15 before 0276c8582488022f057b4cec21975a5edf079f47; from be6e8dc0ba84029997075a1ec77b4ddb863cbe15 before 361d67276eb8ec6be8f27f4ad6c6090459438fee; from be6e8dc0ba84029997075a1ec77b4ddb863cbe15 before 43143776b0a7604d873d1a6f3e552a00aa930224; from be6e8dc0ba84029997075a1ec77b4ddb863cbe15 before dff4f9ff5d7f289e4545cc936362e01ed3252742 | CNA record |
References
- https://git.kernel.org/stable/c/60de2f55d2aca53e81b4ef2a67d7cc9e1eb677db
- https://git.kernel.org/stable/c/742b44342204e5dfe3926433823623c1a0c581df
- https://git.kernel.org/stable/c/d3a9a8e1275eb9b87f006b5562a287aea3f6885f
- https://git.kernel.org/stable/c/d91f6626133698362bba08fbc04bd72c466806d3
- https://git.kernel.org/stable/c/0276c8582488022f057b4cec21975a5edf079f47
- https://git.kernel.org/stable/c/361d67276eb8ec6be8f27f4ad6c6090459438fee
- https://git.kernel.org/stable/c/43143776b0a7604d873d1a6f3e552a00aa930224
- https://git.kernel.org/stable/c/dff4f9ff5d7f289e4545cc936362e01ed3252742
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.