CVE-2025-24152
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 issue was addressed with improved memory handling. This issue is fixed in macOS Sequoia 15.3. An app may be able to cause unexpected system termination or corrupt 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 · moderate confidenceKernel memory handling vulnerability in macOS Sequoia allowing a malicious application to cause unexpected system termination (DoS) or corrupt kernel memory. The fix involves improved memory handling in the kernel.
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.3CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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.
-
Identify macOS versionRun 'sw_vers -productVersion' in Terminal to get the macOS version number (e.g., 15.2, 15.3, 15.4)Affected if Version shows 15.0, 15.1, or 15.2 (any version below 15.3)
-
Confirm macOS Sequoia releaseCheck that the version starts with '15.' which indicates macOS Sequoia (15.x is Sequoia)Affected if Version begins with 15.x and is less than 15.3
-
Verify kernel build dateRun 'uname -v' to see the kernel build string; for Sequoia 15.3 this would be 'Darwin Kernel Version 25.3.0' or laterAffected if Kernel version shows Darwin 25.x with version number below 25.3.0 (e.g., 25.0.0, 25.1.0, 25.2.0)
-
Check System Preferences for update statusOpen System Settings > General > Software Update to see if macOS 15.3 or later is available or installedAffected if Software Update shows an available update to 15.3 or later, or indicates the system is running an earlier version
A system is affected if it is running any version of macOS Sequoia (15.x) prior to version 15.3, as the kernel memory handling flaw exists in those earlier kernel versions.
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 · scoped15.3
Apply macOS Sequoia 15.3 or later to receive the kernel memory handling improvements. No application-level code changes are typically needed for kernel vulnerabilities unless the issue stems from improper API usage.
macOS Sequoia 15.3
- Back up your Mac using Time Machine or another backup solution before upgrading
- Connect your Mac to a power source to ensure the update completes without interruption
- Open System Settings (or System Preferences on older macOS versions)
- Click on General in the sidebar
- Click on Software Update
- If macOS Sequoia 15.3 is available, click Update Now to install it
- Restart your Mac when prompted to complete the installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24152 — 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-2025-24152 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