mm/cma: don't release CMA pages still in use
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 485214cc031771fdbd5829b431f4f115e285dc21, Kernel e8abc61d8a549a91c8fa639f68be2ef13d5fa63b and Kernel 7.3.5.
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() ]
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =7.0, >=9bda131c6093e9c4a8739e2eeb65ba4d5fbefc2f <485214cc031771fdbd5829b431f4f115e285dc21, >=9bda131c6093e9c4a8739e2eeb65ba4d5fbefc2f <e8abc61d8a549a91c8fa639f68be2ef13d5fa63b | 485214cc031771fdbd5829b431f4f115e285dc21, e8abc61d8a549a91c8fa639f68be2ef13d5fa63b |
| linux-kernel: Kernel | >=7.0.0 <7.3.5 | 7.3.5 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket