Skip to main content
Menu
CVEs

Linux kernel denial of service in shmem truncation

CVE-2026-99739Published November 20, 2026, updated

Exploited
No known exploitation
Fix
Fixed in 6.12.118, 6.18.64
Who is exposed
Not reported

Summary

In the Linux kernel, truncating a tmpfs file or memfd to a page-aligned size inside a large swap entry can cause an indefinite hang in shmem_undo_range(). The stuck task holds the inode lock and cannot be killed.

Written by a model

Original description

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

mm/shmem: fix truncate hang in large swap entry

Truncating a tmpfs file or memfd to a page-aligned size inside a large swap entry can loop indefinitely in shmem_undo_range(). The task holds the inode lock and cannot be killed.

A large swap entry represents a whole swapped-out folio. For example, truncate a file whose pages 0-7 share one swap entry to four pages:

[ 0 1 2 3 | 4 5 6 7 ] keep | discard ^ new EOF, start = 4

i_size has already been updated when boundary handling asks shmem_get_partial_folio() for page 4. Since it is swapped out, the helper calls shmem_get_folio() with SGP_READ. That rejects page 4 with -EINVAL because its starting offset equals i_size. Nothing is read back.

The final scan cannot free the entry without losing pages 0-3. It skips it, restarts from start = 4, and finds it again indefinitely. An unaligned truncate avoids this particular failure because the requested page starts below i_size. Folios already in the page-cache cannot trigger it as the direct lookup will return them beyond EOF.

Fix it by letting shmem_get_partial_folio() call shmem_swapin_folio() directly for swap entries. This bypasses the read path's i_size check, allowing the existing boundary handling to zero and split the folio. If swap-in returns a smaller folio, it also splits the swap entry so the final scan can free the entries beyond EOF. Retry the lookup if the entry changes during swap-in.

Handling swap-in allocation failures remains broken and is unchanged by this commit. Even when shmem_swapin_folio() correctly returns -ENOMEM instead of -EEXIST, shmem_get_partial_folio() returns NULL and shmem_undo_range() skips boundary handling. If the large swap entry remains intact, truncation can still loop in the final scan, while hole punching can return without zeroing the boundary.

This may read an entire large folio back from swap while holding i_rwsem, only to discard part of it. Avoiding that I/O would require splitting both the swap entry and any large folio still in the swap cache. That, however, is much bigger work.

What to do

Upgrade to a fixed version: 6.12.118, 6.18.64.

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-99739 (mm/shmem: fix truncate hang in large swap entry), 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-99739 (entry last updated 2026-11-20):
Affected:
- Linux Linux: from 6.12.69, fixed in 6.12.118; from 6.18.9, fixed in 6.18.64
- Linux Linux: versions 6.19
Fixed versions: 6.12.118, 6.18.64.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-99739 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99739 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/9fbca74e8efbb8fed180639af349449f04a2a3c3
- https://git.kernel.org/stable/c/577374a2171cdb68e492725feb564364f93161b6
- https://git.kernel.org/stable/c/ef6daf302dc569a67fe50968f9b6085f111b8560
- https://git.kernel.org/stable/c/fa213b08f37f9dff78ce240a87579dc264fc7a5d
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-99739
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-99739"}.

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 6

Questions about CVE-2026-99739

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

Linux: from 6.12.69 before 6.12.118; from 6.18.9 before 6.18.64. Linux: version 6.19.

Source: cve.now feed data

How do I fix CVE-2026-99739?

Upgrade to a fixed version: 6.12.118, 6.18.64.

Source: cve.now feed data

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