6 matches found
CVE-2026-99699
The Linux kernel contains a vulnerability where pages of allocated multi-range CMA areas (used by hugetlb_cma ) and fixed CMA areas (requested via cma=@) are reserved using memblock_reserve() but are never accepted. Because cma_activate_area() releases these pages to the buddy allocator via __fre...
EUVD-2026-130991
In the Linux kernel, the following vulnerability has been resolved: mm/cma: accept memory of CMA areas reserved at a fixed address CMA areas allocated from memblock have their memory accepted by memblockallocrangenid, but areas reserved at a fixed address with memblockreserve are not. If a fixed...
EUVD-2026-130992
In the Linux kernel, the following vulnerability has been resolved: mm/cma: accept memory of multi-range CMA areas Patch series "mm/cma: accept memory of CMA areas reserved with memblockreserve", v1. Pages of allocated CMA areas are released to the buddy allocator with freepages, which does not...
CVE-2026-99698
The Linux kernel contains a vulnerability in mm/cma where memory from CMA areas reserved at a fixed address using memblock_reserve() is not correctly accepted by memblock_alloc_range_nid(). This contrasts with CMA areas allocated from memblock, which are accepted. The issue is particularly releva...
CVE-2026-99645
The Linux kernel contains a vulnerability in the mm/cma component where a driver calling dma_free_contiguous() before quiescing DMA can cause the kernel to release a CMA page that is still referenced by a device. Because the code proceeds to call free_contig_frozen_range() despite a failed put_pa...
EUVD-2026-130938
In the Linux kernel, the following vulnerability has been resolved: mm/cma: don't release CMA pages still in use When a driver calls dmafreecontiguous before quiescing DMA, the page might still have a reference from the device. putpagetestzero there returns false, WARN fires, but the code proceed...