Kernel panic via null controller dereference
Published Mar 26, 2026 · Updated Mar 26, 2026
Null pointer dereference in FreeBSD 15.0-RELEASE through p4 allows remote attackers to panic an NVMe/TCP target with an I/O CONNECT. In nvmft_handoff_io_queue(), the nonexistent-controller error path dereferences the null ctrlr pointer to log ctrlr->cntlid instead of using the received CNTLID value. Network access to an exposed NVMe/TCP target is sufficient, and a bogus or stale CNTLID crashes the kernel without authentication.
Summary
What happened
Null pointer dereference in FreeBSD 15.0-RELEASE through p4 allows remote attackers to panic an NVMe/TCP target with an I/O CONNECT. In nvmft_handoff_io_queue(), the nonexistent-controller error path dereferences the null ctrlr pointer to log ctrlr->cntlid instead of using the received CNTLID value. Network access to an exposed NVMe/TCP target is sufficient, and a bogus or stale CNTLID crashes the kernel without authentication.
The record
- CVE
- CVE-2026-4652
- Published
- Mar 26, 2026
- Updated
- Mar 26, 2026
- Vendor
- The FreeBSD Project
- Product
- FreeBSD
- Classifications
- CWE-476, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 26, 2026CVE publishedPublication date reported by the CVE source.
- Mar 26, 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=15.0-RELEASE <p5
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.
Weakness, pattern, technique
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