CVE-2023-22338
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 · uneditedOut-of-bounds read in some Intel(R) oneVPL GPU software before version 22.6.5 may allow an authenticated user to potentially enable information disclosure 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 out-of-bounds read vulnerability that allows an authenticated local user to read memory beyond intended boundaries, potentially exposing sensitive information. The flaw exists in the video processing library's memory handling during GPU-accelerated operations.
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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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.
-
Verify if Intel oneVPL GPU Runtime is installedOn Linux, run 'rpm -qa | grep -i onevpl' or check for the presence of libvpl.so library files in /usr/lib/ or /opt/intel/ directoriesAffected if No oneVPL packages or library files are found, meaning the software is not installed and the CVE does not apply
-
Determine the installed version of Intel oneVPL GPU RuntimeRun 'rpm -q libvpl' or 'dpkg -l | grep vpl' to query the installed package version; alternatively, check the library version with 'strings libvpl.so | grep version' or review the package metadataAffected if The installed version is earlier than 22.6.5, indicating the vulnerability is present
-
Identify the host Fedora version if applicableRun 'cat /etc/fedora-release' or 'fedora-release' command to confirm the installed Fedora versionAffected if Running Fedora 37, 38, or 39 with oneVPL installed indicates potential exposure to the Fedora-specific affected versions
-
Confirm the oneVPL video processing components are in useReview application dependencies and logs to determine if any software links against libvpl.so or invokes oneVPL API calls for GPU-accelerated video processing; check for packages like 'intel-onevpl' or 'intel-onevpl-devel'Affected if Applications actively using the oneVPL library for video processing operations on an affected version are vulnerable to the out-of-bounds read
The environment is affected if Intel oneVPL GPU Runtime version is below 22.6.5, or if running Fedora 37/38/39 with a vulnerable oneVPL version installed and actively processing video content.
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. Since this is a vendor-supplied library update, apply through Intel's official distribution channels and verify compatibility with dependent applications.
oneVPL GPU Runtime version 22.6.5 or later
- Identify the installed OneVPL package: `dnf list installed '*onevpl*'` or `rpm -qa | grep onevpl`
- Update the OneVPL package to the fixed version: `sudo dnf update onevpl-gpu-runtime` or `sudo dnf update libvpl`
- Verify the installed version meets the fixed version requirement (22.6.5 or later): `dnf list installed onevpl-gpu-runtime`
- If the fixed version is not available in the current Fedora repositories, enable update-testing or wait for the security update to propagate: `sudo dnf check-update`
- Restart any applications or services using the OneVPL library after the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-22338 — 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-22338 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