Quick answers
- Is CVE-2026-7762 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-7762 being exploited in the wild.
- How severe is CVE-2026-7762?
- Informational severity, with a CVSS score of 8.8, published 5 June 2026.
- Which products and versions are affected?
- Morse Micro HaLowLink 2 prior to 2.11.13.
- Is there a fix for CVE-2026-7762?
- 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-7762 attacked?
- It is attacked from the adjacent network, in device firmware.
- Am I affected by CVE-2026-7762?
- 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
A heap-based buffer overflow exists in the dot11ah.ko HaLow Wi-Fi kernel driver within the morse_dot11ah_find_s1g_caps_for_bssid() function. The vulnerability is caused by the driver using the Information Element (IE) length field from a received frame directly as the size argument for a memcpy operation without validating it against the 15-byte destination buffer. An unauthenticated attacker within radio range can transmit a crafted 802.11ah beacon or probe response frame containing a malformed S1G Capabilities IE (ID 0xD9) to overflow the heap with up to 240 bytes of controlled data. This can lead to a Denial of Service (kernel panic) or Remote Code Execution (RCE). The issue is fixed in version 2.11.13.
Affected products
- Morse Micro HaLowLink 2 prior to 2.11.13
Timeline
- 2026-06-05: disclosed: NVD publication date
- 2026-06-05: advisory: Morse Micro advisory MM-SA-2026-002 published