Goat Feed · KEV

    CISA KEV: Linux Kernel CVE-2025-39682 (CVSS 3.1 9.8 CRITICAL) - Kernel Improper Check for Unusual or Exceptional Conditions Vulnerability

    In the Linux kernel, the following vulnerability has been resolved: tls: fix handling of zero-length records on the rx_list Each recvmsg() call must process either only contiguous DATA records (any number of them) one non-DATA record If the next record has different type than what has already been processed we break out of the main processing loop. If the record has already been decrypted (which may be the case for TLS 1.3 where we don't know type until decryption) we queue the pending record to the rx_list. Next recvmsg() will pick it up from there. Queuing the skb to rx_list after zero-copy decrypt is not possible, since in that case we decrypted directly to the user space buffer, and we don't have an skb to queue (darg.skb points to the ciphertext skb for access to metadata like length). Only data records are allowed zero-copy, and we break the processing loop after each non-data record. So we should never zero-copy and then find out that the record type has changed. The corner case we missed is when the initial record comes from rx_list, and it's zero length.

    Back to the daily feed
    KEV
    critical

    Blue Goat Risk Score

    Blue Goat Cyber MedTech rubric v1.0 · methodology

    8.0
    of 10
    high
    CVSS technical
    40% · +3.9

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

    Patient safety
    35% · +1.8

    Delay of care

    Exploit maturity
    15% · +1.5

    On CISA KEV (in-the-wild)

    MedTech exposure
    10% · +0.8

    8/10 network-reachable signals

    How we got to 8.0

    1. 1
      CVSS technical severity (40%)

      Industry-standard exploitability + impact score. We prefer CVSS 4.0 and fall back to 3.1 per the FDA's Feb 2026 premarket cybersecurity guidance. Missing CVSS scores get a neutral 4.0 so unknown vulns are not over- or under-rated.

      3.1 base 9.8 × 40% = +3.92
    2. 2
      Patient safety impact (35%)

      What happens to a patient if this vuln is exploited on a connected device. Auto-inferred from headline, dek, tags, and device class against a curated MedTech keyword library (pacemaker, infusion pump, EHR, PACS, etc.).

      Delay of care → 5 × 35% = +1.75
    3. 3
      Exploit maturity (15%)

      Is anyone actually using this in attacks? KEV listing > weaponized exploit > public PoC > none. KEV alone forces tier=critical regardless of CVSS.

      On CISA KEV (in-the-wild) → 10 × 15% = +1.50
    4. 4
      MedTech exposure (10%)

      How likely this affects clinical operations: presence in our MedTech feed (+4 baseline), network-reachable signals (+3), known device-class tags (+2), identified MedTech vendor (+1).

      Exposure 8/10 × 10% = +0.80

    Tier cutoffs: Critical ≥ 8.5 · High 7.0–8.4 · Notable 4.0–6.9 · Info < 4.0. Full methodology, weights, and changelog at /goatfeed/risk-rubric.

    Need help acting on this?

    Talk to Blue Goat Cyber

    Penetration testing, SBOM, threat modeling, and 524B submission support for MedTech.