CVE-2026-23071

MEDIUMNVD 4.74.7—
EchelonGraph scoreMEDIUM confidence

Score 4.7 from GitHub Security Advisory published 2026-02-04. NVD baseline CVSS 4.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
4.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.7Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
4.7
EG Score
4.7(medium)
EG Risk
21(Track)
EG Risk 21/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity47% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

February 4, 2026

Last Modified

June 17, 2026

Advisory Details (7)

Auto-updated Aug 13, 2026
No patch confirmed yet.
generic

regmap: Fix race condition in hwspinlock irqsave routine - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f1e2fe26a51eca95b41420af76d22c2e613efd5e
generic

regmap: Fix race condition in hwspinlock irqsave routine - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e1a7072bc4f958c9e852dc7e57e39f12b0bb44b5
generic

regmap: Fix race condition in hwspinlock irqsave routine - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c2d2cf710dc3ee1a69e00b4ed8de607a92a07889
generic

regmap: Fix race condition in hwspinlock irqsave routine - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/766e243ae8c8b27087a4cc605752c0d5ee2daeab
generic

regmap: Fix race condition in hwspinlock irqsave routine - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4b58aac989c1e3fafb1c68a733811859df388250
generic

regmap: Fix race condition in hwspinlock irqsave routine - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4aab0ca0a0f7760e33edcb4e47576064d05128f5
generic

regmap: Fix race condition in hwspinlock irqsave routine - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/24f31be6ad70537fd7706269d99c92cade465a09

Patch Availability(21)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1057.57~20.04.1) @ focal2026-06-07ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.176.161) @ jammy2026-06-07ubuntu
ubuntulinux-tools-realtime-5.15 (5.15.0.1104.108) @ jammy2026-06-07ubuntu
ubuntulinux-tools-gcp-fips-5.15 (5.15.0.1105.95) @ jammy2026-06-07ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1057.57) @ jammy2026-06-07ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.176.186~20.04.1) @ focal2026-06-07ubuntu
ubuntulinux-tools-kvm-5.15 (5.15.0.1097.93) @ jammy2026-06-07ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1110.95) @ jammy2026-06-07ubuntu
ubuntulinux-tools-ibm-5.15 (5.15.0.1099.95) @ jammy2026-06-07ubuntu
ubuntulinux-tools-azure-edge (5.15.0.1110.119~20.04.1) @ focal2026-06-07ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1070 (5.15.0-1070.74) @ jammy2026-06-07ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1099.97) @ jammy2026-06-07ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1024.24) @ noble2026-06-07ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-116.116+fips1) @ noble2026-06-07ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1106.115~20.04.1) @ focal2026-06-07ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1056.62) @ noble2026-06-07ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1054.57.1) @ noble2026-06-07ubuntu
ubuntulinux-tools-nvidia-hwe-22.04-edge (6.8.0-1054.57~22.04.1) @ jammy2026-06-07ubuntu
ubuntulinux-virtual-6.8 (6.8.0-117.117) @ noble2026-06-07ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1059.65+fips1) @ noble2026-06-07ubuntu
linuxKernel @ 5.10.249—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (48 versions)5.10.249-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.159-1~deb11u1 (14 versions)6.1.162-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (46 versions)6.1.162-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.69-1~bpo12+1 (10 versions)6.12.69-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (96 versions)6.18.8-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(25)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 3× in last 7d / 18× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 143 total refreshes for this CVE.

  1. 2026-09-18 23:30 UTCOSV refresh
  2. 2026-09-18 19:27 UTCEPSS rescore
  3. 2026-09-16 14:07 UTCEPSS rescore
  4. 2026-09-13 16:47 UTCEPSS rescore
  5. 2026-09-12 15:01 UTCEPSS rescore
  6. 2026-09-11 14:52 UTCEPSS rescore
  7. 2026-09-10 09:34 UTCEPSS rescore
  8. 2026-09-08 22:00 UTCEPSS rescore
  9. 2026-09-06 13:47 UTCEPSS rescore
  10. 2026-09-06 13:47 UTCEPSS rescore
  11. 2026-09-04 05:06 UTCEPSS rescore
  12. 2026-09-02 14:11 UTCEPSS rescore
  13. 2026-09-01 13:53 UTCEPSS rescore
  14. 2026-08-31 03:02 UTCOSV refresh
  15. 2026-08-30 19:17 UTCEPSS rescore
  16. 2026-08-28 21:41 UTCEPSS rescore
  17. 2026-08-27 14:25 UTCEPSS rescore
  18. 2026-08-26 14:46 UTCEPSS rescore
  19. 2026-08-21 23:49 UTCEPSS rescore
  20. 2026-08-20 22:55 UTCEPSS rescore
  21. 2026-08-19 17:03 UTCEPSS rescore
  22. 2026-08-17 13:47 UTCEPSS rescore
  23. 2026-08-16 02:14 UTCEPSS rescore
  24. 2026-08-15 01:30 UTCEPSS rescore
  25. 2026-08-14 11:15 UTCEG score recompute
