x86/mm: Fix pti_clone_pgtable() alignment assumption
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 16a3fe634f6a568c6234b8747e5d50487fed3526 · < ca07aab70dd3b5e7fddb62d7a6ecd7a7d6d0b2ed| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
x86/mm: Fix pti_clone_pgtable() alignment assumption
Guenter reported dodgy crashes on an i386-nosmp build using GCC-11 that had the form of endless traps until entry stack exhaust and then #DF from the stack guard.
It turned out that pti_clone_pgtable() had alignment assumptions on the start address, notably it hard assumes start is PMD aligned. This is true on x86_64, but very much not true on i386.
These assumptions can cause the end condition to malfunction, leading to a 'short' clone. Guess what happens when the user mapping has a short copy of the entry text?
Use the correct increment form for addr to avoid alignment assumptions.
From the CVE record · Linux
The Linux kernel’s pti_clone_pgtable() assumes an alignment that does not hold on i386. This can produce a short copy of entry text in the user mapping and cause repeated traps and a crash. The input does not establish an attacker path, authentication requirements, or user interaction.
Engineers running the Linux kernel on i386 should check their builds, particularly i386-nosmp builds using GCC 11; affected versions are not specified.