CVE-2025-24228
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 buffer overflow issue was addressed with improved memory handling. This issue is fixed in macOS Sequoia 15.4, macOS Sonoma 14.7.5, macOS Ventura 13.7.5. 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 buffer overflow vulnerability in the macOS kernel allows a malicious application to escalate privileges and execute arbitrary code with kernel-level access. This is a privilege escalation issue where user-space code can gain ring-0 execution capabilities.
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>= 13.0, < 13.7.5>= 14.0, < 14.7.5>= 15.0, < 15.4CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/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.
-
Check the installed macOS versionRun 'sw_vers -productVersion' in Terminal or view System Settings > About > macOS versionAffected if The version returned is 13.0 to 13.7.4, 14.0 to 14.7.4, or 15.0 to 15.3.x (any version below 13.7.5, 14.7.5, or 15.4)
-
Confirm the Darwin kernel versionRun 'uname -r' in Terminal to get the kernel release numberAffected if The kernel version corresponds to an affected macOS release (kernel versions below the ones shipped with 13.7.5, 14.7.5, or 15.4)
-
Check if macOS security updates are installedView System Settings > General > Software Update and check the installed security update history, or run 'defaults read /Library/Preferences/com.apple.SoftwareUpdate.plist LastSuccessfulDate'Affected if The system has not received the security update released for this vulnerability (the specific patches dated with the CVE)
-
Verify System Integrity Protection statusRun 'csrutil status' in Terminal (requires recovery mode to change)Affected if SIP is disabled - while not the primary detection method, a disabled SIP increases exploitability of kernel vulnerabilities; however, the vulnerability exists regardless of SIP status
A system is affected if it runs macOS Ventura 13.0-13.7.4, Sonoma 14.0-14.7.4, or Sequoia 15.0-15.3.x without the corresponding security update installed.
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 · scoped13.7.514.7.515.4
Apply the appropriate macOS security update (15.4 for Sequoia, 14.7.5 for Sonoma, or 13.7.5 for Ventura) to patch the kernel buffer overflow. Prioritize updates for systems running untrusted applications.
macOS 13.7.5 (Ventura), macOS 14.7.5 (Sonoma), or macOS 15.4 (Sequoia) depending on your current major version
- 1. Back up your Mac using Time Machine or another backup solution before upgrading.
- 2. Connect your Mac to power to ensure the update process is not interrupted.
- 3. Open System Settings (or System Preferences on older macOS versions).
- 4. Click on General in the sidebar.
- 5. Click Software Update.
- 6. If an update is available, click Update Now to download and install the appropriate version: macOS 13.7.5 for Ventura, macOS 14.7.5 for Sonoma, or macOS 15.4 for Sequoia.
- 7. Allow the update to complete; your Mac may restart several times.
- 8. After the update completes, verify the installed version by going to System Settings > General > About and confirm the macOS version matches the expected patched release.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24228 — 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-24228 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