CVE-2025-39763: ACPI: APEI: send SIGBUS to current task if synchronous memory error not recovered
Published Sep 11, 2025
·Updated
ACPI: APEI: send SIGBUS to current task if synchronous memory error not recovered
Affected Software
8 affected componentsFixes available
Linux Linux kernel
Microsoft azl3 kernel 6.6.96.2-2
Microsoft cbl2 kernel 5.15.186.1-1
Linux Linux kernel<6.6.103
Linux Linux kernel>=6.7<6.12.43
Linux Linux kernel>=6.13<6.15.11
Linux Linux kernel>=6.16<6.16.2
Microsoft azl3 kernel 6.6.96.2-2<6.6.104.2-1
6.6.104.2-1
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 6.6.104.2-1
Event History
Sep 11, 2025
CVE Published
via MITRE·04:52 PM
Data Sourced
via MITRE·04:52 PM
Description
Data Sourced
via NVD·05:15 PM
RemedyDescriptionSeverityAffected Software
Sep 13, 2025
Data Sourced
via Microsoft·01:03 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·08:03 AM
DescriptionSeverity
Updated
via Microsoft·08:03 AM
Affected Software
Frequently Asked Questions
1
What is the severity of CVE-2025-39763?
CVE-2025-39763 has a medium severity due to potential disruptions caused by synchronous memory errors.
2
How do I fix CVE-2025-39763?
To fix CVE-2025-39763, update to the latest version of the Linux kernel where the vulnerability has been addressed.
3
What are the impacts of CVE-2025-39763?
CVE-2025-39763 can lead to a SIGBUS signal being sent to the current task, potentially causing application crashes.
4
Which systems are affected by CVE-2025-39763?
CVE-2025-39763 affects systems running vulnerable versions of the Linux kernel.
5
Is CVE-2025-39763 being actively exploited?
As of now, there are no known active exploits for CVE-2025-39763, but it's advisable to apply patches promptly.