LiveActive security incident?Get immediate response
CVE Record

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

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2026-23071 is a Linux kernel race condition in a regmap hardware spinlock path. Concurrent lock users could overwrite shared interrupt-state storage, potentially corrupting the current lock owner’s state. The record provides kernel fix commits but no CVSS score or confirmed exploitation.

Executive priority

Treat this as a normal kernel maintenance item unless your environment relies heavily on affected hardware spinlock paths. There is no supplied evidence of active exploitation or rated severity, but kernel race conditions should not be ignored on exposed or safety-sensitive systems.

Technical view

The vulnerable code passed &map->spinlock_flags directly to hwspin_lock_timeout_irqsave. Because that storage is shared, concurrent contenders could overwrite it while another context owns the lock. The fix stores IRQ flags in a local stack variable instead.

Likely exposure

Exposure is limited to systems running affected Linux kernel versions that exercise the regmap hwspinlock irqsave routine. The source bundle lists affected kernel lines including 4.15, 5.10.249, 5.15.199, 6.1.162, 6.6.122, 6.12.68, 6.18.8, and 6.19.

Exploitation context

The bundle does not report active exploitation, and KEV status is false. Practical impact depends on reaching the affected kernel path and causing lock contention. No public exploit maturity, attacker prerequisites, or impact rating is provided in the supplied sources.

Researcher notes

The record is technically specific but incomplete for risk scoring. Useful follow-up is commit and backport analysis across maintained kernel branches, plus determining which drivers configure regmap with hwspinlock and whether failures can affect availability, integrity, or privilege boundaries.

Mitigation direction

  • Apply Linux vendor kernel updates containing the referenced stable fixes.
  • Prioritize systems using regmap and hardware spinlock-related kernel paths.
  • Check distribution advisories for packaged fixed kernel builds.
  • Track the CVE record for later CVSS or impact updates.

Validation and detection

  • Compare running kernel versions against vendor fixed-version guidance.
  • Confirm kernel packages include one of the referenced stable fix commits.
  • Review hardware and driver usage for regmap hwspinlock dependency.
  • Document systems deferred from patching and their compensating controls.
Prepared
Confidence
medium
Sources
9

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-23071 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
1ADP providers
8Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux8698b9364710e7bac84b3af07dd410e39c8c2e08, 8698b9364710e7bac84b3af07dd410e39c8c2e08, 8698b9364710e7bac84b3af07dd410e39c8c2e08, 8698b9364710e7bac84b3af07dd410e39c8c2e08, 8698b9364710e7bac84b3af07dd410e39c8c2e08, 8698b9364710e7bac84b3af07dd410e39c8c2e08, 8698b9364710e7bac84b3af07dd410e39c8c2e08unaffected
LinuxLinux4.15, 0, 5.10.249, 5.15.199, 6.1.162, 6.6.122, 6.12.68, 6.18.8, 6.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.