Linux kernel uninitialized memory leak in OverlayFS copy-up
- Exploited
- No known exploitation
- Fix
- Fixed in 3.19, 4.2, 4.5
- Who is exposed
- Not reported
Summary
The ovl copy-up code in the Linux kernel can store uninitialized kernel memory as an extended attribute on the upper file, where users can read it. This happens when a lower layer, such as a FUSE server, answers attribute reads with -ERANGE, and the leaked data can include kernel pointers.
Written by a model
Original description
In the Linux kernel, the following vulnerability has been resolved:
ovl: do not copy up an xattr value that was never read
Copy-up stores uninitialized kernel memory in an xattr of the upper file, where the user can read it.
ovl_copy_xattr() may only pass bytes to ovl_do_setxattr() that ovl_do_getxattr() has read. When the read fails with -ERANGE the function asks for the size again, and if the new size fits the buffer it stores the buffer although nothing was read into it. The buffer comes from kvmalloc(), or it still holds the value of the previous xattr.
A FUSE lower layer that answers every sized GETXATTR with -ERANGE made copy-up store 4096 bytes that the server never sent, with a kernel pointer in them, as an xattr of the upper file.
Fix this by failing the copy-up with -EIO when the size that follows -ERANGE fits the buffer.
What to do
Upgrade to a fixed version: 3.19, 4.2, 4.5.
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-99418 (ovl: do not copy up an xattr value that was never read), 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-99418 (entry last updated 2026-11-19):
Affected:
- Linux Linux: from 3.18.27, fixed in 3.19; from 4.1.18, fixed in 4.2; from 4.4.3, fixed in 4.5
- Linux Linux: versions 4.5
Fixed versions: 3.19, 4.2, 4.5.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-99418 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99418 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/3b1f5a4652539014f0162944f1a5f71ee520188a
- https://git.kernel.org/stable/c/628260a7204314ab5f1cd93bddb1721cc0226b38
- https://git.kernel.org/stable/c/e35c3b1dc69b8c8efe3d751fafb9b50a85f0e2f7
- https://git.kernel.org/stable/c/755b5c5c9277be251a51623d6065abab948c61bc
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-99418
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-99418"}.Affected versions
- Linux LinuxFrom 3.18.27 · fixed in 3.19; From 4.1.18 · fixed in 4.2; From 4.4.3 · fixed in 4.5
- Linux Linux4.5
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
Evidence 6
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-99418 |
| Record | NVD · CVE-2026-99418 |
| Other links 4 | |
| Link | git.kernel.org · stable/c/3b1f5a4652539014f0162944f1a5f71ee520188a |
| Link | git.kernel.org · stable/c/628260a7204314ab5f1cd93bddb1721cc0226b38 |
| Link | git.kernel.org · stable/c/e35c3b1dc69b8c8efe3d751fafb9b50a85f0e2f7 |
| Link | git.kernel.org · stable/c/755b5c5c9277be251a51623d6065abab948c61bc |
Questions about CVE-2026-99418
Is CVE-2026-99418 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-99418?
Linux: from 3.18.27 before 3.19; from 4.1.18 before 4.2; from 4.4.3 before 4.5. Linux: version 4.5.
Source: cve.now feed data
How do I fix CVE-2026-99418?
Upgrade to a fixed version: 3.19, 4.2, 4.5.
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.