CVE-2026-99371
What it is
In the Linux kernel, the following vulnerability has been resolved: nfsd: clear XDR padding in GETXATTR replies nfsd4_vbuf_to_stream() uses a raw memcpy() for the first fragment of an attribute value. xdr_reserve_space() aligns the reservation but does not initialize the extra bytes. If the complete value fits in that fragment, the loop that clears padding for the final fragment is never entered. A remote client reading an attribute whose length is not a multiple of four can therefore receive one to three stale bytes from the response page. Encode the first fragment with xdr_encode_opaque_fixed(), matching the final-fragment path and ensuring that any XDR padding is zeroed.
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 < 842e2215a87d062b69d5170840f34fbd83f47b41
- Linux < 624531ecd48b96be2a94c964685762960bd11208
- Linux < 99ab5346b69834587b4ae59d1addea5960b50c8b
- Linux < daba58690339ae86f1ebeb5197aa1369fae37e57
- Linux 5.9
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-99371.md and follow it. Check whether this project is affected by CVE-2026-99371. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.