CVE-2026-99418: Linux kernel · ovl: do not copy up an xattr value that was never read
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in e35c3b1dc69b8c8efe3d751fafb9b50a85f0e2f7 : patch Linux kernel soon.
Data as of 19 Nov 2026, 14:52 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in e35c3b1dc69b8c8efe3d751fafb9b50a85f0e2f7, 628260a7204314ab5f1cd93bddb1721cc0226b38, 755b5c5c9277be251a51623d6065abab948c61bc +4
Exploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
This vulnerability has been fixed in Linux kernel versions 3.19, 4.2, and 4.5 as well as specific commits identified by their hashes. Users should upgrade to these fixed versions or later to remediate the issue. No additional mitigation is required once the system is updated.
Description
A vulnerability in the Linux kernel overlay filesystem (ovl) could cause uninitialized kernel memory to be copied into an extended attribute (xattr) of an upper file, potentially exposing kernel memory contents to userspace. This occurs when a FUSE lower layer returns -ERANGE for every sized GETXATTR request, leading to storing uninitialized data during copy-up. The issue has been fixed by ensuring the copy-up fails with -EIO when the size following -ERANGE fits the buffer but no data was read.
References
- git.kernel.org/stable/c/3b1f5a4652539014f0162944f1a5f71ee520188a (opens in a new tab)
- git.kernel.org/stable/c/628260a7204314ab5f1cd93bddb1721cc0226b38 (opens in a new tab)
- git.kernel.org/stable/c/e35c3b1dc69b8c8efe3d751fafb9b50a85f0e2f7 (opens in a new tab)
- git.kernel.org/stable/c/755b5c5c9277be251a51623d6065abab948c61bc (opens in a new tab)