x86/mm/ident_map: Use gbpages only where full GB page should be mapped.
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 66aad4fdf2bf0af29c7decb4433dc5ec6c7c5451 · < cc31744a294584a36bf764a0ffa3255a8e69f036| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel can map a full GB when an identity-map request covers only a small portion of it, potentially including BIOS-reserved regions. On UV systems, processor speculation into those regions can cause system halts; the input does not describe an attacker path, authentication requirements, or user interaction.
Engineers running the Linux kernel on UV systems should check their versions; affected versions were not provided.