CVE-2026-68162

HIGHPre-NVD 7.87.8
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 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:

sctp: avoid auth_enable sysctl UAF during netns teardown

proc_sctp_do_auth() updates the SCTP control socket after changing net.sctp.auth_enable. The handler gets the per-net SCTP state from ctl->data, so an already opened sysctl file can still target a network namespace while that namespace is being torn down.

SCTP previously registered its per-net sysctls from sctp_defaults_init(), while the control socket is created later from sctp_ctrlsock_init(). This exposed a window during initialization where auth_enable was writable before net->sctp.ctl_sock existed, and a teardown window where auth_enable stayed writable after inet_ctl_sock_destroy() had released the control socket.

Move the per-net SCTP sysctl registration into sctp_ctrlsock_init() after sctp_ctl_sock_init() succeeds, and unregister the sysctl table before destroying the control socket in sctp_ctrlsock_exit(). If sysctl registration fails after the control socket was created, destroy the control socket in the same init path.

Make sctp_sysctl_net_unregister() tolerate a missing header and clear the saved pointer so init-error and exit paths can safely share the unregister helper.

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
6%
KEV
Not listed

Published

August 10, 2026

Last Modified

August 17, 2026

Advisory Details (6)

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

sctp: avoid auth_enable sysctl UAF during netns teardown - kernel/git/stable/linux.git - Linux kernel stable tree

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

sctp: avoid auth_enable sysctl UAF during netns teardown - kernel/git/stable/linux.git - Linux kernel stable tree

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

sctp: avoid auth_enable sysctl UAF during netns teardown - kernel/git/stable/linux.git - Linux kernel stable tree

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

sctp: avoid auth_enable sysctl UAF during netns teardown - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/66700c0719675e0e118ae83b2d7168dacd69dd3d
generic

sctp: avoid auth_enable sysctl UAF during netns teardown - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/626bda8cfe43dff19a9833ff6ba055a817b5455c
generic

Revert "sctp: sysctl: auth_enable: avoid using current->nsproxy" - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/19573dcddb8819fd68d6cd1f916c1c99c3fa4ff4

Vendor Advisories for CVE-2026-68162(2)

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 / 44× 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 02:56 UTCEG score recompute
  2. 2026-08-21 02:56 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 15:25 UTCGHSA enrichment
  5. 2026-08-20 03:53 UTCEG score recompute
  6. 2026-08-20 03:53 UTCGHSA enrichment
  7. 2026-08-19 17:04 UTCEPSS rescore
  8. 2026-08-19 16:23 UTCGHSA enrichment
  9. 2026-08-19 04:55 UTCGHSA enrichment
  10. 2026-08-18 17:25 UTCEG score recompute
  11. 2026-08-18 17:25 UTCGHSA enrichment
  12. 2026-08-18 13:48 UTCEPSS rescore
  13. 2026-08-18 04:40 UTCGHSA enrichment
  14. 2026-08-17 17:11 UTCEG score recompute
  15. 2026-08-17 17:11 UTCGHSA enrichment
  16. 2026-08-17 13:47 UTCEPSS rescore
  17. 2026-08-17 05:40 UTCEG score recompute
  18. 2026-08-17 05:40 UTCGHSA enrichment
  19. 2026-08-17 05:10 UTCEG score recompute
  20. 2026-08-17 05:10 UTCGHSA enrichment
  21. 2026-08-16 20:25 UTCEG score recompute
  22. 2026-08-16 20:25 UTCGHSA enrichment
  23. 2026-08-16 14:56 UTCEPSS rescore
  24. 2026-08-16 08:55 UTCEG score recompute
  25. 2026-08-16 08:55 UTCGHSA enrichment
Show 19 more
  1. 2026-08-15 21:26 UTCGHSA enrichment
  2. 2026-08-15 09:57 UTCEG score recompute
  3. 2026-08-15 09:57 UTCGHSA enrichment
  4. 2026-08-15 01:30 UTCEPSS rescore
  5. 2026-08-14 22:28 UTCGHSA enrichment
  6. 2026-08-14 10:59 UTCEG score recompute
  7. 2026-08-14 10:59 UTCGHSA enrichment
  8. 2026-08-13 23:30 UTCEG score recompute
  9. 2026-08-13 23:30 UTCGHSA enrichment
  10. 2026-08-13 22:45 UTCEG score recompute 7.80
  11. 2026-08-13 22:45 UTCGHSA enrichment
  12. 2026-08-13 22:44 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  13. 2026-08-13 22:00 UTCEPSS rescore
  14. 2026-08-13 17:16 UTCEG score recompute
  15. 2026-08-13 17:16 UTCGHSA enrichment
  16. 2026-08-12 13:51 UTCEPSS rescore
  17. 2026-08-10 13:24 UTCNVD update
  18. 2026-08-10 12:20 UTCEG score recompute
  19. 2026-08-10 12:17 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-68162?
CVE-2026-68162 is a high vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: sctp: avoid auth_enable sysctl UAF during netns teardown procsctpdo_auth() updates the SCTP control socket after changing net.sctp.auth_enable. The handler gets the per-net SCTP state from ctl->data, so an already opened sysctl…
When was CVE-2026-68162 disclosed?
CVE-2026-68162 was first published in the National Vulnerability Database on August 10, 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-68162 actively exploited?
CVE-2026-68162 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 93.9% of all scored CVEs.
What is the CVSS score of CVE-2026-68162?
CVE-2026-68162 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-68162?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68162, 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-68162

Explore →

Is Your Infrastructure Affected by CVE-2026-68162?

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