CVE-2022-49052

published 26 Feb 2025 · updated 5 Aug 2026

mm: fix unexpected zeroed page mapping with zram swap

7.1HighCVSS 7.1EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 12ba1d38115a101c45d8e0ca3aa1181fd148e57f, Kernel 20ed94f8181a25212e7404e44958e234f407624b, Kernel afac4b88699a06c8b9369f9d759a1ec3c254b788 and 3 more.

In the Linux kernel, the following vulnerability has been resolved: mm: fix unexpected zeroed page mapping with zram swap Two processes under CLONE_VM cloning, user process can be corrupted by seeing zeroed page unexpectedly. CPU A CPU B do_swap_page do_swap_page SWP_SYNCHRONOUS_IO path SWP_SYNCHRONOUS_IO path swap_readpage valid data swap_slot_free_notify delete zram entry swap_readpage zeroed(invalid) data pte_lock map the *zero data* to userspace pte_unlock pte_lock if (!pte_same) goto out_nomap; pte_unlock return and next refault will read zeroed data The swap_slot_free_notify is bogus for CLONE_VM case since it doesn't increase the refcount of swap slot at copy_mm so it couldn't catch up whether it's safe or not to discard data from backing device. In the case, only the lock it could rely on to synchronize swap slot freeing is page table lock. Thus, this patch gets rid of the swap_slot_free_notify function. With this patch, CPU A will see correct data. CPU A CPU B do_swap_page do_swap_page SWP_SYNCHRONOUS_IO path SWP_SYNCHRONOUS_IO path swap_readpage original data pte_lock map the original data swap_free swap_range_free bd_disk->fops->swap_slot_free_notify swap_readpage read zeroed data pte_unlock pte_lock if (!pte_same) goto out_nomap; pte_unlock return on next refault will see mapped data by CPU B The concern of the patch would increase memory consumption since it could keep wasted memory with compressed form in zram as well as uncompressed form in address space. However, most of cases of zram uses no readahead and do_swap_page is followed by swap_free so it will free the compressed form from in zram quickly.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=4.15, >=0bcac06f27d7528591c27ac2b093ccd71c5d0168 <12ba1d38115a101c45d8e0ca3aa1181fd148e57f, >=0bcac06f27d7528591c27ac2b093ccd71c5d0168 <20ed94f8181a25212e7404e44958e234f407624b, >=0bcac06f27d7528591c27ac2b093ccd71c5d0168 <afac4b88699a06c8b9369f9d759a1ec3c254b788, >=0bcac06f27d7528591c27ac2b093ccd71c5d0168 <e914d8f00391520ecc4495dd0ca0124538ab7119, >=0bcac06f27d7528591c27ac2b093ccd71c5d0168 <f098f8b9820fe3f2e41aefc4329dfe8a3859d1c1, >=0bcac06f27d7528591c27ac2b093ccd71c5d0168 <f86d55cf616199404c05f5b0c5c41b17351baa0212ba1d38115a101c45d8e0ca3aa1181fd148e57f, 20ed94f8181a25212e7404e44958e234f407624b, afac4b88699a06c8b9369f9d759a1ec3c254b788, e914d8f00391520ecc4495dd0ca0124538ab7119, f098f8b9820fe3f2e41aefc4329dfe8a3859d1c1, f86d55cf616199404c05f5b0c5c41b17351baa02

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2022-49052 severity on Zeptric[![CVE-2022-49052](https://zeptric.io/badge/cve/CVE-2022-49052.svg)](https://zeptric.io/cve/CVE-2022-49052)