CVE-2026-74268

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH confidence

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

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

tcp: clear sock_ops cb flags before force-closing a child socket

A child socket inherits the listener's bpf_sock_ops_cb_flags via sk_clone_lock(). If its setup fails in tcp_v4_syn_recv_sock() / tcp_v6_syn_recv_sock(), the child is freed through put_and_exit, where inet_csk_prepare_forced_close() drops the socket lock and tcp_done() runs without it.

If BPF_SOCK_OPS_STATE_CB_FLAG was inherited, tcp_done() -> tcp_set_state() calls tcp_call_bpf(), which expects the lock and trips sock_owned_by_me():

WARNING: include/net/sock.h:1799 at tcp_set_state+0x433/0x550 RIP: 0010:tcp_set_state+0x433/0x550 include/net/sock.h:1799 Call Trace: tcp_done+0xba/0x250 net/ipv4/tcp.c:5095 tcp_v4_syn_recv_sock+0x850/0xa50 net/ipv4/tcp_ipv4.c:1787 tcp_check_req+0xf30/0x1360 net/ipv4/tcp_minisocks.c:926 tcp_v4_rcv+0x1047/0x1b50 net/ipv4/tcp_ipv4.c:2164

The child is freed before it is ever established, so it should run no sock_ops callback. Clear its cb flags in inet_csk_prepare_for_destroy_sock(), the common point for the IPv4, IPv6 and chtls forced-close paths and for the MPTCP ->syn_recv_sock() failure path (dispose_child), which reaches tcp_done() on a child that was never established too.

CVSS v3
9.8
EG Score
9.8(high)
EG Risk
49(Track)
EG Risk 49/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
Severity98% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
46%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 17, 2026

Advisory Details (3)

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

tcp: clear sock_ops cb flags before force-closing a child socket - kernel/git/stable/linux.git - Linux kernel stable tree

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

tcp: clear sock_ops cb flags before force-closing a child socket - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/990348e5bb457697c2f1f7f7b65154a3334d9d2b
generic

tcp: clear sock_ops cb flags before force-closing a child socket - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8874dafc9099bc49c2e5ebba030f85d276421f92

Vendor Advisories for CVE-2026-74268(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 47× in last 7d / 47× 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 09:02 UTCGHSA enrichment
  2. 2026-08-21 04:48 UTCGHSA enrichment
  3. 2026-08-21 00:33 UTCEG score recompute
  4. 2026-08-21 00:33 UTCGHSA enrichment
  5. 2026-08-20 22:56 UTCEPSS rescore
  6. 2026-08-20 20:20 UTCGHSA enrichment
  7. 2026-08-20 16:06 UTCGHSA enrichment
  8. 2026-08-20 11:51 UTCGHSA enrichment
  9. 2026-08-20 07:35 UTCGHSA enrichment
  10. 2026-08-20 03:21 UTCGHSA enrichment
  11. 2026-08-19 23:06 UTCGHSA enrichment
  12. 2026-08-19 18:53 UTCEG score recompute
  13. 2026-08-19 18:53 UTCGHSA enrichment
  14. 2026-08-19 17:04 UTCEPSS rescore
  15. 2026-08-19 14:38 UTCGHSA enrichment
  16. 2026-08-19 10:24 UTCGHSA enrichment
  17. 2026-08-19 06:08 UTCGHSA enrichment
  18. 2026-08-19 01:51 UTCGHSA enrichment
  19. 2026-08-18 21:37 UTCGHSA enrichment
  20. 2026-08-18 17:00 UTCEG score recompute
  21. 2026-08-18 17:00 UTCGHSA enrichment
  22. 2026-08-18 13:49 UTCEPSS rescore
  23. 2026-08-18 13:49 UTCEPSS rescore
  24. 2026-08-18 12:07 UTCGHSA enrichment
  25. 2026-08-18 07:49 UTCGHSA enrichment
Show 22 more
  1. 2026-08-18 03:36 UTCGHSA enrichment
  2. 2026-08-17 23:20 UTCGHSA enrichment
  3. 2026-08-17 19:06 UTCGHSA enrichment
  4. 2026-08-17 14:50 UTCEG score recompute
  5. 2026-08-17 14:50 UTCGHSA enrichment
  6. 2026-08-17 13:47 UTCEPSS rescore
  7. 2026-08-17 10:36 UTCEG score recompute
  8. 2026-08-17 10:36 UTCGHSA enrichment
  9. 2026-08-17 06:23 UTCEG score recompute
  10. 2026-08-17 06:23 UTCGHSA enrichment
  11. 2026-08-17 05:56 UTCEG score recompute▲ 9.80
  12. 2026-08-17 05:56 UTCGHSA enrichment
  13. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  14. 2026-08-17 05:27 UTCEG score recompute
  15. 2026-08-17 05:27 UTCGHSA enrichment
  16. 2026-08-17 05:24 UTCMITRE cvelistV5
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-16 02:15 UTCEPSS rescore
  20. 2026-08-15 06:23 UTCNVD update
  21. 2026-08-15 06:17 UTCEG score recompute
  22. 2026-08-15 06:12 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-74268?
CVE-2026-74268 is a critical vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: tcp: clear sock_ops cb flags before force-closing a child socket A child socket inherits the listener's bpfsockopscbflags via skclonelock(). If its setup fails in tcpv4synrecvsock() / tcpv6synrecvsock(), the child is freed through…
When was CVE-2026-74268 disclosed?
CVE-2026-74268 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-74268 actively exploited?
CVE-2026-74268 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 53.6% of all scored CVEs.
What is the CVSS score of CVE-2026-74268?
CVE-2026-74268 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-74268?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74268, 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-74268

Explore →

Is Your Infrastructure Affected by CVE-2026-74268?

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

Start Free Scan →Browse All CVEs