powerpc/32: Fix hardlockup on vmap stack overflow
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
5.10
|
In the Linux kernel, the following vulnerability has been resolved:
powerpc/32: Fix hardlockup on vmap stack overflow
Since the commit c118c7303ad5 ("powerpc/32: Fix vmap stack - Do not activate MMU before reading task struct") a vmap stack overflow results in a hard lockup. This is because emergency_ctx is still addressed with its virtual address allthough data MMU is not active anymore at that time.
Fix it by using a physical address instead.
From the CVE record · Linux
The Linux kernel’s powerpc/32 vmap stack handling can hard lock up when a stack overflow occurs. At that point, it accesses emergency_ctx through a virtual address even though the data MMU is no longer active. The input does not specify whether an attacker can trigger the overflow or what access would be required.
Engineers running Linux kernels on powerpc/32 should check their affected versions against the vendor advisory; no version range is provided.