CVE-2024-57881: mm/page_alloc: don't call pfn_to_page() on possibly non-existent PFN in split_large_buddy()
First published: Sat Jan 11 2025(Updated: )
In the Linux kernel, the following vulnerability has been resolved: mm/page_alloc: don't call pfn_to_page() on possibly non-existent PFN in split_large_buddy() In split_large_buddy(), we might call pfn_to_page() on a PFN that might not exist. In corner cases, such as when freeing the highest pageblock in the last memory section, this could result with CONFIG_SPARSEMEM && !CONFIG_SPARSEMEM_EXTREME in __pfn_to_section() returning NULL and and __section_mem_map_addr() dereferencing that NULL pointer. Let's fix it, and avoid doing a pfn_to_page() call for the first iteration, where we already have the page. So far this was found by code inspection, but let's just CC stable as the fix is easy.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Linux Kernel | >=6.10<6.12.7 | |
| Linux Kernel | =6.13-rc1 | |
| Linux Kernel | =6.13-rc2 | |
| Linux Kernel | =6.13-rc3 | |
| debian/linux | 5.10.223-1 5.10.234-1 6.1.129-1 6.1.128-1 6.12.20-1 6.12.21-1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://git.kernel.org/stable/c/4234ca9884bcae9e48ed38652d91696ad5cd591d
- https://git.kernel.org/stable/c/faeec8e23c10bd30e8aa759a2eb3018dae00f924
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-57881
- https://nvd.nist.gov/vuln/detail/CVE-2024-57881
- https://launchpad.net/bugs/cve/CVE-2024-57881
- https://security-tracker.debian.org/tracker/CVE-2024-57881
- https://ubuntu.com/security/CVE-2024-57881
- https://git.kernel.org/linus/faeec8e23c10bd30e8aa759a2eb3018dae00f924
Frequently Asked Questions
What is the severity of CVE-2024-57881?
CVE-2024-57881 has a moderate severity level due to potential issues arising from calling pfn_to_page() on non-existent PFNs.
How do I fix CVE-2024-57881?
To fix CVE-2024-57881, ensure your Linux kernel is updated to version 6.12.8 or later.
Which versions of the Linux kernel are affected by CVE-2024-57881?
CVE-2024-57881 affects Linux kernel versions between 6.10 and 6.12.7, as well as 6.13 release candidates.
What is the impact of CVE-2024-57881 on system security?
The impact of CVE-2024-57881 could lead to system instability or security vulnerabilities during memory management.
Where can I find more details about CVE-2024-57881?
Details about CVE-2024-57881 can be found in the changelogs and announcements related to the Linux kernel updates.
- agent/title
- agent/type
- agent/first-publish-date
- agent/author
- agent/weakness
- agent/remedy
- agent/severity
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- collector/usn-cve
- source/Ubuntu
- collector/launchpad-cve
- source/Launchpad
- agent/references
- agent/description
- agent/source
- agent/softwarecombine
- agent/tags
- agent/event
- collector/nvd-cve
- collector/security-tracker-debian
- source/Debian
- vendor/linux
- canonical/linux kernel
- version/linux kernel/6.10
- version/linux kernel/6.13-rc1
- version/linux kernel/6.13-rc2
- version/linux kernel/6.13-rc3
- package-manager/debian