Skip to main content
Menu
CVEs

Linux kernel denial of service in overlayfs copy-up

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

Exploited
No known exploitation
Fix
Fixed in 6.6.73
Who is exposed
Not reported

Summary

The Linux kernel's overlayfs crashes when a user copies up a directory from a lower layer, after a security module has stopped granting the mounter CAP_DAC_READ_SEARCH on an overlay mounted with index and NFS export enabled. Any user who can write to such a directory can trigger the crash.

Written by a model

Original description

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

ovl: always encode the origin fh when index is enabled

On an overlay with index=on,nfs_export=on, copy up of a directory crashes the kernel once an LSM has started to deny CAP_DAC_READ_SEARCH to the mounter, the task that mounted the overlay. The mount and the LSM policy change require root. After that, any user who can write to a directory that exists only in a lower layer triggers the oops by doing so.

Before a file or directory that exists only in a lower layer is changed for the first time, overlayfs copies it to the writable upper layer. This is called copy up.

On copy up, ovl_get_origin_fh() encodes the file handle of the lower inode, called the origin. It returns NULL if ovl_can_decode_fh() says that the lower filesystem cannot decode handles. Whether the callers can handle NULL depends on the index option:

  • Without an index, NULL is fine: the callers store an empty origin xattr.
  • With index enabled, overlayfs keeps entries for copied up inodes in an internal index directory. The name of an index entry is derived from the handle, so ovl_get_origin_fh() must return a handle or an error.

The mount only enables the index if ovl_can_decode_fh() succeeds for all layers, but the result can change later. The function checks the export operations of the filesystem and capable(CAP_DAC_READ_SEARCH). Copy up runs with the mounter's credentials, and an LSM can start to deny the capability to those credentials after the mount. ovl_get_origin_fh() then returns NULL with index enabled.

This goes wrong in two callers:

  • With nfs_export=on, copy up of a directory creates an index entry for the directory. ovl_create_index() passes the NULL handle to ovl_get_index_name_fh(), which dereferences it.
  • If the result changes while mount(2) is still running, ovl_get_indexdir() passes a NULL from ovl_get_origin_fh() to ovl_verify_set_fh() in the same way.

Before the commit in the Fixes tag, these two callers encoded the handle themselves, without consulting ovl_can_decode_fh().

Reproduced with a BPF LSM program that started to deny the capability after the mount. An unprivileged touch in a directory that had not been copied up yet oopsed in ovl_get_index_name_fh(). With this patch the touch succeeds and the directory gets its index entry.

Fix this by calling ovl_can_decode_fh() in ovl_get_origin_fh() only when index is disabled.

What to do

Upgrade to a fixed version: 6.6.73.

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-99421 (ovl: always encode the origin fh when index is enabled), 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-99421 (entry last updated 2026-11-19):
Affected:
- Linux Linux: from 6.6.72, fixed in 6.6.73
- Linux Linux: versions 6.7
Fixed versions: 6.6.73.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-99421 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99421 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/1795ca6571199008f67afa9e88cddf199ddde9ca
- https://git.kernel.org/stable/c/4a58c0d62bd23173dee3f337f623d3e14b6c9dd4
- https://git.kernel.org/stable/c/b050952bc4e3409c655a4abcd987131bd77ef570
- https://git.kernel.org/stable/c/5ccb1e71dfea95a9789967c34d68a2b7c048303e
- https://git.kernel.org/stable/c/949f9d8a5580c77a45fa759123367682aba4d173
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-99421
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-99421"}.

Affected versions

cve.now Index

20Pof 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 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

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

Evidence 7

Questions about CVE-2026-99421

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

Linux: from 6.6.72 before 6.6.73. Linux: version 6.7.

Source: cve.now feed data

How do I fix CVE-2026-99421?

Upgrade to a fixed version: 6.6.73.

Source: cve.now feed data

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