Linux kernel wrong data written in NFSD SETXATTR handling
- Exploited
- No known exploitation
- Fix
- Fixed in 5.11
- Who is exposed
- Not reported
Summary
The NFSD server component of the Linux kernel can copy the wrong bytes into the value of an extended attribute set through a SETXATTR request. This happens when the request data is split across buffer segments with a nonzero starting offset or spans into the tail.
Written by a model
Original description
In the Linux kernel, the following vulnerability has been resolved:
NFSD: copy SETXATTR data from all XDR buffer segments
nfsd4_vbuf_from_vector() manually copies the head followed by whole pages starting at offset zero. This assumes that all remaining data starts at the beginning of the page array and that no data is stored in the tail.
However, nfsd4_decode_setxattr() passes an xdr_buf returned by xdr_stream_subsegment(). Such a sub-buffer can have a nonzero page_base and can span its page and tail segments. Ignoring that layout can copy the wrong bytes into the value passed to vfs_setxattr().
Use read_bytes_from_xdr_buf(), which observes the complete xdr_buf layout.
What to do
Upgrade to a fixed version: 5.11.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-99370 (NFSD: copy SETXATTR data from all XDR buffer segments), 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-99370 (entry last updated 2026-11-19):
Affected:
- Linux Linux: from 5.10.220, fixed in 5.11
- Linux Linux: versions 5.11
Fixed versions: 5.11.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-99370 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99370 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/019cf7e0eebf6dc14b465cc984390b41c854da69
- https://git.kernel.org/stable/c/20b76bdbd029343ea98944cb88bf016da2371739
- https://git.kernel.org/stable/c/fea77ec4a37614cbbe4fb26c621227182439f487
- https://git.kernel.org/stable/c/b01319947c69b0e3ea0fcd4b675eb892f9cad8a0
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-99370
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-99370"}.Affected versions
- Linux LinuxFrom 5.10.220 · fixed in 5.11
- Linux Linux5.11
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach20/20Affects Linux kernel (software on nearly every server, desktop or phone)
- Severity?/10Unknown. No CVSS score or vendor rating
- No patch0/5No signal
What would change the score
- Would score about 75 if added to CISA KEV
- Would score about 70 if CISA's SSVC rates exploitation active
- Would score about 42 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- Record last updated
Evidence 6
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-99370 |
| Record | NVD · CVE-2026-99370 |
| Other links 4 | |
| Link | git.kernel.org · stable/c/019cf7e0eebf6dc14b465cc984390b41c854da69 |
| Link | git.kernel.org · stable/c/20b76bdbd029343ea98944cb88bf016da2371739 |
| Link | git.kernel.org · stable/c/fea77ec4a37614cbbe4fb26c621227182439f487 |
| Link | git.kernel.org · stable/c/b01319947c69b0e3ea0fcd4b675eb892f9cad8a0 |
Questions about CVE-2026-99370
Is CVE-2026-99370 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: cve.now feed data
Which versions are affected by CVE-2026-99370?
Linux: from 5.10.220 before 5.11. Linux: version 5.11.
Source: cve.now feed data
How do I fix CVE-2026-99370?
Upgrade to a fixed version: 5.11.
Source: cve.now feed data
Related
- CVE-2026-99804io_uring/io-wq: save worker type before dropping its reference
- CVE-2026-99803io_uring/net: mask socket type with SOCK_TYPE_MASK in io_socket_bpf_populate()
- CVE-2026-99802io_uring/register: enforce per-task restrictions in io_uring_register_blind()
- CVE-2026-99801io_uring/bpf-ops: clear bpf_ctx while submitting SQEs
- CVE-2026-99800io_uring: free the task context after a grace period
- CVE-2026-99799io_uring/sqpoll: don't wait for the thread to exit
No corrections so far. Something wrong on this page? Report an error.