NVD / CVE Program· CNA nvidia

CVE-2025-23280: NVIDIA Display Driver for Linux contains a vulnerability where an attacker could cause a use-after-free.

Noroxi assessment

Priority: Monitor (action score 28/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.23% (FIRST EPSS).
Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
Fixed version: nvidia-graphics-drivers (Debian:12) 535.309.01-0+deb12u1; nvidia-graphics-drivers-tesla (Debian:12) 525.147.05-6; nvidia-graphics-drivers-tesla-535 (Debian:13) 535.274.02-1~deb13u1.

Low priority for now. Upgrade to nvidia-graphics-drivers (Debian:12) 535.309.01-0+deb12u1; nvidia-graphics-drivers-tesla (Debian:12) 525.147.05-6; nvidia-graphics-drivers-tesla-535 (Debian:13) 535.274.02-1~deb13u1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

NVIDIA Display Driver for Linux contains a vulnerability where an attacker could cause a use-after-free. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, data tampering, denial of service, and information disclosure.

HighCVSS 7.0 · v3.1—No exploit Fix available

BDU:2025-14389

Published: Oct 10, 2025
Updated: Oct 18, 2026
EPSS: 0.2% · 14th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 28 / 40 · 7.0 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.2%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · nvidia: 7.0; NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (nvidia). Independent of NVD's CPE analysis and usually ahead of it.

NVIDIA GeForce
- All driver versions prior to 580.95.05, All driver versions prior to 570.195.03, All driver versions prior to 535.274.02affected
NVIDIA Guest driver
- 580.82.07(All versions prior to and including vGPU 19.1), 580.82.07(All versions up to and including the August 2025 release), 570.172.08(All versions prior to and including vGPU 18.4), 535.261.03(All versions prior to and including vGPU 16.11)affected
NVIDIA NVIDIA RTX, Quadro, NVS
- All driver versions prior to 580.95.05, All driver versions prior to 570.195.03, All driver versions prior to 535.274.02affected
NVIDIA Tesla
- All driver versions prior to 580.95.05, All driver versions prior to 570.195.03, All driver versions prior to 535.274.02affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:12	nvidia-graphics-drivers	before 535.309.01-0+deb12u1	535.309.01-0+deb12u1
Debian:12	nvidia-graphics-drivers-tesla	before 525.147.05-6	525.147.05-6
Debian:12	nvidia-graphics-drivers-tesla-470	from 0	—
Debian:12	nvidia-graphics-drivers-tesla-535	from 0	—
Debian:12	nvidia-open-gpu-kernel-modules	from 0	—
Debian:13	nvidia-graphics-drivers	from 0	—
Debian:13	nvidia-graphics-drivers-tesla-535	before 535.274.02-1~deb13u1	535.274.02-1~deb13u1

Same product

nvidia: all records

Other highest-scoring records for the same primary product.

CVE-2025-23309NVIDIA Display Driver contains a vulnerability where an uncontrolled DLL loading path might lead to arbitrary denial of service, escalation
32Monitor
CVE-2026-47601NVIDIA GPU Display Driver for Windows and Linux contains a vulnerability in the open-source kernel module DMA-BUF import path where an unpri
31Monitor
CVE-2026-47600NVIDIA GPU Display Driver for Windows and Linux contains a vulnerability in the kernel mode layer where an error-handling path could operate
31Monitor

Published before and after this one in the same product

← EarlierCVE-2022-21814Feb 7, 2022 · NVIDIA GPU Display Driver for Linux contains a vulnerability in the kernel driver package, where improper handling of insufficient permissio
24Monitor
Later →CVE-2025-23330Oct 23, 2025 · NVIDIA Display Driver for Linux contains a vulnerability where an attacker might be able to trigger a null pointer dereference.
22Monitor
Later →CVE-2025-23345Oct 23, 2025 · NVIDIA Display Driver for Windows and Linux contains a vulnerability in a video decoder, where an attacker might cause an out-of-bounds read
17Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
debian:nvidia-graphics-drivers	535.309.01-0+deb12u1 · Debian:12	Package registry (OSV)
debian:nvidia-graphics-drivers-tesla	525.147.05-6 · Debian:12	Package registry (OSV)
debian:nvidia-graphics-drivers-tesla-535	535.274.02-1~deb13u1 · Debian:13	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2025-33217110 days apartNVIDIA Display Driver for Windows contains a vulnerability where an attacker could trigger a use after free.
31Monitor
CVE-2025-33220110 days apartNVIDIA vGPU software contains a vulnerability in the Virtual GPU Manager, where a malicious guest could cause heap memory access after the m
31Monitor
CVE-2026-47500355 days apartNVIDIA GPU Display Driver for Windows and Linux contains a vulnerability in the kernel mode layer where improper cleanup of reference counts
31Monitor
CVE-2026-47505355 days apartNVIDIA GPU Display Driver for Windows contains a vulnerability in the kernel mode layer where an attacker could cause a use-after-free.
31Monitor
CVE-2026-47516355 days apartNVIDIA GPU Display Driver for Windows and Linux contains a vulnerability where an unprivileged user could cause a use-after-free.
31Monitor
CVE-2026-47579355 days apartThe NVIDIA GPU Display Driver for Windows contains a vulnerability in the kernel mode driver through which a user might trigger a use-after-
31Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

Someone with local access to the system can trigger it.
A low-privileged account is enough.
No user action is required.
Special conditions such as timing or configuration are required.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

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

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

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

nvd-secondary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

Fix✗ → ✓Sep 28, 2026, 10:48 PM UTC

For records you follow, these changes also arrive as notifications. →

References

nvd.nist.gov/vuln/detail/CVE-2025-23280

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records