LiveActive security incident?Get immediate response
CVE Record

CVE-2016-9083: drivers/vfio/pci/vfio_pci.c in the Linux kernel through 4.8.11 allows local users to bypass integer overflo...

drivers/vfio/pci/vfio_pci.c in the Linux kernel through 4.8.11 allows local users to bypass integer overflow checks, and cause a denial of service (memory corruption) or have unspecified other impact, by leveraging access to a vfio PCI device file for a VFIO_DEVICE_SET_IRQS ioctl call, aka a "state machine confusion bug."

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

A local Linux user with access to a VFIO PCI device file could trigger a kernel driver flaw that corrupts memory. The public record describes denial of service and unspecified other impact, not remote compromise. Business urgency is mainly for hosts using VFIO/PCI passthrough or virtualization workflows where non-root users can reach VFIO device nodes. Exposure is likely limited to Linux systems at or before 4.8.11 where local users can access VFIO PCI device files. This is most relevant to virtualization, PCI passthrough, or device-assignment hosts. General internet-facing exposure is not supported by the provided sources. Prioritize remediation on virtualization hosts and systems that expose VFIO devices to local users. This is not evidenced as internet-exploited, but kernel memory corruption can affect host stability and isolation. Treat as scheduled security maintenance unless VFIO access is broad or untrusted. Mitigation focus: Update affected Linux kernels using vendor-supported packages or upstream-fixed versions.; Apply relevant Red Hat advisories where applicable, including RHSA-2017:0386 or RHSA-2017:0387.; Restrict VFIO device file access to only trusted administrative or virtualization service accounts..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2016-9083 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.