CVE Intelligence
Medium Memory corruption

CVE-2026-47544 — Out-of-bounds Read in NVIDIA Virtual GPU Manager

NVIDIA vGPU Virtual GPU Manager for Linux contains a vulnerability in the kernel mode layer where an attacker could cause an out-of-bounds read. A successful exploit of this vulnerability might lead to code execution, denial of service, escalation of privileges, information disclosure, and data tampering.

Published Sep 30, 2026 · Updated Oct 16, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: nvidia

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.1% (30-day exploitation probability)+0
  • Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.13%
ahead of 2% of scored CVEs · Oct 15, 2026
Affects
NVIDIA
Virtual GPU Manager
CVSS base
6.7
Medium · 2 source(s)
Prioritization reference: 7.8 provisional

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (NVIDIA Virtual GPU Manager).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
NVIDIA Virtual GPU Manager version 595.71.03(All versions prior to and including vGPU 20.1)version 580.159.01(All versions prior to and including vGPU 19.5)version 596.38(All versions prior to and including vGPU 20.1)version 582.51(All versions prior to and including vGPU 19.5) Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

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

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
7.8 CVSS 3.1 High — — nvidia via CVE Program (cve.org) e CISA ADP
6.7 CVSS 3.1 Medium 0.8 5.9 psirt@nvidia.com via NIST National Vulnerability Database
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H (score shown at the top: psirt@nvidia.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-125 · Out-of-bounds Read

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
  • Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
endpoint telemetry (EDR)crash dumps

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · nvidia/virtual gpu manager
    Oct 16, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 16, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 15, 2026
  • CVSS changed · 6.7
    Oct 15, 2026 · NIST National Vulnerability Database
  • Source status changed · → Awaiting Analysis
    Oct 15, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 15, 2026 · NIST National Vulnerability Database
  • CVE published
    Sep 30, 2026 · nvidia

Source activity

Repeated readings are counted rather than listed.

  • 1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

3 on the record

Elsewhere on this site

NVIDIA
every CVE for this vendor
Memory corruption
same class
CWE-125
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-47604 Missing Authorization in NVIDIA GeForce 15d
  • CVE-2026-47603 Missing Authorization in NVIDIA GeForce 15d
  • CVE-2026-47598 Use After Free in NVIDIA GeForce 15d
  • CVE-2026-47602 Buffer Errors (Improper Restriction of Operations within Memory Bounds) in NVIDIA GeForce 15d
  • CVE-2026-47591 Incorrect Authorization in NVIDIA GeForce 15d
  • CVE-2026-47592 Out-of-bounds Read in NVIDIA GeForce 15d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-47544 is "Out-of-bounds Read in NVIDIA Virtual GPU Manager", rated Medium. It affects Virtual GPU Manager (NVIDIA); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 6.7 describes technical severity. EPSS 0.13% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.