CVE-2026-23071
Race Condition in Linux Kernel regmap hwspinlock IRQ Handling
Publication date: 2026-02-04
Last updated on: 2026-03-18
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | From 5.11 (inc) to 5.15.199 (exc) |
| linux | linux_kernel | From 5.16 (inc) to 6.1.162 (exc) |
| linux | linux_kernel | From 6.2 (inc) to 6.6.122 (exc) |
| linux | linux_kernel | From 6.7 (inc) to 6.12.68 (exc) |
| linux | linux_kernel | From 6.13 (inc) to 6.18.8 (exc) |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | From 4.15 (inc) to 5.10.249 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-362 | The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a race condition in the Linux kernel's regmap component, specifically in the hwspinlock irqsave routine.
The issue arises because the address of a shared member variable, '&map->spinlock_flags', was passed directly to the function 'hwspin_lock_timeout_irqsave'.
This caused a race condition where multiple contexts competing for the lock could overwrite the shared flags variable, potentially corrupting the state for the current lock owner.
The fix involved using a local stack variable 'flags' to temporarily store the IRQ state, preventing the race condition.
How can this vulnerability impact me? :
This vulnerability can lead to corruption of the lock state in the Linux kernel when multiple contexts attempt to acquire the same hardware spinlock concurrently.
Such corruption could cause unpredictable behavior in kernel operations that rely on this locking mechanism, potentially leading to system instability or crashes.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know