5.5

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

Analyzed
AliasesUBUNTU-CVE-2025-39763DEBIAN-CVE-2025-39763
Published 11-09-2025Last modified 23-05-2026

Vulnerability summary

CVE-2025-39763 is a medium (CVSS 5.5) vulnerability in linux. EPSS estimates a 0.16% chance of exploitation in the next 30 days, higher than 5.1% of scored vulnerabilities.

Priority
Routine

Not severe (CVSS 5.5, local access); no exploitation reported by the 5 checked sources

Source freshness unavailable

How is this decided?
CVSS score
5.5/10
010
Medium · v3.1 (NVD)
EPSS score
0.16%
0%100%
Low · 0.00 pp in 30 days
KEVNot listedNot listed by any tracked catalog.
RansomwareNot flaggedNo ransomware use recorded.
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 34 · Related 32
DLA-4499-1DSA-6163-1OPENSUSE-SU-2025:20081-1SUSE-SU-2025:03600-1SUSE-SU-2025:03614-1SUSE-SU-2025:03634-1

Timeline

  1. 11-09-2025
    PublishedVulnerability first disclosed.
  2. 23-05-2026
    Last modifiedVulnerability information updated.

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 ]

CVSS metrics

3 scores · 3 sources · 1 version

EPSS trend

Probability

0.16%

Chance of exploitation in the next 30 days

Percentile

5%

Versus all other CVEs

30-day change

No change 0.00 pp

From 0.16% on 04-10-2026

04-10-202603-11-2026

Known exploited

Compare KEV catalogs
CISA KEV

Not in the CISA KEV catalog.

ENISA CNW

Not in the ENISA CNW catalog.

CIRCL

Not in the CIRCL catalog.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

No weakness data has been published for this record.

Affected systems

Version check

Known conditions: local access, low-privilege account, no user interaction (CVSS vector). Other conditions: not stated in public data.

Ubuntu149 products
  • linuxAll versions (No fix recorded) | < 6.8.0-100.100
  • linux-allwinner-5.19All versions (No fix recorded)
  • linux-awsAll versions (No fix recorded) | < 6.8.0-1046.49
  • linux-aws-5.0All versions (No fix recorded)
  • linux-aws-5.11All versions (No fix recorded)
Linux2 products
  • linux≥ 8fcc4ae6faf8b455eeef00bc9ae70744e3b0f462, < 2fbc85da9ac9386bd89fcc94e0aadaea19d47784 | ≥ 8fcc4ae6faf8b455eeef00bc9ae70744e3b0f462, < 082735fbcdb6cd0cf20fbec94516ab2996f1cdd5 | ≥ 8fcc4ae6faf8b455eeef00bc9ae70744e3b0f462, < cfc9bc15bda6fd0c496cbe2c628564d4d7c332c1 | ≥ 8fcc4ae6faf8b455eeef00bc9ae70744e3b0f462, < af089e41811a1ad6a7b2b80e839a73ec4c3cecdd | ≥ 8fcc4ae6faf8b455eeef00bc9ae70744e3b0f462, < 3cb4f18797247985b0f51d5300f8cb6c78f343ea | ≥ 8fcc4ae6faf8b455eeef00bc9ae70744e3b0f462, < 79a5ae3c4c5eb7e38e0ebe4d6bf602d296080060 | af02933d59bd1621a48d8b0b331cca9e530ba14b | ≥ 5.4.69, < 5.5 | 5.8
  • linux_kernel< 6.6.103 | ≥ 6.7, < 6.12.43 | ≥ 6.13, < 6.15.11 | ≥ 6.16, < 6.16.2
Debian1 product
  • linux< 6.1.164-1 | < 6.12.43-1 | < 6.16.3-1

3 vendors · 152 products

References

27 links
Show all 27 references