CVE-2025-38048
virtio_ring: Fix data race by tagging event_triggered as racy for KCSAN
Reported by linux · Published June 18, 2025
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.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| kernel-livepatch-6.12.31-35.92 | Amazon Linux | 1.0-0.amzn2023 |
| kernel-libbpf-devel | Amazon Linux | 6.1.141-155.222.amzn2023 |
| kernel | Amazon Linux | 6.1.141-155.222.amzn2023 |
| kernel-livepatch-6.1.141-155.222 | Amazon Linux | 1.0-0.amzn2023 |
| python3-perf6.12 | Amazon Linux | 6.12.31-35.92.amzn2023 |
| kernel6.12 | Amazon Linux | 6.12.31-35.92.amzn2023 |
| kernel-libbpf-static | Amazon Linux | 6.1.141-155.222.amzn2023 |
| kernel-headers | Amazon Linux | 6.1.141-155.222.amzn2023 |
| perf6.12 | Amazon Linux | 6.12.31-35.92.amzn2023 |
| linux_kernel | linux | 6.14.9, 6.12.31, 6.6.93, 6.1.141, 5.15.185 |
| Linux | Linux | b730cb109633c455ce8a7cd6934986c6a16d88d8 |
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 8d622d21d24803408b256d96463eac4574dcf067, 8d622d21d24803408b256d96463eac4574dcf067, 8d622d21d24803408b256d96463eac4574dcf067 |
| Linux | Linux | 5.14, 0, 5.15.185 |
| amazon:2023 | kernel-livepatch-6.12.31-35.92 | 0 |
| amazon:2023 | kernel-libbpf-devel | 0 |
| amazon:2023 | kernel | 0 |
| amazon:2023 | kernel-livepatch-6.1.141-155.222 | 0 |
| amazon:2023 | python3-perf6.12 | 0 |
| amazon:2023 | kernel6.12 | 0 |
| amazon:2023 | kernel-libbpf-static | 0 |
| amazon:2023 | kernel-headers | 0 |
| amazon:2023 | perf6.12 | 0 |
| Linux | Linux | 8d622d21d24803408b256d96463eac4574dcf067, 5.15.185, 6.1.141 |
| amazon:2023 | perf | 0 |
| amazon:2023 | kernel-libbpf | 0 |
| amazon:2023 | kernel-tools-devel | 0 |
| amazon:2023 | python3-perf | 0 |
| amazon:2023 | kernel-modules-extra | 0 |
| amazon:2023 | kernel-tools | 0 |
| linux | linux_kernel | 5.14, 5.14, 5.14 |
| amazon:2023 | kernel6.12-modules-extra | 0 |
…and 3 more
Timeline
- Jun 17, 2025 CVE Published
- Jun 18, 2025 EPSS Score (30 in total, the first dated here)
- Dec 2, 2025 PoC Published
- Mar 29, 2026 Distribution Patch (320 in total, the first dated here)
- Mar 29, 2026 Security Advisory (332 in total, the first dated here)
- Jun 9, 2026 Coalition ESS Score
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2025-38048
vulnetix vdb fixes CVE-2025-38048
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-38048/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart