CVE-2025-24515
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 for some Intel(R) Graphics Drivers 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 · moderate confidenceA NULL pointer dereference vulnerability in Intel Graphics Drivers allows an authenticated local user to trigger a system crash (BSOD or kernel panic) by causing the driver to dereference a NULL pointer, resulting in denial of service.
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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/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 Intel Graphics Driver installationUse system utilities to locate Intel graphics hardware and driver. On Windows: open Device Manager, expand 'Display adapters'. On Linux: run 'lspci | grep -i vga' or 'lspci -k | grep -A3 -i vga' to see the driver in use.Affected if No Intel graphics hardware or driver present means the system is not affected by this CVE.
-
Determine installed Intel Graphics Driver versionOn Windows: right-click the Intel graphics device in Device Manager, select Properties, view the Driver version field. On Linux: check /var/log/Xorg.0.log or use 'modinfo i915' for kernel driver version.Affected if Unable to determine version or version differs from the patched version released by Intel for this CVE.
-
Check for recent kernel crash or BSOD eventsOn Windows: open Event Viewer, navigate to Windows Logs > System and look for Event ID 1001 (Bugcheck) or critical errors around the time of any crashes. On Linux: check 'dmesg', /var/log/kern.log, or journalctl for kernel oops or panic messages related to i915 or Intel GPU.Affected if Recent unexplained kernel panics or BSOD events mentioning NULL pointer dereference in graphics driver indicate possible exploitation.
-
Assess local user access controlsReview which local user accounts exist on the system and verify which users have authenticated access. The vulnerability requires an authenticated local user to trigger the NULL pointer dereference.Affected if Untrusted or low-privilege local user accounts exist and could potentially trigger the condition.
A system is affected if it runs an unpatched version of Intel Graphics Drivers for the specific hardware present, and the vulnerability can be triggered by any authenticated local user on 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 the Intel Graphics Driver update provided by Intel to patch the vulnerability. Ensure the updated driver is compatible with the system configuration before deployment.
- Consultation1.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 $1,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24515 — 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-2025-24515 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