# CVE-2026-48914: Qemu-kvm: heap buffer overflow in virtio-blk scsi request handling > 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. - **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:N/I:L/A:H`) - **Exploited in the wild:** Not known - **Login needed:** An administrator - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 12 Jun 2026 - **Updated:** 31 Aug 2026 - **Also known as:** ALSA-2026:39311, ALSA-2026:58571, AZL-90138, BELL-CVE-2026-48914, CLSA-2026-1784806096, CLSA-2026-1786357174, DEBIAN-CVE-2026-48914, ECHO-049a-1ec4-f2f6, GHSA-4hmh-vx7h-h98p, OESA-2026-2951, RHSA-2026:39311, RHSA-2026:58571, RLSA-2026:39311, RLSA-2026:58571, UBUNTU-CVE-2026-48914, openSUSE-SU-2026:11250-1 ## 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 (Heap-based Buffer Overflow) ## Which versions are affected by CVE-2026-48914? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `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. ## Is CVE-2026-48914 being exploited? There is no known exploitation of CVE-2026-48914 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text 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) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-48914 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-48914 - OSV: https://osv.dev/vulnerability/CVE-2026-48914 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-48914/ Summaries are generated and may contain mistakes; the official description above is the record.