Medium 5.5Published Sep 11, 2025

CVE-2025-39763ACPI: APEI: send SIGBUS to current task if synchronous memory error not recovered

Updated under an hour ago (Oct 27, 2026, 10:10 PM ET)

Does this affect you?

It affects Linux and 1 other product. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for Linux

Exploited in the last 30 days

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 ]

CVSS: 5.5 MEDIUM (v3.1, NVD)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness (CWE): Not given
Known exploited: Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days): Not loaded for this CVE
Assigned by: Linux
NVD analysis: Analyzed
Record last updated: May 23, 2026
First seen by InfoSec Signals: Oct 19, 2026

Affected products

Affected products

Linux Linux linux:linux (from the name)	8fcc4ae6faf8b455eeef00bc9ae70744e3b0f462 builds before 2fbc85da9ac9386bd89fcc94e0aadaea19d47784; from 8fcc4ae6faf8b455eeef00bc9ae70744e3b0f462 before 082735fbcdb6cd0cf20fbec94516ab2996f1cdd5; from 8fcc4ae6faf8b455eeef00bc9ae70744e3b0f462 before cfc9bc15bda6fd0c496cbe2c628564d4d7c332c1; from 8fcc4ae6faf8b455eeef00bc9ae70744e3b0f462 before af089e41811a1ad6a7b2b80e839a73ec4c3cecdd; 8fcc4ae6faf8b455eeef00bc9ae70744e3b0f462 builds before 3cb4f18797247985b0f51d5300f8cb6c78f343ea; from 8fcc4ae6faf8b455eeef00bc9ae70744e3b0f462 before 79a5ae3c4c5eb7e38e0ebe4d6bf602d296080060; af02933d59bd1621a48d8b0b331cca9e530ba14b; from 5.4.69 before 5.5	CNA record
linux linux_kernel linux:linux_kernel	before 6.6.103; from 6.7 before 6.12.43; from 6.13 before 6.15.11; from 6.16 before 6.16.2	NVD

References

References

https://git.kernel.org/stable/c/2fbc85da9ac9386bd89fcc94e0aadaea19d47784	patch
https://git.kernel.org/stable/c/082735fbcdb6cd0cf20fbec94516ab2996f1cdd5	patch
https://git.kernel.org/stable/c/cfc9bc15bda6fd0c496cbe2c628564d4d7c332c1	patch
https://git.kernel.org/stable/c/af089e41811a1ad6a7b2b80e839a73ec4c3cecdd	patch
https://git.kernel.org/stable/c/3cb4f18797247985b0f51d5300f8cb6c78f343ea	patch
https://git.kernel.org/stable/c/79a5ae3c4c5eb7e38e0ebe4d6bf602d296080060	patch

The CVE record on cve.org NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.