CVE-2026-74610

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: 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:

tls: don't leave a full plaintext sk_msg ring unpushed

When the copy path in tls_sw_sendmsg_locked() adds the fragment that fills the plaintext sk_msg ring, it does not set full_record, so the record is left full and unpushed. A later splice() then adds to an already full ring: sk_msg_page_add() has no fullness check of its own, so sg.end wraps onto sg.start and the ring appears empty. Fragments added after that overwrite live entries, and sg.size no longer matches what is reachable between sg.start and sg.end, so pushing the record runs the scatterwalk off the end of the scatterlist.

An unprivileged user can trigger this on a loopback TCP socket with the "tls" ULP attached:

BUG: kernel NULL pointer dereference, address: 0000000000000008 RIP: 0010:memcpy_from_scatterwalk+0x32/0xc0 Call Trace: skcipher_walk_next+0x1d1/0x2c0 gcm_encrypt_aesni_avx+0x1e9/0x220 bpf_exec_tx_verdict+0x3bb/0x860 tls_sw_sendmsg+0xa1a/0xca0 __sys_sendto+0x1da/0x1f0

Set full_record in the copy path when the ring becomes full, and push a record that is already full on entry to the sendmsg loop.

CVSS v3
7.8
EG Score
7.8(high)
EG Risk
40(Track)
EG Risk 40/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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

August 22, 2026

Last Modified

August 25, 2026

Advisory Details (5)

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

tls: don't leave a full plaintext sk_msg ring unpushed - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7bca91d63341274e857f4aeaad54d229405e93dc
generic

tls: don't leave a full plaintext sk_msg ring unpushed - kernel/git/stable/linux.git - Linux kernel stable tree

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

tls: don't leave a full plaintext sk_msg ring unpushed - kernel/git/stable/linux.git - Linux kernel stable tree

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

tls: don't leave a full plaintext sk_msg ring unpushed - kernel/git/stable/linux.git - Linux kernel stable tree

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

tls: don't leave a full plaintext sk_msg ring unpushed - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/aa8b14647721b5a4958712b35cf43e3125d47753

Vendor Advisories for CVE-2026-74610(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 25× in last 7d / 28× 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-30 04:06 UTCEG score recompute
  2. 2026-08-30 04:06 UTCGHSA enrichment
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-29 15:02 UTCGHSA enrichment
  5. 2026-08-29 01:59 UTCEG score recompute
  6. 2026-08-29 01:59 UTCGHSA enrichment
  7. 2026-08-28 21:42 UTCEPSS rescore
  8. 2026-08-28 12:54 UTCGHSA enrichment
  9. 2026-08-27 23:45 UTCEG score recompute
  10. 2026-08-27 23:45 UTCGHSA enrichment
  11. 2026-08-27 14:25 UTCEPSS rescore
  12. 2026-08-27 10:43 UTCGHSA enrichment
  13. 2026-08-26 21:40 UTCEG score recompute
  14. 2026-08-26 21:40 UTCGHSA enrichment
  15. 2026-08-26 14:47 UTCEPSS rescore
  16. 2026-08-26 08:37 UTCGHSA enrichment
  17. 2026-08-25 19:32 UTCEG score recompute
  18. 2026-08-25 19:32 UTCGHSA enrichment
  19. 2026-08-25 13:49 UTCEPSS rescore
  20. 2026-08-25 06:30 UTCEG score recompute
  21. 2026-08-25 06:30 UTCGHSA enrichment
  22. 2026-08-25 05:45 UTCEG score recompute▲ 7.80
  23. 2026-08-25 05:45 UTCGHSA enrichment
  24. 2026-08-25 05:45 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  25. 2026-08-24 14:18 UTCEPSS rescore
Show 3 more
  1. 2026-08-22 16:24 UTCNVD update
  2. 2026-08-22 15:42 UTCEG score recompute
  3. 2026-08-22 15:35 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-74610?
CVE-2026-74610 is a high vulnerability published on August 22, 2026. In the Linux kernel, the following vulnerability has been resolved: tls: don't leave a full plaintext sk_msg ring unpushed When the copy path in tlsswsendmsg_locked() adds the fragment that fills the plaintext skmsg ring, it does not set fullrecord, so the record is left full and unpushed. A later…
When was CVE-2026-74610 disclosed?
CVE-2026-74610 was first published in the National Vulnerability Database on August 22, 2026, with the most recent update on August 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-74610 actively exploited?
CVE-2026-74610 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.2% of all scored CVEs.
What is the CVSS score of CVE-2026-74610?
CVE-2026-74610 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-74610?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74610, 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-74610

Explore →

Is Your Infrastructure Affected by CVE-2026-74610?

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

Start Free Scan →Browse All CVEs