Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

MediumCVSS 5.5 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 082735fbcdb6cd0cf20fbec94516ab2996f1cdd5, 2fbc85da9ac9386bd89fcc94e0aadaea19d47784, 3cb4f18797247985b0f51d5300f8cb6c78f343ea; azl3 kernel 6.6.96.2-2 on Azure Linux 3.0 6.6.104.2-1; cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0 Release Notes.

Low priority for now. Upgrade to Linux Linux 082735fbcdb6cd0cf20fbec94516ab2996f1cdd5, 2fbc85da9ac9386bd89fcc94e0aadaea19d47784, 3cb4f18797247985b0f51d5300f8cb6c78f343ea; azl3 kernel 6.6.96.2-2 on Azure Linux 3.0 6.6.104.2-1; cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0 Release Notes or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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 ]

Published
Sep 11, 2025
Updated
Nov 5, 2026
EPSS
0.1% · 5th percentile
CWE
—

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-39763

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • af02933d59bd1621a48d8b0b331cca9e530ba14b, 5.8affected
    • 8fcc4ae6faf8b455eeef00bc9ae70744e3b0f462 and later · before 2fbc85da9ac9386bd89fcc94e0aadaea19d47784affected · git
    • 8fcc4ae6faf8b455eeef00bc9ae70744e3b0f462 and later · before 082735fbcdb6cd0cf20fbec94516ab2996f1cdd5affected · git
    • 8fcc4ae6faf8b455eeef00bc9ae70744e3b0f462 and later · before cfc9bc15bda6fd0c496cbe2c628564d4d7c332c1affected · git
    • 8fcc4ae6faf8b455eeef00bc9ae70744e3b0f462 and later · before af089e41811a1ad6a7b2b80e839a73ec4c3cecddaffected · git
    • 8fcc4ae6faf8b455eeef00bc9ae70744e3b0f462 and later · before 3cb4f18797247985b0f51d5300f8cb6c78f343eaaffected · git
    • 8fcc4ae6faf8b455eeef00bc9ae70744e3b0f462 and later · before 79a5ae3c4c5eb7e38e0ebe4d6bf602d296080060affected · git
    • 5.4.69 and later · before 5.5affected · semver
    • before 5.8not affected · semver
    • 6.1.164 and later · up to and including 6.1.*not affected · semver
Affected versions · NVD (4)

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernelbefore 6.6.103
  • linux linux kernel6.7 and later · before 6.12.43
  • linux linux kernel6.13 and later · before 6.15.11
  • linux linux kernel6.16 and later · before 6.16.2

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:11linux-6.1before 6.1.164-1~deb11u16.1.164-1~deb11u1
Debian:12linuxbefore 6.1.164-16.1.164-1
Debian:13linuxbefore 6.12.43-16.12.43-1
Debian:14linuxbefore 6.16.3-16.16.3-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2025-39761Sep 11, 2025 · wifi: ath12k: Decrement TID on RX peer frag setup error handling
    28Monitor
  • ← EarlierCVE-2025-39762Sep 11, 2025 · drm/amd/display: add null check
    22Monitor
  • Later →CVE-2025-39764Sep 11, 2025 · netfilter: ctnetlink: remove refcounting in expectation dumpers
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux082735fbcdb6cd0cf20fbec94516ab2996f1cdd5Vendor (CNA)
Linux Linux2fbc85da9ac9386bd89fcc94e0aadaea19d47784Vendor (CNA)
Linux Linux3cb4f18797247985b0f51d5300f8cb6c78f343eaVendor (CNA)
Linux Linux5.5Vendor (CNA)
Linux Linux79a5ae3c4c5eb7e38e0ebe4d6bf602d296080060Vendor (CNA)
Linux Linuxaf089e41811a1ad6a7b2b80e839a73ec4c3cecddVendor (CNA)
Linux Linuxcfc9bc15bda6fd0c496cbe2c628564d4d7c332c1Vendor (CNA)
azl3 kernel 6.6.96.2-2 on Azure Linux 3.06.6.104.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0Release NotesMicrosoft (MSRC)
debian:linux6.1.164-1 · Debian:12Package registry (OSV)
debian:linux-6.16.1.164-1~deb11u1 · Debian:11Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

Show all references (5 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records