CVE-2022-42864
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 · uneditedA race condition was addressed with improved state handling. This issue is fixed in tvOS 16.2, macOS Monterey 12.6.2, macOS Ventura 13.1, macOS Big Sur 11.7.2, iOS 15.7.2 and iPadOS 15.7.2, iOS 16.2 and iPadOS 16.2, watchOS 9.2. An app may be able to execute arbitrary code with kernel privileges.
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 race condition in Apple kernel components allows a malicious application to potentially execute arbitrary code with kernel-level privileges. The vulnerability involves improper state handling during a specific timing window that can be exploited to escalate privileges from userland to kernel mode.
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< 15.7.2>= 16.0, < 16.2< 15.7.2>= 16.0, < 16.2< 11.7.2>= 12.0, < 12.6.2= 13.0< 16.2< 9.2CVSS 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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/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 macOS versionRun 'sw_vers -productVersion' in TerminalAffected if Version is less than 11.7.2, OR between 12.0 and 12.6.1 inclusive, OR exactly 13.0
-
Identify iOS or iPadOS versionGo to Settings > General > About on the device and note the version numberAffected if Version is less than 15.7.2, OR between 16.0 and 16.1 inclusive
-
Identify tvOS versionGo to Settings > General > About TV on the Apple TV and note the version numberAffected if Version is less than 16.2
-
Identify watchOS versionOpen the Watch app on iPhone, go to My Watch > General > About and note the version numberAffected if Version is less than 9.2
The device is affected if its OS version falls within any of the specified vulnerable ranges for macOS, iOS, iPadOS, tvOS, or watchOS.
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 · scoped9.211.7.212.6.2
Apply the appropriate Apple security update for the affected OS version (iOS 15.7.2/16.2, iPadOS 15.7.2/16.2, macOS 11.7.2/12.6.2/13.1, tvOS 16.2, or watchOS 9.2) to all managed devices. Prioritize devices running affected versions based on exposure and risk.
iOS 15.7.2/16.2+, iPadOS 15.7.2/16.2+, macOS 11.7.2+/12.6.2+/13.1+, tvOS 16.2+, watchOS 9.2+
- For iPhone/iPad: Upgrade to iOS/iPadOS 15.7.2 or later (or iOS/iPadOS 16.2 and later)
- For macOS Big Sur (11.x): Upgrade to macOS Big Sur 11.7.2 or later
- For macOS Monterey (12.x): Upgrade to macOS Monterey 12.6.2 or later
- For macOS Ventura (13.0): Upgrade to macOS Ventura 13.1 or later
- For tvOS: Upgrade to tvOS 16.2 or later
- For watchOS: Upgrade to watchOS 9.2 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-42864 — 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-42864 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