CVE-2016-1814
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 · uneditedIOAcceleratorFamily in Apple iOS before 9.3.2, OS X before 10.11.5, and tvOS before 9.2.1 allows attackers to cause a denial of service (NULL pointer dereference) via a crafted app.
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 confidenceIOAcceleratorFamily in Apple iOS, OS X, and tvOS contains a NULL pointer dereference vulnerability in the graphics accelerator driver component. A locally running crafted application can trigger this condition, causing the system to crash and resulting in denial of service.
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.5< 9.3.2< 9.2.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
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/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 the installed OS versionOn macOS, go to Apple menu > About This Mac to see the version number. On iOS, go to Settings > General > About to see the version. On tvOS, go to Settings > General > About to see the version.Affected if The OS version is earlier than 10.11.5 for macOS, earlier than 9.3.2 for iOS, or earlier than 9.2.1 for tvOS
-
Verify the IOAcceleratorFamily kernel extension is presentOn macOS, run 'kextstat | grep -i IOAccelerator' in Terminal to list loaded IOAccelerator-related kernel extensions.Affected if The IOAcceleratorFamily kernel extension is loaded and the OS version is in the affected range
-
Review system crash logs for IOAcceleratorFamily faultsOn macOS, open Console.app and filter for crash logs containing 'IOAccelerator' or 'AppleIntelHD3000Graphics' around the time of any unexpected shutdowns or kernel panics.Affected if Crash logs show NULL pointer dereference errors in IOAcceleratorFamily and the OS version is below the fixed releases
A user is affected if they are running an unpatched version of macOS below 10.11.5, iOS below 9.3.2, or tvOS below 9.2.1, and the IOAcceleratorFamily graphics driver component is present and triggered by a local application.
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 data9.2.19.3.210.11.5
Update the affected Apple operating systems to the patched versions: iOS 9.3.2 or later, OS X 10.11.5 or later, or tvOS 9.2.1 or later.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-1814 — 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-2016-1814 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