powerpc/64s: Fix crashes when toggling entry flush barrier
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ f79643787e0a0762d2409b7b8334e83f22d85695 · < d2e3590ca39ccfd8a5a46d8c7f095cb6c7b9ae92| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
powerpc/64s: Fix crashes when toggling entry flush barrier
The entry flush mitigation can be enabled/disabled at runtime via a debugfs file (entry_flush), which causes the kernel to patch itself to enable/disable the relevant mitigations.
However depending on which mitigation we're using, it may not be safe to do that patching while other CPUs are active. For example the following crash:
sleeper[15639]: segfault (11) at c000000000004c20 nip c000000000004c20 lr c000000000004c20
Shows that we returned to userspace with a corrupted LR that points into the kernel, due to executing the partially patched call to the fallback entry flush (ie. we missed the LR restore).
Fix it by doing the patching under stop machine. The CPUs that aren't doing the patching will be spinning in the core of the stop machine logic. That is currently sufficient for our purposes, because none of the patching we do is to that code or anywhere in the vicinity.
From the CVE record · Linux
On powerpc/64s, toggling the entry_flush debugfs setting can crash the Linux kernel if it patches the mitigation while other CPUs are active. Someone able to toggle that setting could trigger the crash; the input does not specify the access required.
Operators running Linux kernels on powerpc/64s should check whether their kernel is affected; affected versions are not specified.