ACPI: APEI: send SIGBUS to current task if synchronous memory error not recovered
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 8fcc4ae6faf8b455eeef00bc9ae70744e3b0f462 · < 79a5ae3c4c5eb7e38e0ebe4d6bf602d296080060| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ACPI: APEI: send SIGBUS to current task if synchronous memory error not recovered
If a synchronous error is detected as a result of user-space process triggering a 2-bit uncorrected error, the CPU will take a synchronous error exception such as Synchronous External Abort (SEA) on Arm64. The kernel will queue a memory_failure() work which poisons the related page, unmaps the page, and then sends a SIGBUS to the process, so that a system wide panic can be avoided.
However, no memory_failure() work will be queued when abnormal synchronous errors occur. These errors can include situations like invalid PA, unexpected severity, no memory failure config support, invalid GUID section, etc. In such a case, the user-space process will trigger SEA again. This loop can potentially exceed the platform firmware threshold or even trigger a kernel hard lockup, leading to a system reboot.
Fix it by performing a force kill if no memory_failure() work is queued for synchronous errors.
[ rjw: Changelog edits ]
From the CVE record · Linux
The Linux kernel may fail to terminate a user-space process after an abnormal synchronous memory error when no memory_failure() work is queued. A local process triggering such an error can repeatedly cause synchronous exceptions, potentially leading to a kernel hard lockup and system reboot. The input does not specify whether authentication beyond running a local process is needed.
Engineers running the Linux kernel should check their deployments; affected versions are not specified.