CVE-2026-23271

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-03-20. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

perf: Fix __perf_event_overflow() vs perf_remove_from_context() race

Make sure that __perf_event_overflow() runs with IRQs disabled for all possible callchains. Specifically the software events can end up running it with only preemption disabled.

This opens up a race vs perf_event_exit_event() and friends that will go and free various things the overflow path expects to be present, like the BPF program.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

March 20, 2026

Last Modified

August 5, 2026

Advisory Details (6)

Auto-updated Jun 10, 2026
No patch confirmed yet.
generic

perf: Fix __perf_event_overflow() vs perf_remove_from_context() race - kernel/git/stable/linux.git - Linux kernel stable tree

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

perf: Fix __perf_event_overflow() vs perf_remove_from_context() race - kernel/git/stable/linux.git - Linux kernel stable tree

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

perf: Fix __perf_event_overflow() vs perf_remove_from_context() race - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5c48fdc4b4623533d86e279f51531a7ba212eb87
generic

perf: Fix __perf_event_overflow() vs perf_remove_from_context() race - kernel/git/stable/linux.git - Linux kernel stable tree

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

perf: Fix __perf_event_overflow() vs perf_remove_from_context() race - kernel/git/stable/linux.git - Linux kernel stable tree

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

perf: Fix __perf_event_overflow() vs perf_remove_from_context() race - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3f89b61dd504c5b6711de9759e053b082f9abf12

Vendor Advisories for CVE-2026-23271(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.1.167—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 ... 7.2~rc5-1~exp1 (496 versions)——
linux-6.16.1.106-3~deb11u1 ... 6.1.164-1~deb11u1 (16 versions)6.1.170-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (117 versions)6.19.8-1—

Weakness Classification(1)

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

Additional Vendor Advisories

(13)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 4× in last 7d / 53× 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 188 total refreshes for this CVE.

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

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

Frequently asked(5)

What is CVE-2026-23271?
CVE-2026-23271 is a high vulnerability published on March 20, 2026. In the Linux kernel, the following vulnerability has been resolved: perf: Fix perfeventoverflow() vs perfremovefrom_context() race Make sure that perfeventoverflow() runs with IRQs disabled for all possible callchains. Specifically the software events can end up running it with only preemption…
When was CVE-2026-23271 disclosed?
CVE-2026-23271 was first published in the National Vulnerability Database on March 20, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-23271 actively exploited?
CVE-2026-23271 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 99.2% of all scored CVEs.
What is the CVSS score of CVE-2026-23271?
CVE-2026-23271 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-23271?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23271, 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-23271

Explore →

Is Your Infrastructure Affected by CVE-2026-23271?

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

Start Free Scan →Browse All CVEs