Vulnerability · Published May 21, 2024 · Assigned by Linux

CVE-2023-52739Fix page corruption caused by racy check in __free_pages

High 7.8

In plain English

A high-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.3% (higher than 18% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)7.8High
Exploit odds (30 days)0.3%top 81.9% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: Fix page corruption caused by racy check in __free_pages When we upgraded our kernel, we started seeing some page corruption like the following consistently: BUG: Bad page state in process ganesha.nfsd pfn:1304ca page:0000000022261c55 refcount:0 mapcount:-128 mapping:0000000000000000 index:0x0 pfn:0x1304ca flags: 0x17ffffc0000000() raw: 0017ffffc0000000 ffff8a513ffd4c98 ffffeee24b35ec08 0000000000000000 raw: 0000000000000000 0000000000000001 00000000ffffff7f 0000000000000000 page dumped because: nonzero mapcount CPU: 0 PID: 15567 Comm: ganesha.nfsd Kdump: loaded Tainted: P B O 5.10.158-1.nutanix.20221209.el7.x86_64 #1 Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 04/05/2016 Call Trace: dump_stack+0x74/0x96 bad_page.cold+0x63/0x94 check_new_page_bad+0x6d/0x80 rmqueue+0x46e/0x970 get_page_from_freelist+0xcb/0x3f0 ? _cond_resched+0x19/0x40 __alloc_pages_nodemask+0x164/0x300 alloc_pages_current+0x87/0xf0 skb_page_frag_refill+0x84/0x110 ... Sometimes, it would also show up as corruption in the free list pointer and cause crashes. After bisecting the issue, we found the issue started from commit e320d3012d25 ("mm/page_alloc.c: fix freeing non-compound pages"): if (put_page_testzero(page)) free_the_page(page, order); else if (!PageHead(page)) while (order-- > 0) free_the_page(page + (1 << order), order); So the problem is the check PageHead is racy because at this point we already dropped our reference to the page. So even if we came in with compound page, the page can already be freed and PageHead can return false and we will end up freeing all the tail pages causing double free.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linux6.1.12-1DEBIAN-CVE-2023-52739
Debian:13linux6.1.12-1DEBIAN-CVE-2023-52739
Debian:14linux6.1.12-1DEBIAN-CVE-2023-52739
Ubuntu:22.04:LTSlinux5.15.0-72.79UBUNTU-CVE-2023-52739
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2023-52739
Ubuntu:22.04:LTSlinux-aws5.15.0-1036.40UBUNTU-CVE-2023-52739
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2023-52739
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2023-52739
Ubuntu:22.04:LTSlinux-azure5.15.0-1038.45UBUNTU-CVE-2023-52739
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2023-52739
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2023-52739
Ubuntu:22.04:LTSlinux-azure-fde5.15.0-1038.45.1UBUNTU-CVE-2023-52739
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2023-52739
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2023-52739
Ubuntu:22.04:LTSlinux-gcp5.15.0-1034.42UBUNTU-CVE-2023-52739
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2023-52739
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2023-52739
Ubuntu:22.04:LTSlinux-gke5.15.0-1033.38UBUNTU-CVE-2023-52739
Ubuntu:22.04:LTSlinux-gkeop5.15.0-1020.25UBUNTU-CVE-2023-52739
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2023-52739
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2023-52739
Ubuntu:22.04:LTSlinux-ibm5.15.0-1030.33UBUNTU-CVE-2023-52739
Ubuntu:22.04:LTSlinux-intel-iotg5.15.0-1030.35UBUNTU-CVE-2023-52739
Ubuntu:22.04:LTSlinux-kvm5.15.0-1033.38UBUNTU-CVE-2023-52739
Ubuntu:22.04:LTSlinux-lowlatency5.15.0-72.79UBUNTU-CVE-2023-52739
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2023-52739
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2023-52739
Ubuntu:22.04:LTSlinux-nvidia5.15.0-1025.25UBUNTU-CVE-2023-52739
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2023-52739
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2023-52739
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2023-52739
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2023-52739
Ubuntu:22.04:LTSlinux-oracle5.15.0-1035.41UBUNTU-CVE-2023-52739
Ubuntu:22.04:LTSlinux-raspi5.15.0-1029.31UBUNTU-CVE-2023-52739
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2023-52739
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2023-52739
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2023-52739
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2023-52739
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2023-52739
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2023-52739

Affected products (as reported)

VendorProductVersions
Linux Linux e320d3012d25b1fb5f3df4edb7bd44a1c362ec10 – before 0a626e27f984dfbe96bd8e4fd08f20a2ede3ea23e320d3012d25b1fb5f3df4edb7bd44a1c362ec10 – before 3af734f3eac6f70ef8e272a80da40544b9d0f2b5e320d3012d25b1fb5f3df4edb7bd44a1c362ec10 – before 3b4c045a98f53a8890a94bb5846a390c8e39e673e320d3012d25b1fb5f3df4edb7bd44a1c362ec10 – before 462a8e08e0e6287e5ce13187257edbf24213ed03830b103831a924a23af48562c4d274696e75ab4f5.9.2 – before 5.10
Linux Linux 5.10

References