CVE-2026-68162

sctp: avoid auth_enable sysctl UAF during netns teardown

HIGH
7.8
CVSS Score
Published: August 10, 2026 at 11:59 AM UTC
Updated: October 19, 2026 at 09:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

10c869a52f266e40f548cc3c565d14930a5edafc15649fd5415eda664ef35780c2013adeb5d9c6951b67030d39f2b00f94ac1f0af11ba6657589e4d35.10.2345.15.1775.4.2906.1.1256.12.106.136.6.727ec30c54f339c640aa7e49d7e9f7bbed6bd42bf6bd2a2939423566c654545fa3e96a656662a0af9ec184bc621e3cef03ac9ba81a50dda2dae6a21d36dc583e7e5f8515ca489c0df28e4362a70eade382
Vendor states this is fixed in 158f3cc332dc53f43ec20060233d7c3cecd6d912 (fixed)
Vendor states this is fixed in 19573dcddb8819fd68d6cd1f916c1c99c3fa4ff4 (fixed)
Vendor states this is fixed in 626bda8cfe43dff19a9833ff6ba055a817b5455c (fixed)
Vendor states this is fixed in 66700c0719675e0e118ae83b2d7168dacd69dd3d (fixed)
Vendor states this is fixed in a50e73488e0bbdd262b3be3c9a1d8dd078382381 (fixed)
Vendor states this is fixed in be6aae9d1b91c603adb35872d37d40e83daf8758 (fixed)
Vendor states this is fixed in ceb7190b5c873d4a1267a1600c5aa52c600e929f (fixed)
Vendor states this is fixed in f8d5e7846025f4ab15a461235f8ebae9094a361a (fixed)
Vendor states this is fixed in fd66854a22661929245f3d2b244c432bc8b1a150 (fixed)
Vendor states this is fixed in 5.10.266 (unaffected)
Vendor states this is fixed in 5.15.217 (unaffected)
Vendor states this is fixed in 5.4.292 (unaffected)
Vendor states this is fixed in 6.1.184 (unaffected)
Vendor states this is fixed in 6.12.101 (unaffected)
Vendor states this is fixed in 6.13 (unaffected)
Vendor states this is fixed in 6.18.42 (unaffected)
Vendor states this is fixed in 6.6.151 (unaffected)
Vendor states this is fixed in 7.1.6 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusRECEIVED
CWE
CWE-416

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card