CVE-2015-7076
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 · uneditedThe Intel Graphics Driver component in Apple OS X before 10.11.2 allows local users to gain privileges or cause a denial of service (NULL pointer dereference) via unspecified vectors.
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 local privilege escalation vulnerability exists in the Intel Graphics Driver component of Apple OS X versions prior to 10.11.2. The flaw allows a local attacker to potentially gain elevated (root) privileges or cause a denial of service by triggering a NULL pointer dereference through unspecified vectors in the graphics driver.
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<= 10.11.1CVSS 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
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:L/Au:N/C:C/I:C/A:C
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 installed OS X versionOpen System Preferences > General, or run 'sw_vers' in Terminal to display the system versionAffected if The version displayed is 10.11.1 or earlier (10.11.0, 10.10.x, etc.)
-
Identify Intel Graphics Driver componentCheck for the presence of Intel graphics-related kernel extensions (kexts) in /System/Library/Extensions/ - look for files such as IntelGraphicsPowerManagement.kext, IntelHDGraphics.kext, or similar Intel GPU driver kextsAffected if Intel graphics driver kexts are present on the system
-
Verify graphics driver is loadedRun 'kextstat | grep -i intel' in Terminal to list loaded Intel kernel extensionsAffected if Any Intel graphics driver kexts are loaded and active
-
Confirm system is not patchedCompare your installed OS X version against the fixed version 10.11.2 - check Apple Security Update 2015-002 or later is installedAffected if The system remains at OS X 10.11.1 or earlier and has not received the security update
The system is affected if it runs OS X 10.11.1 or earlier with Intel Graphics Driver loaded, and has not applied the OS X 10.11.2 security update.
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 Apple security update OS X 10.11.2 or later, which includes the patched Intel Graphics Driver. For enterprise environments, deploy the update via MDM or patch management systems to ensure all affected systems are remediated.
- Consultation1.0 h
- Implementation2.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-7076 — 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-2015-7076 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