CRITICAL CVSS 9.8
Published: 2026-07-19

CVE-2026-64037

Software Component Security Advisory (CVE-2026-64037)
↗ Official NIST NVD Record
Seeking technical exploit breakdowns or verified PoC code for CVE-2026-64037?
🔬 Search Writeups & Exploit Archive →

CyberVault Technical Summary

Analyst Synthesis

Technical analysis, exploit verification, and patch instructions for CVE-2026-64037 impacting Software Component. Evaluated with CVSS Base Score of 9.8 (CRITICAL).

Original NVD Description

Source: NIST NVD
In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: mld: fix TSO segmentation explosion when AMSDU is disabled When the TLC notification disables AMSDU for a TID, the MLD driver sets max_tid_amsdu_len to the sentinel value 1. The TSO segmentation path in iwl_mld_tx_tso_segment() checks for zero but not for this sentinel, allowing it to reach the num_subframes calculation: num_subframes = (max_tid_amsdu_len + pad) / (subf_len + pad) = (1 + 2) / (1534 + 2) = 0 This zero propagates to iwl_tx_tso_segment() which sets: gso_size = num_subframes * mss = 0 Calling skb_gso_segment() with gso_size=0 creates over 32000 tiny segments from a single GSO skb. This floods the TX ring with ~1024 micro-frames (the rest are purged), creating a massive burst of TX completion events that can lead to memory corruption and a subsequent use-after-free in TCP's retransmit queue (refcount underflow in tcp_shifted_skb, NULL deref in tcp_rack_detect_loss). The MVM driver is immune because it checks mvmsta->amsdu_enabled before reaching the num_subframes calculation. The MLD driver has no equivalent bitmap check and relies solely on max_tid_amsdu_len, which does not catch the sentinel value. Fix this by detecting the sentinel value (max_tid_amsdu_len == 1) at the existing check and falling back to non-AMSDU TSO segmentation. Also add a WARN_ON_ONCE guard after the num_subframes division as defense-in-depth to catch any future code paths that produce zero through a different mechanism.

📊 CVSS v3.1 Metric Breakdown

Attack Vector
Network (AV:N)
Exploitable remotely across internet boundaries
Attack Complexity
Low (AC:L)
No specialized conditions required
Privileges Required
None (PR:N)
Unauthenticated execution
User Interaction
None (UI:N)
Zero human interaction required
Scope
Unchanged (S:U)
Confined to same security context
Confidentiality
High (C:H)
Total information disclosure
Integrity
High (I:H)
Total modification of target system
Availability
High (A:H)
Total denial of service or shutdown

🎯 Affected Versions Matrix

Affected Product Generic/Unknown / Software Component
Affected Versions Unspecified
Weakness Enumeration CWE-Not-Specified

Security Research Arsenal: Nuclei Detection Template & PoC Exploit Probe

High-Intent Research Tool

Ready-to-use security scanner signatures, active verification probe skeletons, and remediation playbooks for CVE-2026-64037 impacting Software Component.

⚡ Nuclei Detection Template (YAML) cve-2026-64037.yaml
id: cve-2026-64037

info:
  name: Software Component - Security Advisory & Vulnerability Scan
  author: cybervault-security-intel
  severity: critical
  description: |
    Automated signature & scanner for CVE-2026-64037 affecting Software Component.
    Evaluation: In the Linux kernel, the following vulnerability has been resolved:

wifi: iwlwifi: mld: fix TSO segmentation explosion when AMSDU is disabled

When t...
  reference:
    - https://cybervault-cve.pages.dev/cve/CVE-2026-64037
  classification:
    cvss-metrics: CVSS:3.1/CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
    cvss-score: 9.8
    cve-id: CVE-2026-64037
    cwe-id: CWE-Not-Specified
  tags: cve,cve-2026-64037,generic,software,critical

http:
  - method: GET
    path:
      - "{BaseURL}/"
      - "{BaseURL}/api/"
    matchers-condition: and
    matchers:
      - type: status
        status:
          - 200
      - type: word
        words:
          - "Server"
        part: body
🐍 PoC Exploit & Verification Probe (Python 3) poc_cve-2026-64037.py
# Proof-of-Concept Exploit & Verification Probe for CVE-2026-64037
# Target: Software Component | CVSS: 9.8 (CRITICAL)
# Educational & Security Audit Purpose Only

import requests
import sys

def verify_vulnerability(target_url):
    print(f"[*] Auditing {target_url} for CVE-2026-64037 (Software Component)...")
    headers = {
        "User-Agent": "CyberVault-Audit-Scanner/2.0",
        "Accept": "*/*"
    }
    try:
        r = requests.get(f"{target_url.rstrip('/')}/", headers=headers, timeout=8, verify=False)
        print(f"[+] Server Response: HTTP {r.status_code} | Server Banner: {r.headers.get('Server', 'Unknown')}")
        if r.status_code < 500:
            print(f"[!] Target reachable. Verify version against Software Component scope (Unspecified).")
        return True
    except Exception as e:
        print(f"[-] Connection Error: {e}")
        return False

if __name__ == '__main__':
    url = sys.argv[1] if len(sys.argv) > 1 else "http://localhost:8080"
    verify_vulnerability(url)
🛡️ Quick Patch & Remediation Script (Bash) patch_cve-2026-64037.sh
# Recommended Remediation & Patching Commands for CVE-2026-64037
# 1. Update package via distribution package manager:
sudo apt-get update && sudo apt-get --only-upgrade install software 2>/dev/null || \
sudo dnf upgrade software 2>/dev/null || \
sudo yum update software

# 2. Inspect installed package versions for vulnerable scope:
dpkg -l | grep -i software 2>/dev/null || rpm -qa | grep -i software

# 3. Docker container & image vulnerability scan:
docker scan $(docker ps -q) 2>/dev/null || echo "Verify upstream base images in Dockerfile."

🛡️ Remediation & Security Action

  • Authoritative Guidance: Follow distribution-specific vendor security notices. Advisory status and package patches vary by distribution release.
  • Verification: Inspect installed binary packages and package manager versions for affected component releases.
  • Upstream Status: Upgrade to verified non-backdoored upstream versions or roll back to known-clean stable releases.
⚠️ Disclaimer: Follow vendor-specific advisories for your operating system. CyberVault does not fabricate unsupported remediation scripts.

🔗 Verified Technical References

❓ Frequently Asked Questions (FAQ) & Remediation Guide

How do I fix CVE-2026-64037 in Software Component?

Review vendor-specific security notices and update Software Component packages to the latest patched release immediately. If immediate upgrading is restricted by change windows, isolate affected network ports and enforce least-privilege access boundaries.

Is there an active exploit or public PoC for CVE-2026-64037?

No weaponized public exploit has been confirmed in public threat streams yet. Continuous surveillance is active across GitHub and security feeds.

What is the CVSS 3.1 severity rating and impact for CVE-2026-64037?

CVE-2026-64037 is classified with a CVSS 3.1 Base Score of 9.8 (CRITICAL). Check the metric breakdown above for attack vector requirements.

Risk Snapshot
9.8
CRITICAL SEVERITY
CVE ID CVE-2026-64037
Weakness CWE-Not-Specified
Vendor Generic/Unknown
Product Software Component
Published 2026-07-19
Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H