{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89589 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89589 is a vulnerability in Linux, published on 11 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-89589 and fix it if it is affected.\n\nWhat it is: CVE-2026-89589 is a vulnerability in Linux, published on 11 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-89589 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-89589/ (Markdown: https://insights.sbomify.com/CVE-2026-89589/index.md)","id":"CVE-2026-89589","markdown":"https://insights.sbomify.com/CVE-2026-89589/index.md","name":"CVE-2026-89589","record":{"aliases":["BELL-CVE-2026-89589","DEBIAN-CVE-2026-89589","GHSA-9wp4-w6jg-245j","UBUNTU-CVE-2026-89589"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A race condition in the Linux kernel CXL CPER handling can cause a deadlock when a GHES interrupt occurs while holding a spinlock, leading to system denial of service.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"acpi/apei/ghes: Use raw_spinlock_t for CXL CPER work locks","id":"CVE-2026-89589","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"accel/rocket: Fix error path handling in rocket_job_run()","id":"CVE-2026-89590"},"packages":[],"prev":{"headline":"ACPI: APEI: GHES: fix ARM section length accounting after header","id":"CVE-2026-89588"},"products":["Linux"],"published":"2026-09-11","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A race condition in the Linux kernel CXL CPER handling can cause a deadlock when a GHES interrupt occurs while holding a spinlock, leading to system denial of service.","url":"https://insights.sbomify.com/CVE-2026-89589/"}