Linux
fuse: reject oversized dirents in page cache
In the Linux kernel, the following vulnerability has been resolved: fuse: reject oversized dirents in page cache fuse_add_dirent_to_cache() computes a serialized dirent size from the server-controlled namelen field and copies the dirent into a single page-cache page. The existing logic only checks whether the dirent fits in the remaining space of the current page and advances to a fresh page if not. It never checks whether the dirent itself exceeds PAGE_SIZE. As a result, a malicious FUSE server can return a dirent with namelen=4095, producing a serialized record size of 4120 bytes. On 4 KiB page systems this causes memcpy() to overflow the cache page by 24 bytes into the following kernel page. Reject dirents that cannot fit in a single page before copying them into the readdir cache.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 27992ef80770d61a57f6c3a551735b08cefdffa3, < 7de93abfaae1b2dc94da8a07a36421bd073f1d8f
- >= 27992ef80770d61a57f6c3a551735b08cefdffa3, < 474ce83c96a55f2eeb14dee2be375eeadfdacdf5
- >= 27992ef80770d61a57f6c3a551735b08cefdffa3, < 51a8de6c50bf947c8f534cd73da4c8f0a13e7bed
Fixed in 7de93abfaae1b2dc94da8a07a36421bd073f1d8f, 474ce83c96a55f2eeb14dee2be375eeadfdacdf5, 51a8de6c50bf947c8f534cd73da4c8f0a13e7bed
- 6.15
Fixed in 0, 6.18.25, 7.0.2, 7.1
Mitigation
Upgrade Linux to 7de93abfaae1b2dc94da8a07a36421bd073f1d8f or 474ce83c96a55f2eeb14dee2be375eeadfdacdf5 or 51a8de6c50bf947c8f534cd73da4c8f0a13e7bed or later.
Upgrade Linux to 0 or 6.18.25 or 7.0.2 or 7.1 or later.
Timeline
Days relative to CVE publicationFirst public PoC 60 days after publication; not in CISA KEV. First PoC: 0xCyberstan/CVE-2026-31694-POC (created 30 Jun 2026, found by us: backfilled).
PoC repositories
Found on GitHub.2 PoCs
PoCs 2
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| 0xCyberstan/CVE-2026-31694-POC | 30 Jun 2026 +60 d | 18 | PoC |
| zenzue/CVE_2026_31694 | 29 Jul 2026 +88 d | 0 | PoC |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.