CVE-2025-38048: virtio_ring: Fix data race by tagging event_triggered as racy for KCSAN
Noroxi assessment
Priority: Monitor (action score 18/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.14% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: Linux Linux 02d2d6caee3abc9335cfca35f8eb4492173ae6f2, 2e2f925fe737576df2373931c95e1a2b66efdfef, 4ed8f0e808b3fcc71c5b8be7902d8738ed595b17.
Low priority for now. Upgrade to Linux Linux 02d2d6caee3abc9335cfca35f8eb4492173ae6f2, 2e2f925fe737576df2373931c95e1a2b66efdfef, 4ed8f0e808b3fcc71c5b8be7902d8738ed595b17 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: virtio_ring: Fix data race by tagging event_triggered as racy for KCSAN syzbot reports a data-race when accessing the event_triggered, here is the simplified stack when the issue occurred: ================================================================== BUG: KCSAN: data-race in virtqueue_disable_cb / virtqueue_enable_cb_delayed write to 0xffff8881025bc452 of 1 bytes by task 3288 on cpu 0: virtqueue_enable_cb_delayed+0x42/0x3c0 drivers/virtio/virtio_ring.c:2653 start_xmit+0x230/0x1310 drivers/net/virtio_net.c:3264 __netdev_start_xmit include/linux/netdevice.h:5151 [inline] netdev_start_xmit include/linux/netdevice.h:5160 [inline] xmit_one net/core/dev.c:3800 [inline] read to 0xffff8881025bc452 of 1 bytes by interrupt on cpu 1: virtqueue_disable_cb_split drivers/virtio/virtio_ring.c:880 [inline] virtqueue_disable_cb+0x92/0x180 drivers/virtio/virtio_ring.c:2566 skb_xmit_done+0x5f/0x140 drivers/net/virtio_net.c:777 vring_interrupt+0x161/0x190 drivers/virtio/virtio_ring.c:2715 __handle_irq_event_percpu+0x95/0x490 kernel/irq/handle.c:158 handle_irq_event_percpu kernel/irq/handle.c:193 [inline] value changed: 0x01 -> 0x00 ================================================================== When the data race occurs, the function virtqueue_enable_cb_delayed() sets event_triggered to false, and virtqueue_disable_cb_split/packed() reads it as false due to the race condition. Since event_triggered is an unreliable hint used for optimization, this should only cause the driver temporarily suggest that the device not send an interrupt notification when the event index is used. Fix this KCSAN reported data-race issue by explicitly tagging the access as data_racy.
- Published
- Jun 18, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 3th percentile
- CWE
- CWE-362
Report tools
Action score
18
Low priority for now.
- CVSS
- 18 / 40 · 4.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
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.
Is your version affected? Check itNoroxi 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 |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
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
- 5.14affected
- 8d622d21d24803408b256d96463eac4574dcf067 and later · before 02d2d6caee3abc9335cfca35f8eb4492173ae6f2affected · git
- 8d622d21d24803408b256d96463eac4574dcf067 and later · before b6d6419548286b2b9d2b90df824d3cab797f6ae8affected · git
- 8d622d21d24803408b256d96463eac4574dcf067 and later · before b49b5132e4c7307599492aee1cdc6d89f7f2a7daaffected · git
- 8d622d21d24803408b256d96463eac4574dcf067 and later · before b730cb109633c455ce8a7cd6934986c6a16d88d8affected · git
- 8d622d21d24803408b256d96463eac4574dcf067 and later · before 4ed8f0e808b3fcc71c5b8be7902d8738ed595b17affected · git
- 8d622d21d24803408b256d96463eac4574dcf067 and later · before 2e2f925fe737576df2373931c95e1a2b66efdfefaffected · git
- before 5.14not affected · semver
- 5.15.185 and later · up to and including 5.15.*not affected · semver
- 6.1.141 and later · up to and including 6.1.*not affected · semver
Affected versions · NVD (7)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux11.0
- linux linux kernel5.16 and later · before 6.1.141
- linux linux kernel6.2 and later · before 6.6.93
- linux linux kernelbefore 5.15.185
- linux linux kernel6.13 and later · before 6.14.9
- linux linux kernel6.7 and later · before 6.12.31
- linux linux kernel6.15
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.147-1 | 6.1.147-1 |
| Debian:13 | linux | before 6.12.32-1 | 6.12.32-1 |
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-38038Jun 18, 2025 · cpufreq: amd-pstate: Remove unnecessary driver_lock in set_boost22Monitor
- ← EarlierCVE-2025-38043Jun 18, 2025 · firmware: arm_ffa: Set dma_mask for ffa devices22Monitor
- Later →CVE-2025-38050Jun 18, 2025 · mm/hugetlb: fix kernel NULL pointer dereference when replacing free hugetlb folios22Monitor
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 | 02d2d6caee3abc9335cfca35f8eb4492173ae6f2 | Vendor (CNA) |
| Linux Linux | 2e2f925fe737576df2373931c95e1a2b66efdfef | Vendor (CNA) |
| Linux Linux | 4ed8f0e808b3fcc71c5b8be7902d8738ed595b17 | Vendor (CNA) |
| Linux Linux | b49b5132e4c7307599492aee1cdc6d89f7f2a7da | Vendor (CNA) |
| Linux Linux | b6d6419548286b2b9d2b90df824d3cab797f6ae8 | Vendor (CNA) |
| Linux Linux | b730cb109633c455ce8a7cd6934986c6a16d88d8 | Vendor (CNA) |
| debian:linux | 6.1.147-1 · Debian:12 | 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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
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.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')CVSS vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/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.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/2e2f925fe737576df2373931c95e1a2b66efdfef
- git.kernel.org/stable/c/4ed8f0e808b3fcc71c5b8be7902d8738ed595b17
- git.kernel.org/stable/c/b49b5132e4c7307599492aee1cdc6d89f7f2a7da
- git.kernel.org/stable/c/b6d6419548286b2b9d2b90df824d3cab797f6ae8
- git.kernel.org/stable/c/b730cb109633c455ce8a7cd6934986c6a16d88d8
- lists.debian.org/debian-lts-announce/2025/10/msg00008.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.