CVE-2026-72242

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:

selinux: avoid sk_socket dereference in selinux_sctp_bind_connect()

selinux_sctp_bind_connect() dereferences sk->sk_socket to pass a struct socket * to selinux_socket_bind() and selinux_socket_connect_helper(). However, when the hook is invoked from the ASCONF softirq path (sctp_process_asconf), there is no file reference guaranteeing that sk->sk_socket is non-NULL. The setsockopt callers (bindx, connectx, set_primary, sendmsg connect) hold a file reference and are not affected.

Both selinux_socket_bind() and selinux_socket_connect_helper() immediately resolve sock->sk, never using the struct socket * for anything else. Refactor the inner logic into helpers that take a struct sock * directly so that selinux_sctp_bind_connect() never needs to touch sk->sk_socket at all.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
38(Track)
EG Risk 38/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
46%
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

selinux: avoid sk_socket dereference in selinux_sctp_bind_connect() - kernel/git/stable/linux.git - Linux kernel stable tree

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

selinux: avoid sk_socket dereference in selinux_sctp_bind_connect() - kernel/git/stable/linux.git - Linux kernel stable tree

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

selinux: avoid sk_socket dereference in selinux_sctp_bind_connect() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5d4d93f9bfbc997ffbb03cd6107e8f6979dbb9b4
generic

selinux: avoid sk_socket dereference in selinux_sctp_bind_connect() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/56acfeb10019e200ab6787d01f8d7cbe0f01526f
generic

selinux: avoid sk_socket dereference in selinux_sctp_bind_connect() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/37d642b37ccdc31e1947c2ebc8dc38f03d4a0ceb

Vendor Advisories for CVE-2026-72242(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 31× in last 7d / 31× 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 01:48 UTCEG score recompute
  2. 2026-08-21 01:48 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 12:47 UTCGHSA enrichment
  5. 2026-08-19 23:42 UTCEG score recompute
  6. 2026-08-19 23:42 UTCGHSA enrichment
  7. 2026-08-19 17:04 UTCEPSS rescore
  8. 2026-08-19 10:40 UTCGHSA enrichment
  9. 2026-08-18 21:37 UTCEG score recompute
  10. 2026-08-18 21:37 UTCGHSA enrichment
  11. 2026-08-18 13:49 UTCEPSS rescore
  12. 2026-08-18 13:49 UTCEPSS rescore
  13. 2026-08-18 08:22 UTCGHSA enrichment
  14. 2026-08-17 19:22 UTCEG score recompute
  15. 2026-08-17 19:21 UTCGHSA enrichment
  16. 2026-08-17 13:47 UTCEPSS rescore
  17. 2026-08-17 06:20 UTCEG score recompute
  18. 2026-08-17 06:20 UTCGHSA enrichment
  19. 2026-08-17 05:59 UTCEG score recompute 7.50
  20. 2026-08-17 05:59 UTCGHSA enrichment
  21. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  22. 2026-08-17 05:31 UTCEG score recompute
  23. 2026-08-17 05:31 UTCGHSA enrichment
  24. 2026-08-17 05:25 UTCMITRE cvelistV5
  25. 2026-08-16 14:56 UTCEPSS rescore
Show 6 more
  1. 2026-08-16 14:56 UTCEPSS rescore
  2. 2026-08-16 02:15 UTCEPSS rescore
  3. 2026-08-15 06:39 UTCGHSA enrichment
  4. 2026-08-15 06:23 UTCNVD update
  5. 2026-08-15 06:09 UTCEG score recompute
  6. 2026-08-15 06:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-72242?
CVE-2026-72242 is a high vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: selinux: avoid sksocket dereference in selinuxsctpbindconnect() selinuxsctpbindconnect() dereferences sk->sksocket to pass a struct socket * to selinuxsocketbind() and selinuxsocketconnect_helper(). However, when the hook is…
When was CVE-2026-72242 disclosed?
CVE-2026-72242 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-72242 actively exploited?
CVE-2026-72242 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 54.1% of all scored CVEs.
What is the CVSS score of CVE-2026-72242?
CVE-2026-72242 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-72242?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72242, 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-72242

Explore →

Is Your Infrastructure Affected by CVE-2026-72242?

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