Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2017-8380

Qemu: scsi: megasas: out-of-bounds read in megasas_mmio_write

Overview

Published
28 Aug 2017
Modified
17 Jun 2026
Critical CVE
0 Registry packages
55 OS packages
4 Linux distributions
Yes Fix available

Description

Buffer overflow in the "megasas_mmio_write" function in Qemu 2.9.0 allows remote attackers to have unspecified impact via unknown vectors.

Source: OX vulnerability database

Severity

9.8 · CRITICAL

CVSS 3.0 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Weakness: CWE-119

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 11 fixes

Oracle Linux 1 release · 2 packages

fixed 2
qemu ivshmem-tools
Oracle Linux fixes for CVE-2017-8380
ReleasePackageFixed in
7 qemu +9 15:3.0.0-1.el7
7 ivshmem-tools +10 15:3.1.0-1.el7

debian 4 releases · 1 package

fixed 4
qemu
debian fixes for CVE-2017-8380
ReleasePackageFixed in
11 qemu 1:2.8+dfsg-5
12 qemu 1:2.8+dfsg-5
13 qemu 1:2.8+dfsg-5
14 qemu 1:2.8+dfsg-5

echo 1 release · 1 package

fixed 1
qemu
echo fixes for CVE-2017-8380
ReleasePackageFixed in
qemu 1:2.8+dfsg-5

openSUSE 1 release · 4 packages

fixed 4
qemu-ipxe qemu-seabios qemu qemu-sgabios
openSUSE fixes for CVE-2017-8380
ReleasePackageFixed inAdvisory
Tumbleweed qemu-ipxe 1.0.0+-32.1 openSUSE-SU-2024:11287-1
Tumbleweed qemu-seabios +1 1.14.0_0_g155821a-32.1 openSUSE-SU-2024:11287-1
Tumbleweed qemu +42 6.1.0-32.1 openSUSE-SU-2024:11287-1
Tumbleweed qemu-sgabios 8-32.1 openSUSE-SU-2024:11287-1

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.