In the Linux kernel, the following vulnerability has been resolved:
mm/util: don't read __page_2 for order-1 folios in snapshot_page()
snapshot_page() currently reads __page_2 after checking nr_pages > 1, but it should only do so when nr_pages > 2.
If an order-1 folio is allocated at the end of a vmemmap section, __page_2 will not exist and reading it will cause a fault.
During DLPAR memory remove on a 22 TB ppc64le LPAR, snapshot_page() oopsed on the page isolation path while reading an order-1 folio's __page_2 from an adjacent absent section (unmapped vmemmap).
Fix this to avoid reading memmap that doesn't exist (e.g., a vmemmap hole).
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Amazon_linux_2023 | — | Upgrade kernel6.18-toolsUpgrade kernel6.18-develUpgrade kernel6.18-modules-extra-commonUpgrade kernel6.18Upgrade python3-perf6.18Upgrade perf6.18Upgrade kernel6.18-debuginfo-common-x86_64Upgrade microvm-kernel6.18Upgrade kernel6.18-tools-develUpgrade kernel6.18-modules-extraUpgrade kernel6.18-headersUpgrade kernel6.18-debuginfoUpgrade bpftool6.18Upgrade kernel-livepatch-6.18.44-99.149Upgrade perf6.18-debuginfoUpgrade kernel6.18-tools-debuginfoUpgrade python3-perf6.18-debuginfoUpgrade kernel6.18-debuginfo-common-aarch64Upgrade bpftool6.18-debuginfo | Sep 30, 2026 | Aug 28, 2026 |
| Redhat_linux | — | No solution exists | Sep 3, 2026 | Aug 28, 2026 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub