CVE-2026-48914 Qemu-kvm: heap buffer overflow in virtio-blk scsi request handling
Medium 6.7
Published
Updated
Check this codebase for CVE-2026-48914 and fix it if it is affected.
What it is: CVE-2026-48914 is a medium-severity memory corruption vulnerability in Red Hat Enterprise Linux 10, published on 12 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-48914 in the wild and no public exploit code.
Affected product: Red Hat Enterprise Linux 10. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-48914/ (Markdown: https://insights.sbomify.com/CVE-2026-48914/index.md)
A malicious guest can cause a heap buffer overflow in QEMU's virtio-blk device, leading to a denial of service for the host process.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-48914?
CVE-2026-48914 is a medium-severity memory corruption vulnerability in Red Hat Enterprise Linux 10, published on 12 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
A flaw was found in QEMU's virtio-blk device. The issue arises because the device does not properly validate the size of input descriptors before writing data. A malicious guest with high privileges could exploit this vulnerability by submitting a malformed virtio-blk SCSI request, leading to an out-of-bounds write in the host heap memory and a potential denial of service (DoS) for the QEMU process.
Weakness: CWE-122
Which versions are affected by CVE-2026-48914?
Linux distribution packages (40)
qemu-guest-agent AlmaLinux:10 | All versions | 18:10.1.0-16.el10_2.5.alma.1 |
qemu-img AlmaLinux:10 | All versions | 18:10.1.0-16.el10_2.5.alma.1 |
qemu-kvm AlmaLinux:10 | All versions | 18:10.1.0-16.el10_2.5.alma.1 |
qemu-kvm-audio-pa AlmaLinux:10 | All versions | 18:10.1.0-16.el10_2.5.alma.1 |
qemu-kvm-block-blkio AlmaLinux:10 | All versions | 18:10.1.0-16.el10_2.5.alma.1 |
qemu-kvm-block-curl AlmaLinux:10 | All versions | 18:10.1.0-16.el10_2.5.alma.1 |
qemu-kvm-block-rbd AlmaLinux:10 | All versions | 18:10.1.0-16.el10_2.5.alma.1 |
qemu-kvm-common AlmaLinux:10 | All versions | 18:10.1.0-16.el10_2.5.alma.1 |
qemu-kvm-core AlmaLinux:10 | All versions | 18:10.1.0-16.el10_2.5.alma.1 |
qemu-kvm-device-display-virtio-gpu AlmaLinux:10 | All versions | 18:10.1.0-16.el10_2.5.alma.1 |
qemu-kvm-device-display-virtio-gpu-ccw AlmaLinux:10 | All versions | 18:10.1.0-16.el10_2.5.alma.1 |
qemu-kvm-device-display-virtio-gpu-pci AlmaLinux:10 | All versions | 18:10.1.0-16.el10_2.5.alma.1 |
qemu-kvm-device-display-virtio-vga AlmaLinux:10 | All versions | 18:10.1.0-16.el10_2.5.alma.1 |
qemu-kvm-device-usb-host AlmaLinux:10 | All versions | 18:10.1.0-16.el10_2.5.alma.1 |
qemu-kvm-device-usb-redirect AlmaLinux:10 | All versions | 18:10.1.0-16.el10_2.5.alma.1 |
qemu-kvm-docs AlmaLinux:10 | All versions | 18:10.1.0-16.el10_2.5.alma.1 |
qemu-kvm-tools AlmaLinux:10 | All versions | 18:10.1.0-16.el10_2.5.alma.1 |
qemu-kvm-ui-egl-headless AlmaLinux:10 | All versions | 18:10.1.0-16.el10_2.5.alma.1 |
qemu-kvm-ui-opengl AlmaLinux:10 | All versions | 18:10.1.0-16.el10_2.5.alma.1 |
qemu-pr-helper AlmaLinux:10 | All versions | 18:10.1.0-16.el10_2.5.alma.1 |
qemu-guest-agent AlmaLinux:9 | All versions | 17:10.1.0-17.el9_8.4.alma.1 |
qemu-img AlmaLinux:9 | All versions | 17:10.1.0-17.el9_8.4.alma.1 |
qemu-kvm AlmaLinux:9 | All versions | 17:10.1.0-17.el9_8.4.alma.1 |
qemu-kvm-audio-pa AlmaLinux:9 | All versions | 17:10.1.0-17.el9_8.4.alma.1 |
qemu-kvm-block-blkio AlmaLinux:9 | All versions | 17:10.1.0-17.el9_8.4.alma.1 |
qemu-kvm-block-curl AlmaLinux:9 | All versions | 17:10.1.0-17.el9_8.4.alma.1 |
qemu-kvm-block-rbd AlmaLinux:9 | All versions | 17:10.1.0-17.el9_8.4.alma.1 |
qemu-kvm-common AlmaLinux:9 | All versions | 17:10.1.0-17.el9_8.4.alma.1 |
qemu-kvm-core AlmaLinux:9 | All versions | 17:10.1.0-17.el9_8.4.alma.1 |
qemu-kvm-device-display-virtio-gpu AlmaLinux:9 | All versions | 17:10.1.0-17.el9_8.4.alma.1 |
qemu-kvm-device-display-virtio-gpu-ccw AlmaLinux:9 | All versions | 17:10.1.0-17.el9_8.4.alma.1 |
qemu-kvm-device-display-virtio-gpu-pci AlmaLinux:9 | All versions | 17:10.1.0-17.el9_8.4.alma.1 |
qemu-kvm-device-display-virtio-vga AlmaLinux:9 | All versions | 17:10.1.0-17.el9_8.4.alma.1 |
qemu-kvm-device-usb-host AlmaLinux:9 | All versions | 17:10.1.0-17.el9_8.4.alma.1 |
qemu-kvm-device-usb-redirect AlmaLinux:9 | All versions | 17:10.1.0-17.el9_8.4.alma.1 |
qemu-kvm-docs AlmaLinux:9 | All versions | 17:10.1.0-17.el9_8.4.alma.1 |
qemu-kvm-tools AlmaLinux:9 | All versions | 17:10.1.0-17.el9_8.4.alma.1 |
qemu-kvm-ui-egl-headless AlmaLinux:9 | All versions | 17:10.1.0-17.el9_8.4.alma.1 |
qemu-kvm-ui-opengl AlmaLinux:9 | All versions | 17:10.1.0-17.el9_8.4.alma.1 |
qemu-pr-helper AlmaLinux:9 | All versions | 17:10.1.0-17.el9_8.4.alma.1 |
How do I fix CVE-2026-48914?
Apply the vendor's patch.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is CVE-2026-48914 being exploited?
There is no known exploitation of CVE-2026-48914 in the wild and no public exploit code.
Sources
Also known as ALSA-2026:39311, ALSA-2026:58571, AZL-90138, BELL-CVE-2026-48914, CLSA-2026-1784806096, CLSA-2026-1786357174 and 10 more.