CVE-2025-20090
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 · uneditedUntrusted Pointer Dereference for some Intel(R) QuickAssist Technology software before version 2.5.0 may allow an authenticated user to potentially enable denial of service via local access.
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 confidenceIntel QuickAssist Technology software before version 2.5.0 contains an untrusted pointer dereference vulnerability. An authenticated local user could exploit this flaw to potentially cause a denial of service condition.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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< 2.5.0-0007CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Intel QuickAssist Technology software is installedLocate the Intel QAT software on the system. Check common installation directories such as /opt/intel/qat or /usr/lib64/qat, or query installed packages using the system package manager (e.g., rpm -qa or dpkg -l) for qat-related packages.Affected if Intel QuickAssist Technology software is not found on the system
-
Determine the installed version of Intel QuickAssist TechnologyRetrieve the version information from the installed software. This may be available in a version file within the installation directory, or accessible via a version flag if a command-line tool like qat_util or qat_driver is present.Affected if The installed version cannot be determined or verified
-
Compare the installed version against the vulnerable rangeCompare the discovered version number to the threshold 2.5.0-0007. Examine both the major.minor.patch components and the -#### build suffix to determine if the version is earlier than 2.5.0-0007.Affected if The installed version is less than 2.5.0-0007 (e.g., 2.4.x, 2.3.x, or any version without the 2.5.0-0007 patch level)
The environment is affected if Intel QuickAssist Technology is installed and the installed version is earlier than 2.5.0-0007.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.5.0-0007
Upgrade Intel QuickAssist Technology software to version 2.5.0 or later to address the vulnerability.
2.5.0-0007
- 1. Identify the currently installed version of Intel(R) QuickAssist Technology on the system
- 2. Verify the installed version is below 2.5.0-0007
- 3. Obtain the fixed version 2.5.0-0007 or later from Intel's official support channels (intel.com or Intel OneAPI SDK/QuickAssist downloads)
- 4. Follow Intel's standard upgrade procedure for QuickAssist Technology software
- 5. After upgrade, verify the new version is 2.5.0-0007 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-20090 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-20090 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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