Code execution via ctl_write_buffer use-after-free
Published Sep 5, 2024 · Updated Nov 4, 2025
Use-after-free in FreeBSD ctl before 13.3-RELEASE-p6, 14.0-RELEASE-p10, and 14.1-RELEASE-p4 allows attackers to execute code. ctl_write_buffer marks a persistent LUN buffer as request-allocated, so command completion frees memory still referenced by lun->write_buffer. Exposure requires either a bhyve guest with virtio_scsi or an iSCSI target; code runs in sandboxed bhyve userspace or on the target host.
Summary
What happened
Use-after-free in FreeBSD ctl before 13.3-RELEASE-p6, 14.0-RELEASE-p10, and 14.1-RELEASE-p4 allows attackers to execute code. ctl_write_buffer marks a persistent LUN buffer as request-allocated, so command completion frees memory still referenced by lun->write_buffer. Exposure requires either a bhyve guest with virtio_scsi or an iSCSI target; code runs in sandboxed bhyve userspace or on the target host.
The record
- CVE
- CVE-2024-45063
- Published
- Sep 5, 2024
- Updated
- Nov 4, 2025
- Vendor
- The FreeBSD Project
- Product
- FreeBSD
- Classifications
- CWE-416, T1210
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 5, 2024CVE publishedPublication date reported by the CVE source.
- Nov 4, 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=13.3 <13.3_p6
- Affected versionversion=13.3-RELEASE <p6
- Affected versionversion=14.0 <14.0_p10
- Affected versionversion=14.0-RELEASE <p10
- Affected versionversion=14.1 <14.1_p4
- Affected versionversion=14.1-RELEASE <p4
What conditions does exploitation require?
What is affected?
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