FKIE_CVE-2026-89589
Vulnerability from fkie_nvd - Published: 2026-09-11 20:19 - Updated: 2026-09-11 20:19
Severity
Summary
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 registration and unregistration helpers acquire
cxl_cper_work_lock and cxl_cper_prot_err_work_lock with a spinlock
guard(), which leaves local interrupts enabled. The corresponding post
paths (cxl_cper_post_event(), cxl_cper_post_prot_err()) execute in hard
IRQ context (they are called from the GHES error notification path) and
acquire the same locks with an irqsave guard().
If a CPU is holding one of these locks via a spinlock guard() when a GHES
interrupt arrives on the same CPU, the IRQ handler spins on the held lock
waiting for it to release, while the lock holder is preempted by the IRQ.
The result is a deadlock.
Convert both locks from spinlock_t to raw_spinlock_t and use guard() at
all call sites. On PREEMPT_RT kernels spinlock_t is backed by rt_mutex and
sleeping from hard IRQ context is not permitted; raw_spinlock_t is safe in
both contexts.
Add WARN_ONCE to both register functions to surface double-registration
bugs at runtime.
Restructure both unregister functions to clear the global work pointer
under the lock before calling cancel_work_sync(), closing the window
where a CPER interrupt could schedule work on a pointer about to be
freed. Add kfifo_reset() after cancel_work_sync() so stale entries
are not replayed on next module load.
Both kfifos are single-consumer: only one work_struct is registered at
a time, enforced by the WARN_ONCE guard in the register functions.
kfifo_reset() is safe outside the lock because cancel_work_sync() has
already quiesced the consumer, and no new consumer can register until
the current module exit completes and a fresh module init runs.
Remove the redundant cancel_work_sync() call from cxl_ras_exit() and
cxl_pci_driver_exit(). The CPER unregister functions now quiesce
the work internally.
References
Impacted products
| Vendor | Product | Version |
|---|
{
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/acpi/apei/ghes.c",
"drivers/cxl/core/ras.c",
"drivers/cxl/pci.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "c735dbce7ad03df708bf22ec964f67e43cbc823a",
"status": "affected",
"version": "5e4a264bf8b55d5a1b4c8cd96ac10b99f98d7487",
"versionType": "git"
},
{
"lessThan": "0e25382b05de48d09b243d3d447d236a6d735bc2",
"status": "affected",
"version": "5e4a264bf8b55d5a1b4c8cd96ac10b99f98d7487",
"versionType": "git"
},
{
"lessThan": "6625ca499c3131ef63be3215f8f942d7a097ea3a",
"status": "affected",
"version": "5e4a264bf8b55d5a1b4c8cd96ac10b99f98d7487",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/acpi/apei/ghes.c",
"drivers/cxl/core/ras.c",
"drivers/cxl/pci.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.10"
},
{
"lessThan": "6.10",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.50",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.2.*",
"status": "unaffected",
"version": "7.2.4",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.3-rc1",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "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."
}
],
"id": "CVE-2026-89589",
"lastModified": "2026-09-11T20:19:43.437",
"metrics": {},
"published": "2026-09-11T20:19:43.437",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/0e25382b05de48d09b243d3d447d236a6d735bc2"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/6625ca499c3131ef63be3215f8f942d7a097ea3a"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/c735dbce7ad03df708bf22ec964f67e43cbc823a"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Loading…
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.
Loading…