IpadosOperating system · Apple

CVE-2022-32825

MEDIUM · 5.5 CVSS v3.1 Published 2022-09-23
Fix available
A fix is available. Upgrade to 8.7 / 11.6.8 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges

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 · unedited
The issue was addressed with improved memory handling. This issue is fixed in iOS 15.6 and iPadOS 15.6, macOS Big Sur 11.6.8, watchOS 8.7, tvOS 15.6, macOS Monterey 12.5. An app may be able to disclose kernel memory.

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 confidence

A memory handling flaw in the Apple kernel allows a local malicious application to read kernel memory contents, leading to information disclosure. The vulnerability exists across multiple Apple platforms and enables privilege escalation through kernel memory exposure.

MitigationApply the vendor-supplied patches by updating to iOS 15.6+, iPadOS 15.6+, macOS Big Sur 11.6.8+, macOS Monterey 12.5+, watchOS 8.7+, or tvOS 15.6+ as appropriate for each affected system.

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
IpadosOperating system
Affected:< 15.6
Iphone OsOperating system
Affected:< 15.6
macOSOperating system
Affected:>= 11.0, < 11.6.8>= 12.0, < 12.5
TvosOperating system
Affected:< 15.6
WatchosOperating system
Affected:< 8.7

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify macOS version
    Run 'sw_vers -productVersion' in Terminal or check System Preferences > About
    Affected if Version is 11.0-11.6.7 (any 11.x before 11.6.8) or 12.0-12.4 (any 12.x before 12.5)
  2. Identify iOS/iPadOS version
    Open Settings > General > About on the device and note the Version field
    Affected if Version is below 15.6 (for example 15.5, 15.4, etc.)
  3. Identify tvOS version
    Check Settings > General > About > Version on the Apple TV
    Affected if Version is below 15.6
  4. Identify watchOS version
    Check the Watch app on paired iPhone > General > About, or open Settings > General > About on the Watch
    Affected if Version is below 8.7
  5. Confirm patch status
    On macOS, run 'system_profiler SPSoftwareDataType' and check for 'Security Update' entries; on iOS devices check Settings > General > Software Update to confirm no update is available
    Affected if No vendor security patch has been applied and the OS version falls within the affected ranges

The system is affected if it is running any unpatched version of iOS, iPadOS, macOS, tvOS, or watchOS within the vulnerable version ranges (iOS/iPadOS/tvOS/watchOS below 15.6 or 8.7 respectively; macOS 11.x before 11.6.8 or 12.x before 12.5).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 8.7 / 11.6.8 / 12.5 or later
Fixed in 8.711.6.812.5
Interim mitigation

Apply the vendor-supplied patches by updating to iOS 15.6+, iPadOS 15.6+, macOS Big Sur 11.6.8+, macOS Monterey 12.5+, watchOS 8.7+, or tvOS 15.6+ as appropriate for each affected system.

Recommended fix High confidence

iOS 15.6 / iPadOS 15.6 / macOS Big Sur 11.6.8 / macOS Monterey 12.5 / watchOS 8.7 / tvOS 15.6

  1. Back up your iOS device before upgrading using iTunes or iCloud
  2. On your iPhone, go to Settings > General > Software Update to check for and install iOS 15.6
  3. On your iPad, go to Settings > General > Software Update to check for and install iPadOS 15.6
  4. For Apple Watch, open the Watch app on your iPhone and go to General > Software Update to install watchOS 8.7
  5. For Apple TV, go to Settings > System > Software Updates to install tvOS 15.6
  6. For Mac, go to System Preferences > Software Update to install the appropriate macOS update (macOS Big Sur 11.6.8 or macOS Monterey 12.5)
Caveat Standard OS upgrade considerations apply - ensure app compatibility and backup before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ipados Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-32825 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-32825 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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