Kernel panic via loopback IPv6 use-after-free
Published Mar 26, 2021 · Updated Aug 4, 2024
Kernel use-after-free in FreeBSD 11.4-PRERELEASE before r360733 and 11.3-RELEASE before p13 allows local users to crash the system. Kernel mbuf handling leaves freed packet memory reachable when IPv6 Hop-by-Hop options are sent through the loopback interface. Any local account with socket API access can trigger a kernel panic, interrupting every service on the host.
Summary
What happened
Kernel use-after-free in FreeBSD 11.4-PRERELEASE before r360733 and 11.3-RELEASE before p13 allows local users to crash the system. Kernel mbuf handling leaves freed packet memory reachable when IPv6 Hop-by-Hop options are sent through the loopback interface. Any local account with socket API access can trigger a kernel panic, interrupting every service on the host.
The record
- CVE
- CVE-2020-7462
- Published
- Mar 26, 2021
- Updated
- Aug 4, 2024
- Vendor
- The FreeBSD Project
- Product
- FreeBSD
- Classifications
- CWE-416, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 26, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record 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=FreeBSD 11.3-RELEASE before p13
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