CVE-2025-30444
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 locking. This issue is fixed in macOS Sequoia 15.4, macOS Sonoma 14.7.5, macOS Ventura 13.7.5. Mounting a maliciously crafted SMB network share may lead to system termination.
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 confidenceA race condition vulnerability exists in macOS SMB share mounting functionality. When mounting a maliciously crafted SMB network share, an attacker can trigger a race condition that leads to system termination (kernel panic). The vulnerability is fixed in macOS Sequoia 15.4, Sonoma 14.7.5, and Ventura 13.7.5.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 installed macOS versionRun 'sw_vers -productVersion' in Terminal or go to System Settings > General > About to view the macOS version number.Affected if The version is 13.0 to 13.7.4, 14.0 to 14.7.4, or 15.0 to 15.3 (any version in the < 13.7.5, < 14.7.5, or < 15.4 ranges).
-
Confirm SMB file sharing is enabledRun 'smbutil status' in Terminal or check System Settings > General > Sharing > File Sharing to see if SMB service is active.Affected if SMB file sharing is turned ON, as this is the attack surface for mounting malicious shares.
-
Check if SMB client is loadedRun 'launchctl list | grep -i smb' to see if SMB-related services are running on the system.Affected if Any SMB-related services (smb, netbios, etc.) are actively running.
The system is affected if the installed macOS version falls within any of the vulnerable ranges (13.x before 13.7.5, 14.x before 14.7.5, or 15.x before 15.4) AND SMB file sharing functionality is available or enabled on the machine.
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 all affected systems. Until patched, avoid mounting untrusted or unfamiliar SMB network shares.
macOS Ventura 13.7.5 / macOS Sonoma 14.7.5 / macOS Sequoia 15.4 (depending on your current major version)
- Back up critical data before any system update
- Open System Settings > General > Software Update
- Ensure the device is connected to power and WiFi
- Install macOS Ventura 13.7.5, Sonoma 14.7.5, or Sequoia 15.4 depending on your current macOS version
- Restart the system when prompted to complete the update
- Verify the update was applied by checking System Settings > General > About > System Version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30444 — 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-30444 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