dbcve.org
VulnerabilityAwaiting classification

CVE-2026-7763

CRITICAL · 9.8 CVSS v3.1 Published 2026-06-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A heap-based buffer overflow vulnerability in the morse.ko HaLow Wi-Fi kernel driver in Morse Micro HaLowLink 2 software versions prior to 2.11.13 allows an unauthenticated attacker within radio range to cause a Denial of Service (kernel panic) or potentially achieve Remote Code Execution via a crafted 802.11ah beacon frame containing a malformed Traffic Indication Map (TIM) Information Element. The function morse_page_slicing_process_tim_element() in page_slicing.c derives the TIM bitmap length directly from a received IE field without validating it against the fixed-size destination buffer before passing it to memset and memcpy operations, allowing up to 252 bytes of attacker-controlled data to be written beyond the buffer boundary. Because beacons are broadcast frames processed during passive scanning, no authentication, association, or user interaction is required.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Heap-based buffer overflow in morse.ko HaLow Wi-Fi kernel driver. The function morse_page_slicing_process_tim_element() in page_slicing.c derives the TIM bitmap length directly from a received 802.11ah beacon frame's TIM Information Element without validating it against a fixed-size destination buffer, allowing up to 252 bytes of attacker-controlled data to be written beyond the buffer boundary via memset/memcpy operations. Since beacons are broadcast frames processed during passive scanning, no authentication or association is required.

MitigationUpgrade to Morse Micro HaLowLink 2 version 2.11.13 or later which should include proper bounds validation for the TIM IE length. Until patched, consider disabling the HaLow Wi-Fi interface or implementing network access controls to limit radio range.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the morse.ko kernel module
    Check if the morse.ko kernel module file exists on the system or is currently loaded. Use commands like 'lsmod | grep morse' to see if loaded, or search for the .ko file in the kernel modules directory.
    Affected if The morse.ko module is present and loaded on the system.
  2. Identify the morse.ko driver version
    Retrieve the version information of the morse.ko module using 'modinfo morse.ko' or 'modinfo /path/to/morse.ko', which displays version metadata stored in the module.
    Affected if The driver version cannot be determined or is lower than 2.11.13.
  3. Confirm HaLow 802.11ah Wi-Fi usage
    Verify that the system is actively using or configured to use HaLow (802.11ah) Wi-Fi functionality, since the vulnerability only affects beacon processing in this specific wireless standard.
    Affected if The system uses HaLow (802.11ah) wireless interfaces and processes beacon frames.
  4. Compare installed version to fixed release
    Compare the retrieved driver version against the patched version 2.11.13. If the version string is lower or the module lacks version metadata, the system may be running a vulnerable release.
    Affected if The installed version is lower than 2.11.13 or version information is unavailable.

The system is affected if the morse.ko HaLow Wi-Fi driver is present, the system uses 802.11ah HaLow wireless, and the driver version is below 2.11.13.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Morse Micro HaLowLink 2 version 2.11.13 or later which should include proper bounds validation for the TIM IE length. Until patched, consider disabling the HaLow Wi-Fi interface or implementing network access controls to limit radio range.

Recommended fix High confidence

Morse Micro HaLowLink 2 version 2.11.13 or later

  1. Identify all devices running Morse Micro HaLowLink 2 software prior to version 2.11.13
  2. Upgrade the Morse Micro HaLowLink 2 software on affected devices to version 2.11.13 or later
  3. Verify the upgrade was successful by checking the software version
  4. Confirm the morse.ko driver has been updated to the patched version

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-7763 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-7763 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data