dbcve.org
Improper AuthorizationWeakness · CWE-285

CVE-2025-30508

MEDIUM · 6.5 CVSS v3.1 Published 2026-02-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
67/100
Remediation priority · Elevated
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
Improper authorization in the Intel(R) Quick Assist Technology for some Intel(R) Platforms within Ring 0: Kernel may allow a denial of service. Unprivileged software adversary with an authenticated user combined with a low complexity attack may enable denial of service. 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 (none), integrity (none) 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

Improper authorization vulnerability in Intel(R) Quick Assist Technology kernel driver (Ring 0) allows an authenticated local user with unprivileged access to cause a denial of service via low-complexity attack requiring special internal knowledge and no user interaction.

MitigationApply Intel-provided patches or firmware/driver updates for Quick Assist Technology; restrict local access to trusted authenticated users only until patch is applied.

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/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. Confirm Intel Quick Assist Technology driver is installed
    Check for the presence of the QAT kernel driver by searching for 'qat' driver files or services. On Windows, check Device Manager for 'QuickAssist' devices or look in C:\Windows\System32\drivers for qat*.sys files. On Linux, run 'lsmod | grep qat' or check /proc/modules for qat modules.
    Affected if The Intel QAT driver (qat.sys, qat_dev driver, or similar) is present on the system.
  2. Identify the installed QAT driver version
    On Windows, right-click the QAT driver in Device Manager, select Properties, then the Driver tab to view the version. Alternatively, use 'driverquery /v | findstr -i qat' or check file properties of the driver .sys file. On Linux, run 'modinfo qat' or check the driver version through /sys/module/qat/version if available.
    Affected if A version number is returned that falls within or below any affected version range for CVE-2025-30508.
  3. Verify the QAT service or kernel module is loaded and running
    On Windows, check Services (services.msc) for 'Intel(R) QuickAssist Technology' service and confirm its status. On Linux, check if the qat service is active via 'systemctl status qat' or if the module is loaded via 'lsmod | grep qat'.
    Affected if The QAT driver/service is loaded and running, making the vulnerability exploitable.
  4. Check for unprivileged user access to QAT driver interfaces
    Review system permissions on QAT driver device nodes (e.g., /dev/qat* on Linux) or device objects on Windows. Use 'icacls' on Windows or 'ls -l' on Linux to verify which users or groups have access to QAT device files or driver interfaces.
    Affected if Unprivileged or standard users have read/write access to QAT driver interfaces without elevation.
  5. Audit local user accounts with access to the system
    Review local user accounts and group memberships, particularly for non-administrative users who have console or RDP access to the machine where QAT is installed.
    Affected if Authenticated local users with unprivileged accounts exist on the affected system.

The system is affected if Intel Quick Assist Technology driver is installed, running, and accessible to unprivileged authenticated local users, with a version that matches the affected range for CVE-2025-30508.

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 patches or firmware/driver updates for Quick Assist Technology; restrict local access to trusted authenticated users only until patch is applied.

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-30508 — 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-30508 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