CVE-2025-40205High· 7.8▾ TwilightIn 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 t…
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 42.9 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake. The CVSS score shown above comes from the assigning CNA record, not NVD.
Exploit-prediction probability, daily snapshots since Oct 15.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
Last analysed / modified upstream
0.2%
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.
Linux >= be6e8dc0ba84029997075a1ec77b4ddb863cbe15 < 60de2f55d2aca53e81b4ef2a67d7cc9e1eb677dbLinux >= be6e8dc0ba84029997075a1ec77b4ddb863cbe15 < 742b44342204e5dfe3926433823623c1a0c581dfLinux >= be6e8dc0ba84029997075a1ec77b4ddb863cbe15 < d3a9a8e1275eb9b87f006b5562a287aea3f6885fLinux >= be6e8dc0ba84029997075a1ec77b4ddb863cbe15 < d91f6626133698362bba08fbc04bd72c466806d3Linux >= be6e8dc0ba84029997075a1ec77b4ddb863cbe15 < 0276c8582488022f057b4cec21975a5edf079f47Linux >= be6e8dc0ba84029997075a1ec77b4ddb863cbe15 < 361d67276eb8ec6be8f27f4ad6c6090459438feeLinux >= be6e8dc0ba84029997075a1ec77b4ddb863cbe15 < 43143776b0a7604d873d1a6f3e552a00aa930224Linux >= be6e8dc0ba84029997075a1ec77b4ddb863cbe15 < dff4f9ff5d7f289e4545cc936362e01ed3252742Linux 2.6.29Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-99118Nonedrm/i915/dmc: Harden DMC firmware payload parsing
CVE-2026-99117Nonenet: bridge: mcast: don't truncate the port group walk on teardown
CVE-2026-99121Noneipv4: avoid divide by zero in fib_rebalance
CVE-2026-99120NoneKVM: x86/mmu: Cope with the SS bit being set in #NPF exit codes
CVE-2026-99119Nonedrm/amdgpu/userq: actually validate userq BOs
CVE-2026-99123Nonevsock/virtio: validate packet source for connected sockets