System crash via undisclosed SMB memory handling
Published Mar 31, 2025 · Updated Apr 2, 2026
Memory-handling flaw in SMB in Apple macOS before 15.4 allows local users to cause a system crash through a local app. Apple identifies improved memory handling as the correction but has not disclosed the SMB code locus or unsafe memory operation. A local app must reach the affected SMB functionality, and the documented consequence is system termination rather than data access or code execution.
Summary
What happened
Memory-handling flaw in SMB in Apple macOS before 15.4 allows local users to cause a system crash through a local app. Apple identifies improved memory handling as the correction but has not disclosed the SMB code locus or unsafe memory operation. A local app must reach the affected SMB functionality, and the documented consequence is system termination rather than data access or code execution.
The record
- CVE
- CVE-2025-24269
- Published
- Mar 31, 2025
- Updated
- Apr 2, 2026
- Vendor
- Apple
- Product
- macOS
- Classifications
- CWE-400, T1499
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Mar 31, 2025CVE publishedPublication date reported by the CVE source.
- Apr 2, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <15.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo