VulnerabilityPublished 4 Feb 2026Updated 19 Oct 2026

CVE-2026-23071: Linux kernel · regmap: Fix race condition in hwspinlock irqsave routine

Affects Linux kernelSource CVE Database V5

Not known to be exploited · fixed in f1e2fe26a51eca95b41420af76d22c2e613efd5e : update Linux kernel when convenient.

Data as of 26 Oct 2026, 14:18 UTC

Severity

Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS

0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation: No evidence of active exploitation and no public proof of concept
Automatable: Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact: Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-06-10.

Patch

Available – fixed in f1e2fe26a51eca95b41420af76d22c2e613efd5e, e1a7072bc4f958c9e852dc7e57e39f12b0bb44b5, c2d2cf710dc3ee1a69e00b4ed8de607a92a07889 +4

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 8698b9364710e7bac84b3af07dd410e39c8c2e08, < f1e2fe26a51eca95b41420af76d22c2e613efd5e	Fixed in f1e2fe26a51eca95b41420af76d22c2e613efd5e
LinuxLinux	Affected ≥ 8698b9364710e7bac84b3af07dd410e39c8c2e08, < e1a7072bc4f958c9e852dc7e57e39f12b0bb44b5	Fixed in e1a7072bc4f958c9e852dc7e57e39f12b0bb44b5
LinuxLinux	Affected ≥ 8698b9364710e7bac84b3af07dd410e39c8c2e08, < c2d2cf710dc3ee1a69e00b4ed8de607a92a07889	Fixed in c2d2cf710dc3ee1a69e00b4ed8de607a92a07889
LinuxLinux	Affected ≥ 8698b9364710e7bac84b3af07dd410e39c8c2e08, < 766e243ae8c8b27087a4cc605752c0d5ee2daeab	Fixed in 766e243ae8c8b27087a4cc605752c0d5ee2daeab
LinuxLinux	Affected ≥ 8698b9364710e7bac84b3af07dd410e39c8c2e08, < 24f31be6ad70537fd7706269d99c92cade465a09	Fixed in 24f31be6ad70537fd7706269d99c92cade465a09
LinuxLinux	Affected ≥ 8698b9364710e7bac84b3af07dd410e39c8c2e08, < 4b58aac989c1e3fafb1c68a733811859df388250	Fixed in 4b58aac989c1e3fafb1c68a733811859df388250

Description

In the Linux kernel, the following vulnerability has been resolved: regmap: Fix race condition in hwspinlock irqsave routine Previously, the address of the shared member '&map->spinlock_flags' was passed directly to 'hwspin_lock_timeout_irqsave'. This creates a race condition where multiple contexts contending for the lock could overwrite the shared flags variable, potentially corrupting the state for the current lock owner. Fix this by using a local stack variable 'flags' to store the IRQ state temporarily.

CWE-362Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') (opens in a new tab)
Class weaknessLikelihood of exploit: MediumOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
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.
Architecture and Design
In languages that support it, use synchronization primitives. Only wrap these around critical code to minimize the impact on performance.
Architecture and Design
Use thread-safe capabilities such as the data access abstraction in Spring.
Architecture and Design
Minimize the usage of shared resources in order to remove as much complexity as possible from the control flow and to reduce the likelihood of unexpected conditions occurring.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V1.11.2 (opens in a new tab)
Attack patterns
Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions (opens in a new tab)
Leveraging Race Conditions (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

WeaknessesCWE-362

Technical details

References

Community reviews

Related threats