dbcve.org
IpadosOperating system · Apple

CVE-2025-24257

HIGH · 7.1 CVSS v3.1 Published 2025-03-31
Fix available
A fix is available. Upgrade to 2.4 / 15.4 or later.
See remediation →
74/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
An out-of-bounds write issue was addressed with improved input validation. This issue is fixed in iOS 18.4 and iPadOS 18.4, macOS Sequoia 15.4, visionOS 2.4, watchOS 11.4. An app may be able to cause unexpected system termination or write 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

This is an out-of-bounds write vulnerability in Apple's kernel space affecting iOS, iPadOS, macOS, visionOS, and watchOS. The vulnerability allows a malicious application to write beyond allocated memory boundaries in kernel memory, potentially causing system crashes or achieving kernel-level code execution.

MitigationApply the available security updates (iOS 18.4, iPadOS 18.4, macOS Sequoia 15.4, visionOS 2.4, watchOS 11.4) which contain the fix with improved input validation to prevent the out-of-bounds write.

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:< 18.4
Iphone OsOperating system
Affected:< 18.4
macOSOperating system
Affected:>= 15.0, < 15.4
VisionosOperating system
Affected:< 2.4

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
None
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/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 checks

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

  1. Identify your Apple device type
    Determine whether your device is an iPhone (iOS), iPad (iPadOS), Mac (macOS), Vision Pro (visionOS), or Apple Watch (watchOS)
    Affected if The device runs any of the affected Apple operating systems
  2. Check iOS or iPadOS version
    On iPhone or iPad, go to Settings > General > About > Version and note the version number (for example, 18.3.1)
    Affected if Running iOS or iPadOS version lower than 18.4 (for example, 18.3.x, 17.x, etc.)
  3. Check macOS version
    On Mac, click the Apple menu > About This Mac, or run 'sw_vers' in Terminal, and note the version number (for example, 15.3)
    Affected if Running macOS version 15.0 through 15.3.x (versions 15.0, 15.1, 15.2, 15.3)
  4. Check visionOS version
    On Vision Pro, go to Settings > General > About and note the version number
    Affected if Running visionOS version lower than 2.4 (for example, 2.3.x, 2.2.x, etc.)

You are affected if your device runs iOS, iPadOS, or visionOS versions below 18.4/18.4/2.4 respectively, or macOS versions 15.0 through 15.3.x.

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 2.4 / 15.4 / 18.4 or later
Fixed in 2.415.418.4
Interim mitigation

Apply the available security updates (iOS 18.4, iPadOS 18.4, macOS Sequoia 15.4, visionOS 2.4, watchOS 11.4) which contain the fix with improved input validation to prevent the out-of-bounds write.

Recommended fix High confidence

iOS 18.4, iPadOS 18.4, macOS Sequoia 15.4, visionOS 2.4 (depending on device)

  1. For iPhone: Upgrade to iOS 18.4 via Settings > General > Software Update
  2. For iPad: Upgrade to iPadOS 18.4 via Settings > General > Software Update
  3. For Mac: Upgrade to macOS Sequoia 15.4 via System Settings > General > Software Update
  4. For Vision Pro: Upgrade to visionOS 2.4 via Settings > General > Software Update
Caveat Standard OS update considerations - backup data before upgrading, ensure compatibility with critical apps

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

Fix this in Ipados Scoped from the published advisory
  • Consultation3.0 h
  • Implementation5.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,310
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-24257 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2025-24257 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