dbcve.org
Graphics DriverApplication · Intel

CVE-2025-32092

MEDIUM · 6.7 CVSS v3.1 Published 2026-02-10
Fix available
A fix is available. Upgrade to 6.12.28-linux-250521T070434Z / 25.30.1702.0 or later.
See remediation →
67/100
Remediation priority · Elevated
Patch available

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
Insecure inherited permissions for some Intel(R) Graphics Software before version 25.30.1702.0 within Ring 3: User Applications may allow an escalation of privilege. Unprivileged software adversary with an authenticated user combined with a high complexity attack may enable escalation of privilege. This result may potentially occur via local access when attack requirements are present without special internal knowledge and requires active user interaction. The potential vulnerability may impact the confidentiality (high), integrity (high) and availability (high) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.

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

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Graphics DriverApplication
Affected:< 32.0.101.7026< 32.0.101.6979
Graphics SoftwareApplication
Affected:< 25.30.1702.0
Linux Intel Lts KernelApplication
Affected:< 6.12.28-linux-250521T070434Z

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
High
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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.

dbcve · scoped
Upgrade available Upgrade to 6.12.28-linux-250521T070434Z / 25.30.1702.0 / 32.0.101.6979 or later
Fixed in 6.12.28-linux-250521T070434Z25.30.1702.032.0.101.6979
Vendor patch intel.com →
Recommended fix High confidence

Intel Graphics Software 25.30.1702.0 or later; Intel Graphics Driver 32.0.101.7026 or 32.0.101.6979; Linux Intel LTS Kernel 6.12.28-linux-250521T070434Z or later

  1. Identify the affected Intel Graphics Software version installed on the system using the Intel Graphics Control Panel or system information tools
  2. Download Intel Graphics Software version 25.30.1702.0 or later from the official Intel download center
  3. If using Intel Graphics Drivers, upgrade to version 32.0.101.7026 or 32.0.101.6979 (whichever is applicable to your hardware)
  4. For Linux systems running Intel integrated graphics, upgrade the Intel LTS kernel to version 6.12.28-linux-250521T070434Z or later
  5. Close all graphics-intensive applications before upgrading
  6. Run the Intel Graphics Software installer with administrator privileges
  7. Restart the system after installation to ensure the new graphics driver/software loads properly
  8. Verify the installed version matches the fixed release (25.30.1702.0 for Graphics Software or 32.0.101.7026/32.0.101.6979 for drivers)
Caveat Driver updates may require system restart; ensure all work is saved and graphics-intensive applications are closed before upgrade

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-32092 — 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-32092 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