Kernel memory disclosure via sockaddr over-copy
Published Jan 30, 2025 · Updated Feb 7, 2025
Uninitialized memory exposure in FreeBSD 14.2-RELEASE allows local users to read 14 bytes of kernel heap data through ktrace. The ktrcapfail() path records a variable-length sockaddr as a full struct sockaddr, copying up to 14 trailing uninitialized bytes into the userspace trace. An unprivileged local program must trigger the affected capability-mode trace path, and disclosure is limited to 14 bytes per event.
Summary
What happened
Uninitialized memory exposure in FreeBSD 14.2-RELEASE allows local users to read 14 bytes of kernel heap data through ktrace. The ktrcapfail() path records a variable-length sockaddr as a full struct sockaddr, copying up to 14 trailing uninitialized bytes into the userspace trace. An unprivileged local program must trigger the affected capability-mode trace path, and disclosure is limited to 14 bytes per event.
The record
- CVE
- CVE-2025-0662
- Published
- Jan 30, 2025
- Updated
- Feb 7, 2025
- Vendor
- The FreeBSD Project
- Product
- FreeBSD
- Classifications
- CWE-122, T1005
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Jan 30, 2025CVE publishedPublication date reported by the CVE source.
- Feb 7, 2025Record 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=14.2-RELEASE <p1
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