CVE-2025-39763
Last modified
CVE-2025-39763 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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. EPSS estimates a 0.15% chance of exploitation in the next 30 days.
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 ]
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| 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 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2025-39763?
How severe is CVE-2025-39763?
How do I fix CVE-2025-39763?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-39758In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-39759In the Linux kernel, the following vulnerability has been re…7
- CVE-2025-3976A vulnerability was found in PHPGurukul COVID19 Testing Mana…9.8
- CVE-2025-39760In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2025-39761In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2025-39762In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-39764In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-39765In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-39766In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-39767In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-39768In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-39769In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2025-39763?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
