CVE-2026-99393
What it is
In the Linux kernel, the following vulnerability has been resolved: xfs: don't overrun incore inode when cleaning attr forks LOLLM noticed that xrep_dinode_check_afork doesn't check for a di_forkoff value that is so large that the attr fork would begin after the end of the inode space. This causes afork_{ptr,size} to be nonsense. What we really ought to do here is zap the attr fork.
At a glance
- Fix
- No patch or advisory is linked yet. Look at mitigations or restrict exposure.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: not scored yet.
- Severity: not scored yet.
- Fix: none linked yet, which raises it.
Details
- Published
- Last modified
- Record status
- Received
Affected
- Linux < 4a6217e7bdf3b1cdd28799d19c175cb3bad375ec
- Linux < 6b93f0aeb8815a3ad296492e97173f9fc137340e
- Linux < 471e4ae43cc5f931430f7701df45ce82c8afc05d
- Linux < c28b4b48deac17749ed1ebe4289a4ba73541ddc6
- Linux 6.8
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-99393.md and follow it. Check whether this project is affected by CVE-2026-99393. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.