Skip to main content
VulnerabilityPublished

CVE-2026-99616: Linux kernel · ovl: look up the index by the decoded origin

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-99616· High

Not known to be exploited · fixed in aae380322cf51c645448d7063888fb5d14df08cb : patch Linux kernel soon.

Data as of 20 Nov 2026, 07:34 UTC

Severity
High

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in aae380322cf51c645448d7063888fb5d14df08cb, 520ef67f47f69255695859b0008281a384d0bc20, 7cd237effa89a6bb59da3bc9f98c9823cf1429ba +1

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 19 Nov 2026.

What to do

Upgrade Linux kernel to aae380322cf51c645448d7063888fb5d14df08cb, 520ef67f47f69255695859b0008281a384d0bc20, 7cd237effa89a6bb59da3bc9f98c9823cf1429ba or 4b0d6c2bb0eadacecf35641cd63851d8406b22f2.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ f71bd9cfb692ec80236b186419bf907eb5fa348c, < aae380322cf51c645448d7063888fb5d14df08cb
Fixed in
  • aae380322cf51c645448d7063888fb5d14df08cb
LinuxLinuxAffected
  • ≥ f71bd9cfb692ec80236b186419bf907eb5fa348c, < 520ef67f47f69255695859b0008281a384d0bc20
Fixed in
  • 520ef67f47f69255695859b0008281a384d0bc20
LinuxLinuxAffected
  • ≥ f71bd9cfb692ec80236b186419bf907eb5fa348c, < 7cd237effa89a6bb59da3bc9f98c9823cf1429ba
Fixed in
  • 7cd237effa89a6bb59da3bc9f98c9823cf1429ba
LinuxLinuxAffected
  • ≥ f71bd9cfb692ec80236b186419bf907eb5fa348c, < 4b0d6c2bb0eadacecf35641cd63851d8406b22f2
Fixed in
  • 4b0d6c2bb0eadacecf35641cd63851d8406b22f2
LinuxLinuxAffected
  • =4.16
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: ovl: look up the index by the decoded origin A file opened by file handle on an overlay with nfs_export=on can show the stale lower data of a file that was copied up to the upper layer. While the file opened this way stays in the inode cache, a lookup of the copied up file by path fails with ESTALE for all users. The open can also succeed for a file that was removed, where it has to fail with ESTALE. This happens with a handle that has one byte changed. The handle comes from an NFS client, or from a process that calls open_by_handle_at() with CAP_DAC_READ_SEARCH in the initial user namespace. When a file in a lower layer is about to be modified, overlayfs first copies it to the upper layer (copy up). With nfs_export=on, each copy up also creates an entry in the index directory, a directory that overlayfs keeps for itself on the upper filesystem. The handle of an overlay file that comes from a lower layer wraps the handle of its lower inode. Overlayfs calls this lower inode the origin. The overlay handle stays valid after a copy up. To decode such a handle, ovl_lower_fh_to_d() first decodes the wrapped handle to the origin. If no overlay inode is cached for the origin, it looks in the index directory: - An index entry there leads to the upper file. - A whiteout, the marker that overlayfs uses for a removed file, means that the overlay file was removed. The name of an index entry is the handle that copy up encoded for the origin, as a hex string. ovl_lower_fh_to_d() builds the name for this lookup from the bytes that the caller passed in. But handles with different bytes can decode to the same inode: - Overlayfs ignores some flag bits of the handle. - A lower filesystem can accept a different fid type, extra bytes, or generation 0 for any generation. Such a handle decodes to the origin but misses the index entry or the whiteout. So the decode returns an overlay inode that has only the lower file. While that inode is cached, a path lookup of a copied up file fails with ESTALE, since the upper file that the lookup finds does not match the cached inode, which has none. Reproduced on tmpfs and on ext4 with open_by_handle_at(), after a copy up and a mount cycle. A handle in which one flag bit, the fid type, the length or the generation was changed read the old lower data, and path lookups returned ESTALE. Fix this by re-encoding the decoded origin and building the index name from that handle.

References

Community reviews

Loading reviews…