Remote kernel panic via IPv6 fragment length overflow
Published Aug 1, 2023 · Updated Jul 9, 2025
Integer overflow in FreeBSD 12.4, 13.1, and 13.2 allows remote attackers to trigger a kernel panic via crafted IPv6 fragments. The frag6.c reassembly path stores the combined fragment payload length in the 16-bit ip6_plen field without first rejecting totals above IPV6_MAXPACKET. Unauthenticated IPv6 reachability is sufficient; affected release branches panic, interrupting the host until it restarts.
Summary
What happened
Integer overflow in FreeBSD 12.4, 13.1, and 13.2 allows remote attackers to trigger a kernel panic via crafted IPv6 fragments. The frag6.c reassembly path stores the combined fragment payload length in the 16-bit ip6_plen field without first rejecting totals above IPV6_MAXPACKET. Unauthenticated IPv6 reachability is sufficient; affected release branches panic, interrupting the host until it restarts.
The record
- CVE
- CVE-2023-3107
- Published
- Aug 1, 2023
- Updated
- Jul 9, 2025
- Vendor
- The FreeBSD Project
- Product
- FreeBSD
- Classifications
- CWE-190, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 1, 2023CVE publishedPublication date reported by the CVE source.
- Jul 9, 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=12.4-RELEASE <12.4-RELEASE-p4
- Affected versionversion=13.1-RELEASE <13.1-RELEASE-p9
- Affected versionversion=13.2-RELEASE <13.2-RELEASE-p2
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