CVE-2024-37355
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 in some Intel(R) Graphics software may allow an authenticated user to potentially enable escalation of privilege 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 confidenceThis is an improper access control vulnerability in Intel Graphics software that allows an authenticated local user to potentially escalate privileges. The vulnerability stems from insufficient access control checks in the graphics driver or related software components, enabling a user with valid credentials to gain elevated system privileges beyond what their account should normally permit.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/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 Graphics software installationOn Windows, run 'msinfo32' and look for 'Intel(R) Graphics' under Components > Display, or check Device Manager > Display adapters. On Linux, run 'lspci | grep -i vga' or check /usr/lib/x86_64-linux-gnu/dri/*.so files for Intel drivers.Affected if Intel Graphics hardware or drivers are present on the system
-
Determine Intel Graphics driver versionOn Windows, right-click the Intel Graphics entry in Device Manager, select Properties > Driver tab, and note the Driver Version. On Linux, run 'cat /sys/class/drm/card0/device/driver' and check the driver version via 'modinfo i915' or 'intel_gpu_top' if available.Affected if Unable to retrieve a version number indicates the driver may not be properly installed or is a non-standard variant
-
Check for authenticated local user accessReview system accounts and user privileges using 'net user' on Windows or 'cat /etc/passwd' and 'getent group' on Linux. Identify whether untrusted or low-privilege local users exist on the system.Affected if The system has local user accounts beyond the administrator or primary user, making privilege escalation relevant
-
Verify graphics driver service configurationOn Windows, check if the Intel Graphics service (igfxCUIService or similar) runs with elevated privileges via Services.msc. On Linux, check /etc/security/permissions and driver module loading configuration for proper file permissions.Affected if Graphics driver services run with elevated privileges and file permissions on driver components are overly permissive
A user is affected if Intel Graphics software is installed and the system has local user accounts, as the vulnerability allows an authenticated local user to escalate privileges through insufficient access control in the graphics driver components.
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 the relevant Intel Graphics software patch or update provided by Intel to remediate this vulnerability. As this is a local privilege escalation issue, prioritize patching systems with direct user access, particularly those with untrusted local users.
- Consultation2.0 h
- Implementation4.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-37355 — 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-2024-37355 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