CVE-2026-72330

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-15. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

net/tls: Consume empty data records in tls_sw_read_sock()

A peer may send a zero-length TLS application_data record; TLS 1.3 explicitly permits these as a traffic-analysis countermeasure (RFC 8446, Section 5.1). After decryption such a record has full_len ==

  • tls_sw_read_sock() hands it to the read_actor, which has no
payload to consume and returns zero. The loop treats a zero return as backpressure (used <= 0), requeues the skb at the head of rx_list, and stops. rx_list is serviced head-first on the next call, so the empty record is dequeued, fails the same way, and is requeued again; every later record on the connection is blocked behind it.

tls_sw_recvmsg() does not stall on this: a zero-length data record copies nothing and falls through to consume_skb(). Mirror that in the read_sock() path by recognizing an empty data record before the actor runs, consuming it, and continuing.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
39(Track)
EG Risk 39/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
48%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 17, 2026

Advisory Details (5)

Auto-updated Aug 17, 2026
No patch confirmed yet.
generic

net/tls: Consume empty data records in tls_sw_read_sock() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ebc295ce343600c2d60c1e1e0c5d192080217457
generic

net/tls: Consume empty data records in tls_sw_read_sock() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e8a4c9fc437b16aef38f86ce3275677e36924259
generic

net/tls: Consume empty data records in tls_sw_read_sock() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c6b440cf766a557b08d25f1b571b3d57d039686e
generic

net/tls: Consume empty data records in tls_sw_read_sock() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3be28e2c9cd0230cb51fd4967df095273afd3848
generic

net/tls: Consume empty data records in tls_sw_read_sock() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0867b0f2513ebc1c475af9898c97f4772a68d964

Vendor Advisories for CVE-2026-72330(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 32× in last 7d / 32× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-21 05:51 UTCEG score recompute
  2. 2026-08-21 05:51 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 18:03 UTCGHSA enrichment
  5. 2026-08-20 06:15 UTCGHSA enrichment
  6. 2026-08-19 18:24 UTCEG score recompute
  7. 2026-08-19 18:24 UTCGHSA enrichment
  8. 2026-08-19 17:04 UTCEPSS rescore
  9. 2026-08-19 06:26 UTCGHSA enrichment
  10. 2026-08-18 18:38 UTCEG score recompute
  11. 2026-08-18 18:38 UTCGHSA enrichment
  12. 2026-08-18 13:49 UTCEPSS rescore
  13. 2026-08-18 13:49 UTCEPSS rescore
  14. 2026-08-18 06:49 UTCGHSA enrichment
  15. 2026-08-17 18:59 UTCEG score recompute
  16. 2026-08-17 18:59 UTCGHSA enrichment
  17. 2026-08-17 13:47 UTCEPSS rescore
  18. 2026-08-17 06:30 UTCEG score recompute
  19. 2026-08-17 06:30 UTCGHSA enrichment
  20. 2026-08-17 05:58 UTCEG score recompute▲ 7.50
  21. 2026-08-17 05:58 UTCGHSA enrichment
  22. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  23. 2026-08-17 05:30 UTCEG score recompute
  24. 2026-08-17 05:30 UTCGHSA enrichment
  25. 2026-08-17 05:25 UTCMITRE cvelistV5
Show 7 more
  1. 2026-08-16 14:56 UTCEPSS rescore
  2. 2026-08-16 14:56 UTCEPSS rescore
  3. 2026-08-16 02:15 UTCEPSS rescore
  4. 2026-08-15 06:36 UTCGHSA enrichment
  5. 2026-08-15 06:23 UTCNVD update
  6. 2026-08-15 06:07 UTCEG score recompute
  7. 2026-08-15 06:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-72330?
CVE-2026-72330 is a high vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: net/tls: Consume empty data records in tlsswread_sock() A peer may send a zero-length TLS application_data record; TLS 1.3 explicitly permits these as a traffic-analysis countermeasure (RFC 8446, Section 5.1). After decryption such…
When was CVE-2026-72330 disclosed?
CVE-2026-72330 was first published in the National Vulnerability Database on August 15, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-72330 actively exploited?
CVE-2026-72330 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 52.5% of all scored CVEs.
What is the CVSS score of CVE-2026-72330?
CVE-2026-72330 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-72330?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72330, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-72330

Explore →

Is Your Infrastructure Affected by CVE-2026-72330?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs