In the Linux kernel, the following vulnerability has been resolved: acpi/apei/ghes: Use raw_spinlock_t for CXL CPER work locks The CXL CPER work… (CVE-2026-89589)
A deadlock vulnerability in the Linux kernel's ACPI APEI GHES component related to CXL CPER work locks has been resolved. The issue arises because the locking mechanism used spinlock_t with local interrupts enabled, which can cause deadlocks when an interrupt handler tries to acquire the same lock already held by the interrupted CPU. The fix involves switching to raw_spinlock_t and restructuring the registration and unregistration functions to prevent race conditions and stale work scheduling.
AI Analysis
Technical Summary
The vulnerability in the Linux kernel's ACPI APEI GHES subsystem involves improper use of spinlock_t for CXL CPER work locks. The registration and unregistration helpers acquire locks with spinlock guard() that leaves local interrupts enabled, while the interrupt handlers acquire the same locks with irqsave guard(). This mismatch can cause a deadlock if an interrupt arrives on a CPU holding the lock, as the IRQ handler spins waiting for the lock while the lock holder is preempted. The fix converts these locks to raw_spinlock_t, which is safe in hard IRQ context, and restructures the unregister functions to clear global pointers under lock before cancelling work, preventing scheduling on freed pointers. Additional safeguards like WARN_ONCE were added to detect double registrations.
Potential Impact
The vulnerability can cause a deadlock in the kernel when a CPU holding a spinlock is interrupted by a GHES error notification interrupt that tries to acquire the same lock. This deadlock can halt progress on the affected CPU, potentially impacting system stability and reliability. There is no indication of privilege escalation or data corruption from the provided information.
Mitigation Recommendations
A fix is available that converts the affected locks from spinlock_t to raw_spinlock_t and restructures the registration and unregistration logic to prevent deadlocks and race conditions. Users should apply the updated Linux kernel patches that include these changes. No additional mitigation steps are indicated or necessary beyond applying the official fix.
In the Linux kernel, the following vulnerability has been resolved: acpi/apei/ghes: Use raw_spinlock_t for CXL CPER work locks The CXL CPER work… (CVE-2026-89589)
Description
A deadlock vulnerability in the Linux kernel's ACPI APEI GHES component related to CXL CPER work locks has been resolved. The issue arises because the locking mechanism used spinlock_t with local interrupts enabled, which can cause deadlocks when an interrupt handler tries to acquire the same lock already held by the interrupted CPU. The fix involves switching to raw_spinlock_t and restructuring the registration and unregistration functions to prevent race conditions and stale work scheduling.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in the Linux kernel's ACPI APEI GHES subsystem involves improper use of spinlock_t for CXL CPER work locks. The registration and unregistration helpers acquire locks with spinlock guard() that leaves local interrupts enabled, while the interrupt handlers acquire the same locks with irqsave guard(). This mismatch can cause a deadlock if an interrupt arrives on a CPU holding the lock, as the IRQ handler spins waiting for the lock while the lock holder is preempted. The fix converts these locks to raw_spinlock_t, which is safe in hard IRQ context, and restructures the unregister functions to clear global pointers under lock before cancelling work, preventing scheduling on freed pointers. Additional safeguards like WARN_ONCE were added to detect double registrations.
Potential Impact
The vulnerability can cause a deadlock in the kernel when a CPU holding a spinlock is interrupted by a GHES error notification interrupt that tries to acquire the same lock. This deadlock can halt progress on the affected CPU, potentially impacting system stability and reliability. There is no indication of privilege escalation or data corruption from the provided information.
Mitigation Recommendations
A fix is available that converts the affected locks from spinlock_t to raw_spinlock_t and restructures the registration and unregistration logic to prevent deadlocks and race conditions. Users should apply the updated Linux kernel patches that include these changes. No additional mitigation steps are indicated or necessary beyond applying the official fix.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-9wp4-w6jg-245j
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-89589"]
Threat ID: 6aa4a00d55bf5e2cf5a86684
Added to database: 09/12/2026, 00:42:53 UTC
Last enriched: 09/12/2026, 01:03:47 UTC
Last updated: 09/12/2026, 01:03:47 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.