CVE-2025-38267

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-07-10. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

ring-buffer: Do not trigger WARN_ON() due to a commit_overrun

When reading a memory mapped buffer the reader page is just swapped out with the last page written in the write buffer. If the reader page is the same as the commit buffer (the buffer that is currently being written to) it was assumed that it should never have missed events. If it does, it triggers a WARN_ON_ONCE().

But there just happens to be one scenario where this can legitimately happen. That is on a commit_overrun. A commit overrun is when an interrupt preempts an event being written to the buffer and then the interrupt adds so many new events that it fills and wraps the buffer back to the commit. Any new events would then be dropped and be reported as "missed_events".

In this case, the next page to read is the commit buffer and after the swap of the reader page, the reader page will be the commit buffer, but this time there will be missed events and this triggers the following warning:

------------[ cut here ]------------ WARNING: CPU: 2 PID: 1127 at kernel/trace/ring_buffer.c:7357 ring_buffer_map_get_reader+0x49a/0x780 Modules linked in: kvm_intel kvm irqbypass CPU: 2 UID: 0 PID: 1127 Comm: trace-cmd Not tainted 6.15.0-rc7-test-00004-g478bc2824b45-dirty #564 PREEMPT Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 RIP: 0010:ring_buffer_map_get_reader+0x49a/0x780 Code: 00 00 00 48 89 fe 48 c1 ee 03 80 3c 2e 00 0f 85 ec 01 00 00 4d 3b a6 a8 00 00 00 0f 85 8a fd ff ff 48 85 c0 0f 84 55 fe ff ff <0f> 0b e9 4e fe ff ff be 08 00 00 00 4c 89 54 24 58 48 89 54 24 50 RSP: 0018:ffff888121787dc0 EFLAGS: 00010002 RAX: 00000000000006a2 RBX: ffff888100062800 RCX: ffffffff8190cb49 RDX: ffff888126934c00 RSI: 1ffff11020200a15 RDI: ffff8881010050a8 RBP: dffffc0000000000 R08: 0000000000000000 R09: ffffed1024d26982 R10: ffff888126934c17 R11: ffff8881010050a8 R12: ffff888126934c00 R13: ffff8881010050b8 R14: ffff888101005000 R15: ffff888126930008 FS: 00007f95c8cd7540(0000) GS:ffff8882b576e000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f95c8de4dc0 CR3: 0000000128452002 CR4: 0000000000172ef0 Call Trace: ? __pfx_ring_buffer_map_get_reader+0x10/0x10 tracing_buffers_ioctl+0x283/0x370 __x64_sys_ioctl+0x134/0x190 do_syscall_64+0x79/0x1c0 entry_SYSCALL_64_after_hwframe+0x76/0x7e RIP: 0033:0x7f95c8de48db Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 1c 48 8b 44 24 18 64 48 2b 04 25 28 00 00 RSP: 002b:00007ffe037ba110 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007ffe037bb2b0 RCX: 00007f95c8de48db RDX: 0000000000000000 RSI: 0000000000005220 RDI: 0000000000000006 RBP: 00007ffe037ba180 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffe037bb6f8 R14: 00007f95c9065000 R15: 00005575c7492c90 irq event stamp: 5080 hardirqs last enabled at (5079): [] _raw_spin_unlock_irqrestore+0x50/0x70 hardirqs last disabled at (5080): [] _raw_spin_lock_irqsave+0x63/0x70 softirqs last enabled at (4182): [] handle_softirqs+0x552/0x710 softirqs last disabled at (4159): [] __irq_exit_rcu+0x107/0x210 ---[ end trace 0000000000000000 ]---

The above was triggered by running on a kernel with both lockdep and KASAN as well as kmemleak enabled and executing the following command:

# perf record -o perf-test.dat -a -- trace-cmd record --nosplice -e all -p function hackbench 50

With perf interjecting a lot of interrupts and trace-cmd enabling all events as well as function tracing, with lockdep, KASAN and kmemleak enabled, it could cause an interrupt preempting an event being written to add enough event ---truncated---

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

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 (value × EchelonGraph’s weight)
Severity78% × 45%
The EG Score, 7.8 of 10.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
10th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 10, 2025

Last Modified

November 18, 2025

Advisory Details (3)

Auto-updated Sep 24, 2026
Patch available.
Web page

ring-buffer: Do not trigger WARN_ON() due to a commit_overrun - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e018053632bad8ee0752242c7d2cffb0bbf45404
Web page

ring-buffer: Do not trigger WARN_ON() due to a commit_overrun - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b8df8cb8f7eef52baa9ac5bf36a405ca67945a91
Web page

ring-buffer: Do not trigger WARN_ON() due to a commit_overrun - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4fc78a7c9ca994e1da5d3940704d4e8f0ea8c5e4

Vendor Advisories for CVE-2025-38267(1)

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

Patch Availability(9)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-hwe-24.04-edge (6.14.0-32.32) @ plucky2026-05-30ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.14.0-1012.12~24.04.1) @ noble2026-05-30ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.14.0-32.32~24.04.1) @ noble2026-05-30ubuntu
ubuntulinux-tools-oem-6.14 (6.14.0-1012.12) @ noble2026-05-30ubuntu
ubuntulinux-tools-azure-6.14 (6.14.0-1012.12) @ plucky2026-05-30ubuntu
ubuntulinux-tools-oracle-edge (6.14.0-1013.13~24.04.1) @ noble2026-05-30ubuntu
ubuntulinux-tools-raspi-6.14 (6.14.0-1014.14) @ plucky2026-05-30ubuntu
redhatkernel-0:6.12.0-211.7.1.el10_22026-05-19redhat
linuxKernel @ 6.12.34 (fixes >=6.10.0)—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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.35-1: fixed in 6.12.35-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.35-1: fixed in 6.12.35-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(7)

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 11× in last 7d / 28× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 90 of 159 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 10 repeat rows among the latest 100 are merged into the row they repeat. The 69 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-38267?
CVE-2025-38267 is a high-severity vulnerability; its CVE record was published on July 10, 2025. In the Linux kernel, the following vulnerability has been resolved: ring-buffer: Do not trigger WARNON() due to a commitoverrun When reading a memory mapped buffer the reader page is just swapped out with the last page written in the write buffer. If the reader page is the same as the commit buffer…
When was the CVE record for CVE-2025-38267 published?
The CVE record for CVE-2025-38267 was published on July 10, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 18, 2025; the record at its source may have been updated since.
Is CVE-2025-38267 actively exploited?
CVE-2025-38267 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (10th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-38267?
CVE-2025-38267 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2025-38267?
A fix for CVE-2025-38267 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-38267 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-38267

Explore →

Is Your Infrastructure Affected by CVE-2025-38267?

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

Book a Demo →Browse All CVEs