CVE-2025-39763ACPI: APEI: send SIGBUS to current task if synchronous memory error not recovered
- 5.5MediumCVSS base score
- 0.17%Exploitation in 30 daysEPSS · top 94% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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 ]
Timeline
ID reserved
By Linux
- 5 months later
· 5 months later
Published
- 14 months later
· 14 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.17% · top 94% of all CVEs (18 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected 8fcc4ae6faf8b455eeef00bc9ae70744e3b0f462 – < 2fbc85da9ac9386bd89fcc94e0aadaea19d47784
- affected 8fcc4ae6faf8b455eeef00bc9ae70744e3b0f462 – < 082735fbcdb6cd0cf20fbec94516ab2996f1cdd5
- affected 8fcc4ae6faf8b455eeef00bc9ae70744e3b0f462 – < cfc9bc15bda6fd0c496cbe2c628564d4d7c332c1
- affected 8fcc4ae6faf8b455eeef00bc9ae70744e3b0f462 – < af089e41811a1ad6a7b2b80e839a73ec4c3cecdd
- affected 8fcc4ae6faf8b455eeef00bc9ae70744e3b0f462 – < 3cb4f18797247985b0f51d5300f8cb6c78f343ea
- affected 8fcc4ae6faf8b455eeef00bc9ae70744e3b0f462 – < 79a5ae3c4c5eb7e38e0ebe4d6bf602d296080060
- affected af02933d59bd1621a48d8b0b331cca9e530ba14b
- affected 5.4.69 – < 5.5
- affected 5.8
- unaffected < 5.8
- unaffected 6.1.164 – ≤ 6.1.*
- unaffected 6.6.103 – ≤ 6.6.*
- unaffected 6.12.43 – ≤ 6.12.*
- unaffected 6.15.11 – ≤ 6.15.*
- unaffected 6.16.2 – ≤ 6.16.*
- unaffected 6.17 – ≤ *
References
References6
- https://git.kernel.org/stable/c/2fbc85da9ac9386bd89fcc94e0aadaea19d47784 (opens in a new tab)
- https://git.kernel.org/stable/c/082735fbcdb6cd0cf20fbec94516ab2996f1cdd5 (opens in a new tab)
- https://git.kernel.org/stable/c/cfc9bc15bda6fd0c496cbe2c628564d4d7c332c1 (opens in a new tab)
- https://git.kernel.org/stable/c/af089e41811a1ad6a7b2b80e839a73ec4c3cecdd (opens in a new tab)
- https://git.kernel.org/stable/c/3cb4f18797247985b0f51d5300f8cb6c78f343ea (opens in a new tab)
- https://git.kernel.org/stable/c/79a5ae3c4c5eb7e38e0ebe4d6bf602d296080060 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-28949 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2025-39763)Record last updated .