Kernel crash via incorrect WireGuard packet sizing
Published Mar 20, 2025 · Updated Mar 21, 2025
Incorrect buffer sizing in OpenBSD 7.5 before errata 015 and 7.6 before errata 006 allows remote authenticated users to crash the kernel. The wg_encap() path capped plaintext_len at the peer MTU even though subsequent mbuf handling did not accommodate that truncation, producing inconsistent packet and buffer lengths. Reachability requires a configured WireGuard peer able to send tunnel traffic; successful exploitation interrupts the entire system by crashing its kernel.
Summary
What happened
Incorrect buffer sizing in OpenBSD 7.5 before errata 015 and 7.6 before errata 006 allows remote authenticated users to crash the kernel. The wg_encap() path capped plaintext_len at the peer MTU even though subsequent mbuf handling did not accommodate that truncation, producing inconsistent packet and buffer lengths. Reachability requires a configured WireGuard peer able to send tunnel traffic; successful exploitation interrupts the entire system by crashing its kernel.
The record
- CVE
- CVE-2025-30334
- Published
- Mar 20, 2025
- Updated
- Mar 21, 2025
- Vendor
- OpenBSD Project
- Product
- OpenBSD
- Classifications
- CWE-131, T1499.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 20, 2025CVE publishedPublication date reported by the CVE source.
- Mar 21, 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=7.5 <7.5 errata 015
- Affected versionversion=7.6 <7.6 errata 006
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