Answer in brief
CVE-2024-50017 records a Unknown severity vulnerability in x86/mm/ident_map: Use gbpages only where full GB page should be mapped.. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=66aad4fdf2bf0af29c7decb4433dc5ec6c7c5451 <cb2555fb0223edac9e7820f16de17ae04a39ad39 || >=66aad4fdf2bf0af29c7decb4433dc5ec6c7c5451 <fe9bab1d6441ed49dc3dd0acce4c2215e8d85447 || >=66aad4fdf2bf0af29c7decb4433dc5ec6c7c5451 <d113f9723f2bfd9c6feeb899b8ddbee6b8a6e01f || >=66aad4fdf2bf0af29c7decb4433dc5ec6c7c5451 <d80a99892f7a992d103138fa4636b2c33abd6740 || >=66aad4fdf2bf0af29c7decb4433dc5ec6c7c5451 <a23823098ab2c277c14fc110b97d8d5c83597195 || >=66aad4fdf2bf0af29c7decb4433dc5ec6c7c5451 <cc31744a294584a36bf764a0ffa3255a8e69f036 | cb2555fb0223edac9e7820f16de17ae04a39ad39, fe9bab1d6441ed49dc3dd0acce4c2215e8d85447, d113f9723f2bfd9c6feeb899b8ddbee6b8a6e01f, d80a99892f7a992d103138fa4636b2c33abd6740, a23823098ab2c277c14fc110b97d8d5c83597195, cc31744a294584a36bf764a0ffa3255a8e69f036 |
| Linux/Linuxgeneric | 4.12 | Not reported |
Published upstream
Oct 21, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 14, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 14, 2026
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.
Quoted source text, attributed separately from HOL analysis.