Service disablement via per-report socket descriptor leak
Published Mar 9, 2026 · Updated Mar 9, 2026
Resource exhaustion in blocklistd in The FreeBSD Project FreeBSD 15.0-RELEASE through p2 allows remote attackers to disable IP blocking. The process() function leaves bi_fd open after every adverse event report instead of closing the received descriptor on all exits. A large pool of sacrificial IP addresses accelerates exhaustion until blocklistd cannot run its helper or accept reports, while routine events eventually cause the same failure.
Summary
What happened
Resource exhaustion in blocklistd in The FreeBSD Project FreeBSD 15.0-RELEASE through p2 allows remote attackers to disable IP blocking. The process() function leaves bi_fd open after every adverse event report instead of closing the received descriptor on all exits. A large pool of sacrificial IP addresses accelerates exhaustion until blocklistd cannot run its helper or accept reports, while routine events eventually cause the same failure.
The record
- CVE
- CVE-2026-2261
- Published
- Mar 9, 2026
- Updated
- Mar 9, 2026
- Vendor
- The FreeBSD Project
- Product
- FreeBSD
- Classifications
- CWE-772, T1499.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 9, 2026CVE publishedPublication date reported by the CVE source.
- Mar 9, 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 <p3
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.
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