Show 75 more
  1. 2026-08-14 11:15 UTCVendor advisory
  2. 2026-08-14 11:15 UTCGHSA enrichment
  3. 2026-08-13 22:00 UTCEPSS rescore
  4. 2026-08-13 03:34 UTCEG score recompute
  5. 2026-08-13 03:34 UTCVendor advisory
  6. 2026-08-13 03:34 UTCGHSA enrichment
  7. 2026-08-11 00:00 UTCEPSS rescore
  8. 2026-08-09 15:53 UTCEG score recompute
  9. 2026-08-09 15:53 UTCVendor advisory
  10. 2026-08-09 15:53 UTCGHSA enrichment
  11. 2026-08-09 13:46 UTCEPSS rescore
  12. 2026-08-08 16:37 UTCEPSS rescore
  13. 2026-08-07 22:48 UTCEG score recompute
  14. 2026-08-07 22:48 UTCVendor advisory
  15. 2026-08-07 22:48 UTCGHSA enrichment
  16. 2026-08-06 13:46 UTCEPSS rescore
  17. 2026-08-06 04:23 UTCEG score recompute
  18. 2026-08-06 04:23 UTCVendor advisory
  19. 2026-08-06 04:23 UTCGHSA enrichment
  20. 2026-08-05 19:17 UTCEPSS rescore
  21. 2026-08-04 15:10 UTCEPSS rescore
  22. 2026-08-04 10:38 UTCEPSS rescore
  23. 2026-08-02 21:27 UTCEG score recompute
  24. 2026-08-02 21:27 UTCVendor advisory
  25. 2026-08-02 21:27 UTCGHSA enrichment
  26. 2026-08-02 02:26 UTCEPSS rescore
  27. 2026-08-01 04:15 UTCEPSS rescore
  28. 2026-07-30 23:50 UTCOSV refresh
  29. 2026-07-30 01:30 UTCEPSS rescore
  30. 2026-07-27 14:13 UTCEPSS rescore
  31. 2026-07-25 14:17 UTCEPSS rescore
  32. 2026-07-25 14:17 UTCEPSS rescore
  33. 2026-07-24 14:17 UTCEPSS rescore
  34. 2026-07-23 14:18 UTCEPSS rescore
  35. 2026-07-23 14:18 UTCEPSS rescore
  36. 2026-07-23 03:06 UTCEG score recompute
  37. 2026-07-22 14:08 UTCEPSS rescore
  38. 2026-07-20 17:08 UTCEPSS rescore
  39. 2026-07-18 10:04 UTCEPSS rescore
  40. 2026-07-18 10:04 UTCEPSS rescore
  41. 2026-07-16 17:03 UTCEPSS rescore
  42. 2026-07-16 17:03 UTCEPSS rescore
  43. 2026-07-15 16:57 UTCEPSS rescore
  44. 2026-07-15 16:57 UTCEPSS rescore
  45. 2026-07-15 02:00 UTCEPSS rescore
  46. 2026-07-15 02:00 UTCEPSS rescore
  47. 2026-07-13 22:30 UTCEPSS rescore
  48. 2026-07-13 08:08 UTCOSV refresh
  49. 2026-07-13 06:13 UTCEPSS rescore
  50. 2026-07-13 06:13 UTCEPSS rescore
  51. 2026-07-12 05:46 UTCEPSS rescore
  52. 2026-07-12 05:46 UTCEPSS rescore
  53. 2026-07-11 08:27 UTCEPSS rescore
  54. 2026-07-09 19:10 UTCEPSS rescore
  55. 2026-07-08 15:15 UTCEPSS rescore
  56. 2026-07-08 15:15 UTCEPSS rescore
  57. 2026-07-06 16:27 UTCEPSS rescore
  58. 2026-07-06 16:27 UTCEPSS rescore
  59. 2026-07-06 02:23 UTCEPSS rescore
  60. 2026-07-06 02:23 UTCEPSS rescore
  61. 2026-07-04 06:31 UTCEPSS rescore
  62. 2026-07-04 06:31 UTCEPSS rescore
  63. 2026-07-01 15:06 UTCEPSS rescore
  64. 2026-07-01 15:06 UTCEPSS rescore
  65. 2026-06-30 23:22 UTCEPSS rescore
  66. 2026-06-30 23:22 UTCEPSS rescore
  67. 2026-06-28 14:07 UTCEPSS rescore
  68. 2026-06-28 14:07 UTCEPSS rescore
  69. 2026-06-27 03:08 UTCEPSS rescore
  70. 2026-06-25 13:49 UTCEPSS rescore
  71. 2026-06-25 13:49 UTCEPSS rescore
  72. 2026-06-24 22:31 UTCOSV refresh
  73. 2026-06-23 21:33 UTCEPSS rescore
  74. 2026-06-23 21:32 UTCEPSS rescore
  75. 2026-06-21 01:59 UTCEPSS rescore

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-23071?
CVE-2026-23071 is a medium vulnerability published on February 4, 2026. 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 'hwspinlocktimeout_irqsave'. This creates a race condition where multiple contexts…
When was CVE-2026-23071 disclosed?
CVE-2026-23071 was first published in the National Vulnerability Database on February 4, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-23071 actively exploited?
CVE-2026-23071 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.9% of all scored CVEs.
What is the CVSS score of CVE-2026-23071?
CVE-2026-23071 has a CVSS v3 base score of 4.7 (NVD).
How do I remediate CVE-2026-23071?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23071, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-23071

Explore →

Is Your Infrastructure Affected by CVE-2026-23071?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs