Skip to main content
Menu
CVEs

Linux kernel use-after-free in overlayfs directory listing

CVE-2026-99424Published November 19, 2026, updated

Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported

Summary

The Linux kernel has a use-after-free bug in its directory listing code. An unprivileged process that lists a directory during its copy-up can cause the readdir cache of another open file descriptor to be freed while it is still in use.

Written by a model

Original description

In the Linux kernel, the following vulnerability has been resolved:

ovl: set OVL_WHITEOUTS before publishing the upper dir

Listing a directory while it is copied up causes a use-after-free of the readdir cache.

A merge directory must never be iterated as a real upper directory: that mode frees the cache in OVL_I(inode)->cache without looking at its refcount, while files opened in merged mode still use it. ovl_copy_up_workdir() publishes the upper dentry before it sets OVL_WHITEOUTS, and ovl_dir_open() samples both without a lock, so an open between the two stores finds the upper directory and takes it for a real one.

With a delay between the two stores, an unprivileged process that listed a directory during its copy-up saw only "." and "..", and its next getdents freed the readdir cache of another descriptor.

Fix this by setting OVL_WHITEOUTS before ovl_inode_update(), so that ovl_dir_reset() agrees with ovl_dir_open(), and by testing OVL_TYPE_MERGE() of the path type in ovl_dir_open(), so that an open that observes the upper dentry never iterates a merge dir as a real dir, regardless of the order in which it observes the flag.

[amir: test OVL_TYPE_MERGE() instead of smp_rmb() in ovl_dir_open()]

What to do

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-99424 (ovl: set OVL_WHITEOUTS before publishing the upper dir), 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-99424 (entry last updated 2026-11-19):
Affected:
- Linux Linux: version range not reported
- Linux Linux: versions 4.15
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-99424 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99424 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/43ad4a3090e1c2a0c34e9802882b42c5c078d556
- https://git.kernel.org/stable/c/7805739ce4577f2c53f5a30be2d48e83e91c63bc
- https://git.kernel.org/stable/c/ea5327a9228bfd1609e54f1fca50786e8f963da5
- https://git.kernel.org/stable/c/cbec8610ec5aaf35df50094ff639febc23f20773
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-99424
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-99424"}.

Affected versions

cve.now Index

25Pof 100 · provisional · methodology v3
  • 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 patch5/5No patch listed yet

What would change the score

  • Would score about 80 if added to CISA KEV
  • Would score about 75 if CISA's SSVC rates exploitation active
  • Would score about 47 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 6

Questions about CVE-2026-99424

Is CVE-2026-99424 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-99424?

Linux: version 4.15.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.