Bug 2577795 (CVE-2026-99645) - CVE-2026-99645 kernel: kernel: Memory corruption via premature release of in-use CMA pages
Summary: CVE-2026-99645 kernel: kernel: Memory corruption via premature release of in-...
Keywords:
Status: NEW
Alias: CVE-2026-99645
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-11-20 06:14 UTC by OSIDB Bzimport
Modified: 2026-11-20 11:15 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-11-20 06:14:16 UTC
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() ]


Note You need to log in before you can comment on or make changes to this bug.