Skip to main content
Menu
CVEs

Linux kernel denial of service via infinite loop in shmem truncation

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

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

Summary

The Linux kernel's shmem truncation code can loop forever while holding a file lock when swapping in a large entry at the end of the file fails. This can hang the affected system.

Written by a model

Original description

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

mm/shmem: fix truncate loop after boundary swapin failure

If swapping in a large entry at the new EOF fails, shmem_undo_range() leaves the entry in place. Its final scan skips the entry, then restarts from the same start index and finds it again. Truncation can loop forever while holding i_rwsem.

Advance start past the skipped entry so that a restarted scan can finish, as we already do for folios that cannot be split.

Note that this does not fix the missing zeroing when boundary swapin fails, it merely prevents the endless loop.

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-99737 (mm/shmem: fix truncate loop after boundary swapin failure), 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-99737 (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-99737 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99737 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/7f1bbb9c6a8ed3fed72bf7efc906ebe31e92feeb
- https://git.kernel.org/stable/c/d4d46430852caf5e7dbca1386fc6621ecf8fe2b0
- https://git.kernel.org/stable/c/e6e9ba49679e5f33f62615fb57ec103045fbc8f9
- https://git.kernel.org/stable/c/5f1ec2cf92a7d655a8eb39711987822f9b1f9d67
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-99737
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-99737"}.

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-99737

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

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-99737?

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.