CVE-2023-22840
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 · uneditedImproper neutralization in software for the Intel(R) oneVPL GPU software before version 22.6.5 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 · high confidenceIntel oneVPL GPU software before version 22.6.5 contains an improper input validation (neutralization) vulnerability allowing an authenticated local user 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= 37= 38= 39< 22.6.5CVSS 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 oneVPL is installedOn Linux, check for installed packages using package manager commands (e.g., rpm -qa | grep -i onevpl, dpkg -l | grep -i onevpl, or rpm -qi libvpl). On Windows, check Programs and Features or the installation directory for oneVPL components.Affected if Intel oneVPL GPU Runtime package is found on the system
-
Determine the installed versionRetrieve the version of the installed Intel oneVPL package. On Linux, use commands such as 'rpm -qi <package-name>', 'dpkg -s <package-name>', or check the file version of libvpl.so in the installation directory. On Windows, right-click the DLL file, select Properties, and check the File Version attribute.Affected if A version number is returned that can be compared against 22.6.5
-
Compare version against the affected rangeParse the installed version number and compare it numerically to 22.6.5. Ensure you are comparing the full version string (e.g., 22.6.0, 22.5.0, 22.6.5).Affected if The installed version is lower than 22.6.5 (for example, 22.6.0, 22.5.x, or any version string that sorts lexicographically or numerically below 22.6.5)
-
Confirm the operating system if using FedoraCheck the Fedora version by running 'cat /etc/fedora-release' or 'rpm -q fedora-release'. This step applies only if oneVPL was installed via Fedora repositories.Affected if The system is running Fedora 37, 38, or 39 and has Intel oneVPL installed from that distribution
The environment is affected if Intel oneVPL GPU Runtime is installed and its version is less than 22.6.5, or if using Fedora 37, 38, or 39 with the distribution-provided package.
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 · scoped22.6.5
Update Intel oneVPL GPU software to version 22.6.5 or later to remediate this vulnerability.
Intel oneVPL GPU Runtime version 22.6.5 or later
- Update Intel oneVPL GPU Runtime to version 22.6.5 or later by downloading from Intel's official website or your system's package manager
- For Fedora systems, run 'sudo dnf update' or 'sudo dnf upgrade' to receive the patched packages for versions 37, 38, and 39
- Verify the installed version using 'rpm -q intel-onevpl' or similar package query command
- Restart any applications or services that utilize the oneVPL GPU runtime after the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-22840 — 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-2023-22840 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