Quick answers
- Is CVE-2026-7764 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-7764 being exploited in the wild.
- How severe is CVE-2026-7764?
- Informational severity, published 4 June 2026.
- Which products and versions are affected?
- Morse Micro HaLowLink 2 prior to 2.11.12.
- Is there a fix for CVE-2026-7764?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-7764 attacked?
- It is attacked from the adjacent network, in device firmware.
- Am I affected by CVE-2026-7764?
- Check whether you run Morse Micro HaLowLink 2 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An out-of-bounds read vulnerability exists in the morse.ko kernel driver due to insufficient validation of Vendor Information Element (IE) lengths. Specifically, the function morse_vendor_find_vendor_ie() only verifies that an IE is longer than 3 bytes before passing it to functions that read at fixed offsets. An attacker can transmit a crafted 802.11ah beacon or probe response frame with an undersized IE to trigger a heap out-of-bounds read of up to 9 bytes. This can result in a kernel panic (DoS) or the disclosure of kernel heap memory. The vulnerability is exploitable by any unauthenticated attacker within radio range without user interaction. This issue is resolved in HaLowLink 2 version 2.11.12.
Affected products
- Morse Micro HaLowLink 2 prior to 2.11.12
Timeline
- 2026-06-04: advisory: NVD publication date
- 2026-06-04: disclosed: Public disclosure of CVE-2026-7764