CVE-2026-99395
Severity unknownNo known exploitationFix availablexfs: bound inode fork length against the fork size during log recovery
Record last updated
CVSS score
No score published yet
EPSS, chance of exploitation in 30 days
Higher than 13% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
Description
In the Linux kernel, the following vulnerability has been resolved: xfs: bound inode fork length against the fork size during log recovery xlog_recover_inode_commit_pass2() copies an inode log item's data/attr fork region into the inode buffer using the on-log region length without bounding it against the fork capacity, e.g.: len = item->ri_buf[2].iov_len; memcpy(XFS_DFORK_DPTR(dip), src, len); The only guard is an ASSERT, which is a no-op on production kernels (CONFIG_XFS_DEBUG off), and xfs_dinode_verify() runs only after the copy. A crafted image with a dirty log can therefore drive a heap out-of-bounds write at mount time. The XFS_ILOG_DBROOT sibling already passes XFS_DFORK_DSIZE as a bound; the DDATA/DEXT and ADATA/AEXT memcpy paths did not. Bound each logged fork region against the destination fork size before copying it, and reject the log item with -EFSCORRUPTED when it does not fit. Because the recovered inode is only verified after the fork data has been copied in, the checks are done up front, before any memcpy into the on-disk inode.
Patching and mitigation
- Patch status
- Fix available (source: CVE record (Linux))
- Fix documented (source date)
- Mitigation
- None documented
- Vendor guidance
- No vendor link on record
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| Linux | Linux | from 658fa68b6f34f73c7e4023489accd34c1db91cb1 before f2cc5001ffcc1d8e5e16607ce4b6920ea30c2cfe | f2cc5001ffcc1d8e5e16607ce4b6920ea30c2cfe | CVE Program |
| Linux | Linux | from 658fa68b6f34f73c7e4023489accd34c1db91cb1 before e2768e65a5f2f942c831e3df3b06ad7332d423e6 | e2768e65a5f2f942c831e3df3b06ad7332d423e6 | CVE Program |
| Linux | Linux | from 658fa68b6f34f73c7e4023489accd34c1db91cb1 before 9232301894a06e664d8de2da97175cf98419bd16 | 9232301894a06e664d8de2da97175cf98419bd16 | CVE Program |
| Linux | Linux | from 658fa68b6f34f73c7e4023489accd34c1db91cb1 before af559d87fdd921b90c86125f78d8b97d754432dd | af559d87fdd921b90c86125f78d8b97d754432dd | CVE Program |
| Linux | Linux | 5.8 | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 6.12.117 up to and including 6.12.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 6.18.61 up to and including 6.18.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 7.3.2 up to and including 7.3.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | 7.4-rc1 | Not documented | CVE Program |
| Linux | Linux (unaffected) | all versions before 5.8 | Not documented | CVE Program |
Timeline
Disclosure
CVE record published by Linux
Source: CVE Program (opens in a new tab)
Patch
Fix documented by CVE record (Linux)
Vendor guidance and references
- https://git.kernel.org/stable/c/9232301894a06e664d8de2da97175cf98419bd16 (opens in a new tab)
- https://git.kernel.org/stable/c/af559d87fdd921b90c86125f78d8b97d754432dd (opens in a new tab)
- https://git.kernel.org/stable/c/e2768e65a5f2f942c831e3df3b06ad7332d423e6 (opens in a new tab)
- https://git.kernel.org/stable/c/f2cc5001ffcc1d8e5e16607ce4b6920ea30c2cfe (opens in a new tab)