NVIDIA code execution via memory write flaw in virtio networking
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Summary
NVIDIA VIRTIO-Net for Bluefield, including the GA, LTS25, LTS24, and LTS23 releases, has a flaw that lets a VM user with low privileges send a crafted message that causes a Write-What-Where condition. The flaw can be reached from an adjacent network, and a successful attack may allow code execution in the Virtio-Net scope.
Written by a model
Original description
NVIDIA VIRTIO-Net for Bluefield contains a vulnerability in Virtio-Net where a VM user may cause a Write-What-Where condition by crafted message. A successful exploit of this vulnerability may lead to Code Execution in Virtio-Net scope.
What to do
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-65094 (NVIDIA VIRTIO-Net for Bluefield contains a vulnerability in Virtio-Net where a VM user may cause a Write-What-Where condition by crafted…), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-65094 (entry last updated 2026-11-20):
Affected:
- NVIDIA VIRTIO-Net GA: versions All versions prior to 25.10.6
- NVIDIA VIRTIO-Net LTS25: versions All versions prior to 25.10.2
- NVIDIA VIRTIO-Net LTS24: versions All versions prior to 24.10.50
- NVIDIA VIRTIO-Net LTS23: version range not reported
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-65094 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-65094 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://nvd.nist.gov/vuln/detail/CVE-2026-65094
- https://www.cve.org/CVERecord?id=CVE-2026-65094
- https://github.com/NVIDIA/product-security/tree/main/2026/5815
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-65094
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-65094"}.Affected versions
- NVIDIA VIRTIO-Net GAAll versions prior to 25.10.6
- NVIDIA VIRTIO-Net LTS25All versions prior to 25.10.2
- NVIDIA VIRTIO-Net LTS24All versions prior to 24.10.50
- NVIDIA VIRTIO-Net LTS23Version range not reported
cve.now Index
- Exploitation0/40No signal
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity10/10CVSS 9.0, total technical impact per CISA
- No patch5/5No patch listed yet
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
- Would score about 37 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-65094 |
| Record | NVD · CVE-2026-65094 |
| Other links 1 | |
| Repository | GitHub · NVIDIA/product-security · tree/main/2026/5815 |
Questions about CVE-2026-65094
Is CVE-2026-65094 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-65094?
VIRTIO-Net GA: version All versions prior to 25.10.6. VIRTIO-Net LTS25: version All versions prior to 25.10.2. VIRTIO-Net LTS24: version All versions prior to 24.10.50.
Source: cve.now feed data
Related
- CVE-2026-67455NVIDIA Model Optimizer for Linux and Windows contains a vulnerability where an attacker could cause a deserialization of untrusted data.
- CVE-2026-100971NVIDIA OpenShell for Linux contains a vulnerability in the L7 path allowlist enforcement component where a local attacker with low…
- CVE-2026-100963NVIDIA TensorRT for Linux contains a vulnerability where a user could cause an integer overflow issue.
- CVE-2026-100972NVIDIA OpenShell for Linux contains a vulnerability in resource-level authorization for create, read, update, and delete operations where…
- CVE-2026-100968NVIDIA Megatron-LM contains a vulnerability in dataset loading where an attacker could cause deserialization of untrusted data.
- CVE-2026-100967NVIDIA Megatron-LM contains a vulnerability where an attacker could cause deserialization of untrusted data.
No corrections so far. Something wrong on this page? Report an error.