CVE-2025-39763: Linux kernel · ACPI: APEI: send SIGBUS to current task if synchronous memory error not recovered
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in cfc9bc15bda6fd0c496cbe2c628564d4d7c332c1 : patch Linux kernel soon.
Data as of 5 Nov 2026, 21:47 UTC
Rated High by Threat Radar's AI analysis · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-05.
- Patch
- Available – fixed in cfc9bc15bda6fd0c496cbe2c628564d4d7c332c1, af089e41811a1ad6a7b2b80e839a73ec4c3cecdd, 082735fbcdb6cd0cf20fbec94516ab2996f1cdd5 +4
Exploitation evidence
Disclosed: evidence found.
CVE published 11 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix is available in Linux kernel version 5.5 and later, which forcefully kills the affected process when no memory_failure() work is queued for synchronous errors. Users should upgrade to version 5.5 or later to remediate this issue.
Description
A vulnerability in the Linux kernel's ACPI APEI subsystem could cause a system reboot due to a kernel hard lockup triggered by abnormal synchronous memory errors. When such errors occur and no memory_failure() work is queued, the user-space process may repeatedly trigger synchronous external aborts, potentially exceeding firmware thresholds. The issue affects Linux kernel versions >=5.4.69 <5.5 and version 5.8. The fix involves forcefully killing the affected process if no memory_failure() work is queued, preventing the error loop and system instability.
References
- git.kernel.org/stable/c/2fbc85da9ac9386bd89fcc94e0aadaea19d47784 (opens in a new tab)
- git.kernel.org/stable/c/082735fbcdb6cd0cf20fbec94516ab2996f1cdd5 (opens in a new tab)
- git.kernel.org/stable/c/cfc9bc15bda6fd0c496cbe2c628564d4d7c332c1 (opens in a new tab)
- git.kernel.org/stable/c/af089e41811a1ad6a7b2b80e839a73ec4c3cecdd (opens in a new tab)
- git.kernel.org/stable/c/3cb4f18797247985b0f51d5300f8cb6c78f343ea (opens in a new tab)
- git.kernel.org/stable/c/79a5ae3c4c5eb7e38e0ebe4d6bf602d296080060 (opens in a new tab)