{"cve":"CVE-2026-89589","nvd":{"published":"2026-09-11T20:19:43.437","modified":"2026-10-19T09:17:55.210","status":"Received","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nacpi/apei/ghes: Use raw_spinlock_t for CXL CPER work locks\n\nThe CXL CPER work registration and unregistration helpers acquire\ncxl_cper_work_lock and cxl_cper_prot_err_work_lock with a spinlock\nguard(), which leaves local interrupts enabled. The corresponding post\npaths (cxl_cper_post_event(), cxl_cper_post_prot_err()) execute in hard\nIRQ context (they are called from the GHES error notification path) and\nacquire the same locks with an irqsave guard().\n\nIf a CPU is holding one of these locks via a spinlock guard() when a GHES\ninterrupt arrives on the same CPU, the IRQ handler spins on the held lock\nwaiting for it to release, while the lock holder is preempted by the IRQ.\nThe result is a deadlock.\n\nConvert both locks from spinlock_t to raw_spinlock_t and use guard() at\nall call sites. On PREEMPT_RT kernels spinlock_t is backed by rt_mutex and\nsleeping from hard IRQ context is not permitted; raw_spinlock_t is safe in\nboth contexts.\n\nAdd WARN_ONCE to both register functions to surface double-registration\nbugs at runtime.\n\nRestructure both unregister functions to clear the global work pointer\nunder the lock before calling cancel_work_sync(), closing the window\nwhere a CPER interrupt could schedule work on a pointer about to be\nfreed. Add kfifo_reset() after cancel_work_sync() so stale entries\nare not replayed on next module load.\n\nBoth kfifos are single-consumer: only one work_struct is registered at\na time, enforced by the WARN_ONCE guard in the register functions.\nkfifo_reset() is safe outside the lock because cancel_work_sync() has\nalready quiesced the consumer, and no new consumer can register until\nthe current module exit completes and a fresh module init runs.\n\nRemove the redundant cancel_work_sync() call from cxl_ras_exit() and\ncxl_pci_driver_exit(). The CPER unregister functions now quiesce\nthe work internally.","cvss_v4":null,"cvss_v3":null,"cwes":[],"references":["https://git.kernel.org/stable/c/0e25382b05de48d09b243d3d447d236a6d735bc2","https://git.kernel.org/stable/c/6625ca499c3131ef63be3215f8f942d7a097ea3a","https://git.kernel.org/stable/c/c735dbce7ad03df708bf22ec964f67e43cbc823a","https://git.kernel.org/stable/c/cbc27a4302a1feb0ff77c1755021837a738b0ce9"],"products":[],"source":"nvd","synced_at":"2026-10-19T22:53:43.293028046+00:00"},"epss":{"cve":"CVE-2026-89589","score":0.00175,"percentile":0.06993,"date":"2026-10-25"},"kev":null,"osv":[],"attribution":["This product uses the NVD API but is not endorsed or certified by the NVD.","EPSS scores: FIRST Exploit Prediction Scoring System, https://www.first.org/epss","Known exploited vulnerabilities: CISA Known Exploited Vulnerabilities Catalog, https://www.cisa.gov/known-exploited-vulnerabilities-catalog","Package advisories: OSV (https://osv.dev), from the GitHub Advisory Database, PyPA, Go, RustSec and other ecosystem databases, under CC-BY 4.0 or CC0","CVE records: the CVE Program's CVE List (https://www.cve.org), under its terms of use (https://www.cve.org/Legal/TermsOfUse). CVE is a registered trademark of The MITRE Corporation; this product is not affiliated with the CVE Program."]}