CVE-2024-50017: x86/mm/ident_map: Use gbpages only where full GB page should be mapped.
First published: Mon Oct 21 2024(Updated: )
In the Linux kernel, the following vulnerability has been resolved: x86/mm/ident_map: Use gbpages only where full GB page should be mapped. When ident_pud_init() uses only GB pages to create identity maps, large ranges of addresses not actually requested can be included in the resulting table; a 4K request will map a full GB. This can include a lot of extra address space past that requested, including areas marked reserved by the BIOS. That allows processor speculation into reserved regions, that on UV systems can cause system halts. Only use GB pages when map creation requests include the full GB page of space. Fall back to using smaller 2M pages when only portions of a GB page are included in the request. No attempt is made to coalesce mapping requests. If a request requires a map entry at the 2M (pmd) level, subsequent mapping requests within the same 1G region will also be at the pmd level, even if adjacent or overlapping such requests could have been combined to map a full GB page. Existing usage starts with larger regions and then adds smaller regions, so this should not have any great consequence.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Linux Kernel | <6.10.14 | |
| Linux Kernel | >=6.11<6.11.3 | |
| debian/linux | <=5.10.223-1<=5.10.226-1<=6.1.123-1<=6.1.128-1 | 6.12.12-1 6.12.15-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/d113f9723f2bfd9c6feeb899b8ddbee6b8a6e01f
- https://git.kernel.org/stable/c/d80a99892f7a992d103138fa4636b2c33abd6740
- https://git.kernel.org/stable/c/a23823098ab2c277c14fc110b97d8d5c83597195
- https://git.kernel.org/stable/c/cc31744a294584a36bf764a0ffa3255a8e69f036
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50017
- https://nvd.nist.gov/vuln/detail/CVE-2024-50017
- https://launchpad.net/bugs/cve/CVE-2024-50017
- https://security-tracker.debian.org/tracker/CVE-2024-50017
- https://ubuntu.com/security/CVE-2024-50017
- https://git.kernel.org/linus/cc31744a294584a36bf764a0ffa3255a8e69f036
Frequently Asked Questions
What is the severity of CVE-2024-50017?
CVE-2024-50017 has a medium severity rating due to its impact on memory mapping in the Linux kernel.
How do I fix CVE-2024-50017?
To fix CVE-2024-50017, upgrade your Linux kernel to version 6.10.14 or later, or 6.11.3 or later.
What systems are affected by CVE-2024-50017?
CVE-2024-50017 affects versions of the Linux kernel prior to 6.10.14 and from 6.11.0 to 6.11.3.
What is the impact of CVE-2024-50017?
The impact of CVE-2024-50017 includes potential vulnerabilities in memory management, which could lead to instability or unnecessary memory usage.
When was CVE-2024-50017 published?
CVE-2024-50017 was published in 2024 as part of ongoing security improvements in the Linux kernel.
- agent/title
- agent/type
- agent/first-publish-date
- agent/author
- agent/remedy
- agent/severity
- collector/mitre-cve
- source/MITRE
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/last-modified-date
- collector/usn-cve
- source/Ubuntu
- collector/launchpad-cve
- source/Launchpad
- collector/security-tracker-debian
- source/Debian
- agent/source
- agent/references
- agent/softwarecombine
- agent/tags
- agent/description
- agent/event
- vendor/linux
- canonical/linux kernel
- version/linux kernel/6.11
- package-manager/debian