Skip to main content
VulnerabilityPublished

CVE-2026-99645: Linux kernel · mm/cma: don't release CMA pages still in use

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited : upgrade to e8abc61d8a549a91c8fa639f68be2ef13d5fa63b or 485214cc031771fdbd5829b431f4f115e285dc21 when convenient.

Data as of 20 Nov 2026, 06:04 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in e8abc61d8a549a91c8fa639f68be2ef13d5fa63b, 485214cc031771fdbd5829b431f4f115e285dc21

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 e8abc61d8a549a91c8fa639f68be2ef13d5fa63b or 485214cc031771fdbd5829b431f4f115e285dc21.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 9bda131c6093e9c4a8739e2eeb65ba4d5fbefc2f, < e8abc61d8a549a91c8fa639f68be2ef13d5fa63b
Fixed in
  • e8abc61d8a549a91c8fa639f68be2ef13d5fa63b
LinuxLinuxAffected
  • ≥ 9bda131c6093e9c4a8739e2eeb65ba4d5fbefc2f, < 485214cc031771fdbd5829b431f4f115e285dc21
Fixed in
  • 485214cc031771fdbd5829b431f4f115e285dc21
LinuxLinuxAffected
  • =7.0
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: mm/cma: don't release CMA pages still in use When a driver calls dma_free_contiguous() before quiescing DMA, the page might still have a reference from the device. put_page_testzero() there returns false, WARN fires, but the code proceeds to free_contig_frozen_range() putting a live page onto buddy and clearing the bitmap. A subsequent allocation can hand the same PFN to a new owner while the original holder still references it. A concurrent put_page() that drops the last reference between the testzero loop and free_contig_frozen_range() can double-queue the page via page->lru, corrupting buddy lists. Avoid the corruption by not freeing a CMA region if any of the pages inside are still in use. Make it explicit in the warning that the driver allowed a leak. While at it, use page_ref_freeze() to make the semantics clearer and switch to pr_warn_ratelimited(). [ david: use page_ref_freeze() + pr_warn_ratelimited() ]

References

Community reviews

Loading reviews…