PT-2026-152525
CVE-2026-99645
·
Published
2026-11-20
·
Updated
2026-11-20
Description by
Score
N/A
Not availableNo severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
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() ]
Found an issue in the description? Have something to add? Feel free to write us 👾