CVE-2022-38973
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 access control for some Intel(R) Arc(TM) graphics cards A770 and A750 Limited Edition sold between October of 2022 and December of 2022 may allow an authenticated user to potentially enable denial of service or infomation 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 · moderate confidenceImproper access control in Intel Arc A770 and A750 Limited Edition graphics cards sold between October-December 2022 allows an authenticated local user to potentially cause denial of service or information disclosure. The vulnerability requires local access and user authentication.
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 dataall versionsall versionsCVSS 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
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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 Intel Arc GPU hardwareUse system information tools (such as lspci -v on Linux, Device Manager on Windows, or system profiling utilities) to enumerate installed graphics hardware and confirm an Intel Arc A750 or A770 is presentAffected if An Intel Arc A750 or A770 graphics card is detected in the system
-
Confirm Limited Edition variantCheck the card model designation through system information, GPU utilities, or physical inspection of the card's packaging/label to determine if it is the Limited Edition variantAffected if The installed card is specifically an Intel Arc A750 or A770 Limited Edition model
-
Determine manufacturing date windowInspect the card's serial number, batch code, or manufacturing date printed on the hardware label, or query the GPU firmware for date information if available. Cross-reference with the card's purchase documentation or receiptAffected if The card's manufacturing date falls within October through December 2022, indicating it is from the affected production window
-
Verify local user authentication contextConfirm that the user checking the system has authenticated local access to the machine (logged in with valid credentials or able to authenticate)Affected if The evaluator has authenticated local access to the system where the affected Intel Arc GPU is installed
The system is affected if it contains an Intel Arc A750 or A770 Limited Edition graphics card manufactured between October and December 2022, and the evaluator has authenticated local user access to that system.
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.
From vendor dataApply Intel-provided firmware and driver updates for affected Arc A770 and A750 Limited Edition graphics cards. Users should verify their card's manufacturing date and contact Intel support if within the affected window.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-38973 — 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-2022-38973 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