dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2025-23244

HIGH · 7.8 CVSS v3.1 Published 2025-05-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
NVIDIA GPU Display Driver for Linux contains a vulnerability which could allow an unprivileged attacker to escalate permissions. A successful exploit of this vulnerability might lead to code execution, denial of service, escalation of privileges, information disclosure, and data tampering.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

NVIDIA GPU Display Driver for Linux contains a privilege escalation vulnerability where an unprivileged attacker can gain elevated permissions. The vulnerability affects the driver component and could enable code execution, denial of service, and information disclosure.

MitigationApply the NVIDIA GPU Display Driver security patch/update once released by NVIDIA. Prior to deployment, validate driver compatibility with existing GPU workloads and ensure proper testing in a staging environment.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify NVIDIA driver is installed
    Run 'nvidia-smi' or check for loaded kernel modules with 'lsmod | grep nvidia'
    Affected if No NVIDIA driver is present, the vulnerability does not apply
  2. Obtain the installed driver version
    Execute 'nvidia-smi' and note the 'Driver Version' field, or use 'cat /proc/driver/nvidia/version'
    Affected if Unable to retrieve version information - driver may not be properly installed
  3. Check the kernel module status
    Run 'lsmod | grep nvidia' to confirm the nvidia kernel module is loaded
    Affected if Kernel module is not loaded, the vulnerable driver component is not active
  4. Compare against affected version ranges
    Cross-reference the installed driver version with the CVE-affected version list once published by NVIDIA in their security bulletin
    Affected if Installed version falls within the affected version ranges published by NVIDIA

You are affected if the NVIDIA GPU Display Driver for Linux is installed and the installed version falls within the CVE-affected version ranges published by NVIDIA.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the NVIDIA GPU Display Driver security patch/update once released by NVIDIA. Prior to deployment, validate driver compatibility with existing GPU workloads and ensure proper testing in a staging environment.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-23244 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-23244 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data