x86/fred: Correct speculative safety in fred_extint()
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 |
|
|
In the Linux kernel, the following vulnerability has been resolved:
x86/fred: Correct speculative safety in fred_extint()
array_index_nospec() is no use if the result gets spilled to the stack, as it makes the believed safe-under-speculation value subject to memory predictions.
For all practical purposes, this means array_index_nospec() must be used in the expression that accesses the array.
As the code currently stands, it's the wrong side of irqentry_enter(), and 'index' is put into %ebp across the function call.
Remove the index variable and reposition array_index_nospec(), so it's calculated immediately before the array access.
From the CVE record · Linux
The Linux kernel's x86 FRED external interrupt handler applies array_index_nospec() too early, allowing its result to be spilled to the stack before an array access. This can undermine the intended speculative safety of that access during interrupt handling. The input does not establish an attacker capability, authentication requirement, or user-interaction requirement.
Engineers running Linux kernels with the affected x86 FRED interrupt-handling code should check their kernel versions against the vendor advisory; affected versions are not listed in the input.