CVE-2022-42879
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 · uneditedNULL pointer dereference in some Intel(R) Arc(TM) Control software before version 1.73.5335.2 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 confidenceA NULL pointer dereference vulnerability exists in Intel Arc Control software versions prior to 1.73.5335.2. An authenticated local user can trigger this condition, causing the software to crash and resulting in denial of service. The vulnerability requires local access and user authentication, reducing its exploitability scope.
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< 31.0.101.4255CVSS 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.
-
Check if Intel Arc Control software is installedUse system inventory or software management tools to enumerate installed applications and look for Intel Arc ControlAffected if Intel Arc Control is found installed on the system
-
Determine installed Intel Arc Control versionAccess the software's built-in version information through its UI, help menu, or system registryAffected if The installed version is lower than 1.73.5335.2
-
Check Intel Graphics Driver versionUse Device Manager, Intel Graphics Command Center, or run dxdiag to view the installed graphics driver versionAffected if The driver version is lower than 31.0.101.4255
-
Verify if Intel Arc Control feature is actively usedCheck if the Intel Arc Control service or related components are running or configured to startAffected if The software is running and accessible to local authenticated users
A user is affected if Intel Arc Control software prior to version 1.73.5335.2 or Intel Graphics Driver version below 31.0.101.4255 is installed and the software is accessible to local authenticated users.
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 · scoped31.0.101.4255
Update Intel Arc Control software to version 1.73.5335.2 or later. In enterprise environments, test the update against specific GPU hardware configurations before broad deployment.
Intel Arc Control software version 1.73.5335.2
- Navigate to Intel's official support website for Intel Arc Control software
- Locate the download section for Intel Arc Control
- Download version 1.73.5335.2 or later
- Run the installer with administrator privileges
- Follow the on-screen installation prompts
- Restart the system if prompted
- Verify the installed version matches 1.73.5335.2 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-42879 — 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-42879 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