CVE-2025-38267: ring-buffer: Do not trigger WARN_ON() due to a commit_overrun
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 4fc78a7c9ca994e1da5d3940704d4e8f0ea8c5e4, b8df8cb8f7eef52baa9ac5bf36a405ca67945a91, e018053632bad8ee0752242c7d2cffb0bbf45404.
Low priority for now. Upgrade to Linux Linux 4fc78a7c9ca994e1da5d3940704d4e8f0ea8c5e4, b8df8cb8f7eef52baa9ac5bf36a405ca67945a91, e018053632bad8ee0752242c7d2cffb0bbf45404 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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: <TASK> ? __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 </TASK> irq event stamp: 5080 hardirqs last enabled at (5079): [<ffffffff83e0adb0>] _raw_spin_unlock_irqrestore+0x50/0x70 hardirqs last disabled at (5080): [<ffffffff83e0aa83>] _raw_spin_lock_irqsave+0x63/0x70 softirqs last enabled at (4182): [<ffffffff81516122>] handle_softirqs+0x552/0x710 softirqs last disabled at (4159): [<ffffffff815163f7>] __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---
- Published
- Jul 10, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- CWE-787
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.10 and later · before 6.12.34
- linux linux kernel6.13 and later · before 6.15.3
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.10affected
- fe832be05a8eee5f1488cbcc2c562dd82d079fd6 and later · before b8df8cb8f7eef52baa9ac5bf36a405ca67945a91affected · git
- fe832be05a8eee5f1488cbcc2c562dd82d079fd6 and later · before e018053632bad8ee0752242c7d2cffb0bbf45404affected · git
- fe832be05a8eee5f1488cbcc2c562dd82d079fd6 and later · before 4fc78a7c9ca994e1da5d3940704d4e8f0ea8c5e4affected · git
- before 6.10not affected · semver
- 6.12.34 and later · up to and including 6.12.*not affected · semver
- 6.15.3 and later · up to and including 6.15.*not affected · semver
- 6.16 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | kernel | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-64k | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-64k-core | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-core | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel-matched | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-core | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-extra | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel-matched | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-core | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-extra | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-abi-stablelists | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-core | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-cross-headers | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-debug | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-debug-core | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel-matched | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules-core | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2025-38264Jul 9, 2025 · nvme-tcp: sanitize request list handling22Monitor
- ← EarlierCVE-2025-38266Jul 10, 2025 · pinctrl: mediatek: eint: Fix invalid pointer dereference for v1 platforms22Monitor
- Later →CVE-2025-38269Jul 10, 2025 · btrfs: exit after state insertion failure at btrfs_convert_extent_bit()22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 4fc78a7c9ca994e1da5d3940704d4e8f0ea8c5e4 | Vendor (CNA) |
| Linux Linux | b8df8cb8f7eef52baa9ac5bf36a405ca67945a91 | Vendor (CNA) |
| Linux Linux | e018053632bad8ee0752242c7d2cffb0bbf45404 | Vendor (CNA) |
| almalinux:kernel | 6.12.0-211.7.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k | 6.12.0-211.7.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-core | 6.12.0-211.7.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 6.12.0-211.7.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 6.12.0-211.7.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 6.12.0-211.7.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 6.12.0-211.7.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 6.12.0-211.7.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 6.12.0-211.7.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 6.12.0-211.7.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 6.12.0-211.7.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-devel-matched | 6.12.0-211.7.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| debian:linux | 6.12.35-1 · Debian:13 | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-debuginfo-common-aarch64 | 0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-debuginfo-common-ppc64le | 0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-787 · Out-of-bounds WriteCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.