Skip to main content
VulnerabilityPublished

CVE-2026-7762: Morse Micro HaLowLink 2 · Heap-based Buffer Overflow

Affects Morse Micro HaLowLink 2Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical : upgrade to 2.11.13 as a priority.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.11.13
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade Morse Micro HaLowLink 2 to 2.11.13.

Affected software

ProductAffectedFixed in
Morse MicroHaLowLink 2Affected
  • <2.11.13
Fixed in
  • 2.11.13

AI-suggested

If you cannot patch yet, limiting exposure to untrusted 802.11ah networks or disabling scanning for 802.11ah networks may reduce risk, but these are not confirmed mitigations from the vendor.

Description

CVE-2026-7762 is a critical heap-based buffer overflow vulnerability in the Morse Micro HaLowLink 2 dot11ah.ko kernel driver affecting versions prior to 2.11.13. An unauthenticated attacker within radio range can exploit this by sending a crafted 802.11ah beacon or probe response frame with a malformed S1G Capabilities Information Element, causing a kernel panic or potentially remote code execution. The vulnerability arises because the driver copies up to 255 bytes into a 15-byte buffer without proper length validation. Exploitation requires no authentication or user interaction and can occur during normal scanning.

References

Community reviews

Loading reviews…