Incorrect Default PermissionsWeakness · CWE-276

CVE-2025-32091

HIGH · 8.2 CVSS v3.1 Published 2025-11-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/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
Incorrect default permissions in some firmware for the Intel(R) Arc(TM) B-series GPUs within Ring 1: Device Drivers may allow an escalation of privilege. System software adversary with a privileged user combined with a low complexity attack may enable escalation of privilege. This result may potentially occur via local access when attack requirements are not present with special internal knowledge and requires no 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 · moderate confidence

Intel Arc B-series GPU firmware and device drivers in Ring 1 contain incorrect default permissions that allow a privileged user with special internal knowledge to escalate privileges via local access without user interaction.

MitigationApply Intel-provided firmware and driver updates for Arc B-series GPUs once released. Verify the permission settings in Ring 1 device drivers align with least-privilege principles.

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
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/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. Identify Intel Arc B-series GPU hardware
    Open Device Manager (Windows) or run 'lspci | grep -i arc' (Linux) to list installed graphics adapters. Look for Arc B580, B570, or other Arc Battlemage series GPUs.
    Affected if No Intel Arc B-series GPU is listed in the system hardware inventory, meaning the system is not vulnerable to this specific driver flaw.
  2. Locate Intel GPU driver version
    On Windows, open Device Manager > Display adapters > Intel Arc B-series GPU > Driver tab to view driver version. On Linux, run 'lsmod | grep i915' and check driver package version via 'intelGPU Composer' or driver metadata.
    Affected if A driver version is installed for an Intel Arc B-series GPU, indicating the vulnerable component is present.
  3. Verify driver is loaded and active
    Confirm the Intel GPU driver module (i915 on Linux, igfx driver on Windows) is loaded and the GPU is functional. Check 'dxdiag' (Windows) or system logs for driver initialization status.
    Affected if The driver is actively loaded and running, meaning the Ring 1 driver component with the permission flaw is operational on the system.
  4. Confirm user privilege context
    Identify the current user account privileges on the system where the GPU is installed. Check if the user has local administrative or elevated privileges that would enable exploitation.
    Affected if A privileged local user account exists on the system with the Intel Arc B-series GPU, which is the attacker profile required for this privilege escalation vulnerability.

A system is affected if it contains an actively-used Intel Arc B-series GPU with the default driver installed, and an untrusted local user with elevated privileges could exploit the Ring 1 permission flaw to escalate further.

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 Intel-provided firmware and driver updates for Arc B-series GPUs once released. Verify the permission settings in Ring 1 device drivers align with least-privilege principles.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-32091 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