CVE-2024-40914mm/huge_memory: don't unpoison huge_zero_folio
- 5.5MediumCVSS base score
- 0.28%Exploitation in 30 daysEPSS · top 80% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: mm/huge_memory: don't unpoison huge_zero_folio When I did memory failure tests recently, below panic occurs: kernel BUG at include/linux/mm.h:1135! invalid opcode: 0000 [#1] PREEMPT SMP NOPTI CPU: 9 PID: 137 Comm: kswapd1 Not tainted 6.9.0-rc4-00491-gd5ce28f156fe-dirty #14 RIP: 0010:shrink_huge_zero_page_scan+0x168/0x1a0 RSP: 0018:ffff9933c6c57bd0 EFLAGS: 00000246 RAX: 000000000000003e RBX: 0000000000000000 RCX: ffff88f61fc5c9c8 RDX: 0000000000000000 RSI: 0000000000000027 RDI: ffff88f61fc5c9c0 RBP: ffffcd7c446b0000 R08: ffffffff9a9405f0 R09: 0000000000005492 R10: 00000000000030ea R11: ffffffff9a9405f0 R12: 0000000000000000 R13: 0000000000000000 R14: 0000000000000000 R15: ffff88e703c4ac00 FS: 0000000000000000(0000) GS:ffff88f61fc40000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000055f4da6e9878 CR3: 0000000c71048000 CR4: 00000000000006f0 Call Trace: <TASK> do_shrink_slab+0x14f/0x6a0 shrink_slab+0xca/0x8c0 shrink_node+0x2d0/0x7d0 balance_pgdat+0x33a/0x720 kswapd+0x1f3/0x410 kthread+0xd5/0x100 ret_from_fork+0x2f/0x50 ret_from_fork_asm+0x1a/0x30 </TASK> Modules linked in: mce_inject hwpoison_inject ---[ end trace 0000000000000000 ]--- RIP: 0010:shrink_huge_zero_page_scan+0x168/0x1a0 RSP: 0018:ffff9933c6c57bd0 EFLAGS: 00000246 RAX: 000000000000003e RBX: 0000000000000000 RCX: ffff88f61fc5c9c8 RDX: 0000000000000000 RSI: 0000000000000027 RDI: ffff88f61fc5c9c0 RBP: ffffcd7c446b0000 R08: ffffffff9a9405f0 R09: 0000000000005492 R10: 00000000000030ea R11: ffffffff9a9405f0 R12: 0000000000000000 R13: 0000000000000000 R14: 0000000000000000 R15: ffff88e703c4ac00 FS: 0000000000000000(0000) GS:ffff88f61fc40000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000055f4da6e9878 CR3: 0000000c71048000 CR4: 00000000000006f0 The root cause is that HWPoison flag will be set for huge_zero_folio without increasing the folio refcnt. But then unpoison_memory() will decrease the folio refcnt unexpectedly as it appears like a successfully hwpoisoned folio leading to VM_BUG_ON_PAGE(page_ref_count(page) == 0) when releasing huge_zero_folio. Skip unpoisoning huge_zero_folio in unpoison_memory() to fix this issue. We're not prepared to unpoison huge_zero_folio yet.
Timeline
ID reserved
By Linux
Published
- 23 months later
· 23 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Modified | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.28% · top 80% of all CVEs (14 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected f8f836100fff594cea8a0a027affb9d5520f09a7 – < 688bb46ad339497b5b7f527b6636d2afe04b46af
- affected 478d134e9506c7e9bfe2830ed03dd85e97966313 – < b2494506f30675245a3e6787281f79601af087bf
- affected 478d134e9506c7e9bfe2830ed03dd85e97966313 – < 0d73477af964dbd7396163a13817baf13940bca9
- affected 478d134e9506c7e9bfe2830ed03dd85e97966313 – < d72b7711919de49d92a67dfc844a6cf4c23dd794
- affected 478d134e9506c7e9bfe2830ed03dd85e97966313 – < fe6f86f4b40855a130a19aa589f9ba7f650423f4
- affected 13d9b8cd12f37d133b07ea5b323583e8a0c6b738
- affected 5.15.41 – < 5.15.162
- affected 5.17.9 – < 5.18
- affected 5.18
- unaffected < 5.18
- unaffected 5.15.162 – ≤ 5.15.*
- unaffected 6.1.95 – ≤ 6.1.*
- unaffected 6.6.35 – ≤ 6.6.*
- unaffected 6.9.6 – ≤ 6.9.*
- unaffected 6.10 – ≤ *
References
References6
- https://git.kernel.org/stable/c/688bb46ad339497b5b7f527b6636d2afe04b46af (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/b2494506f30675245a3e6787281f79601af087bf (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/0d73477af964dbd7396163a13817baf13940bca9 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/d72b7711919de49d92a67dfc844a6cf4c23dd794 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/fe6f86f4b40855a130a19aa589f9ba7f650423f4 (opens in a new tab)x_transferred
- https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2024-38725 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2024-40914)Record last updated .