powerpc/64s/interrupt: Fix interrupt exit race with security mitigation switch
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.15.946.1.126.2In the Linux kernel, the following vulnerability has been resolved:
powerpc/64s/interrupt: Fix interrupt exit race with security mitigation switch
The RFI and STF security mitigation options can flip the interrupt_exit_not_reentrant static branch condition concurrently with the interrupt exit code which tests that branch.
Interrupt exit tests this condition to set MSR[EE|RI] for exit, then again in the case a soft-masked interrupt is found pending, to recover the MSR so the interrupt can be replayed before attempting to exit again. If the condition changes between these two tests, the MSR and irq soft-mask state will become corrupted, leading to warnings and possible crashes. For example, if the branch is initially true then false, MSR[EE] will be 0 but PACA_IRQ_HARD_DIS clear and EE may not get enabled, leading to warnings in irq_64.c.
From the CVE record · Linux
A race in the Linux kernel’s powerpc/64s interrupt exit code can occur when RFI or STF security mitigation options change while an interrupt is exiting. This can corrupt interrupt state, causing warnings and possible crashes. The input does not specify an attacker, access requirements, or user interaction.
Engineers running the Linux kernel on powerpc/64s should check their versions; affected versions are not specified.