Linux kernel register corruption in s390 kprobes exception handling
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 |
|
|
6.18.617.3.27.4-rc1In the Linux kernel, the following vulnerability has been resolved:
s390/kprobes: Prevent kprobes on instructions with exception table entry
The mvcos exception handler ex_handler_ua_mvcos() decodes the faulting instruction, assuming it is an mvcos instruction. In case the instruction is kprobed the decoded instruction is a breakpoint instruction instead, which leads to incorrect instruction decoding and potential register corruption.
Fix this by simply preventing to set a kprobe on such instructions, similar like arm64 is doing it.
From the CVE record · Linux
On s390, placing a kprobe on an instruction with an exception table entry can cause the mvcos exception handler to decode a breakpoint instead of the faulting instruction, potentially corrupting registers. The input does not specify an attacker path, authentication requirements, or user interaction.
Engineers running the Linux kernel on s390 should check their deployments; affected versions are not specified.