CVE-2026-68162
Last modified
CVE-2026-68162 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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(). EPSS estimates a 0.16% chance of exploitation in the next 30 days.
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.
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 10c869a52f266e40f548cc3c565d14930a5edafc, < 19573dcddb8819fd68d6cd1f916c1c99c3fa4ff4; >= dc583e7e5f8515ca489c0df28e4362a70eade382, < ceb7190b5c873d4a1267a1600c5aa52c600e929f; >= bd2a2939423566c654545fa3e96a656662a0af9e, < fd66854a22661929245f3d2b244c432bc8b1a150; >= 1b67030d39f2b00f94ac1f0af11ba6657589e4d3, < 158f3cc332dc53f43ec20060233d7c3cecd6d912; >= 7ec30c54f339c640aa7e49d7e9f7bbed6bd42bf6, < 66700c0719675e0e118ae83b2d7168dacd69dd3d; >= c184bc621e3cef03ac9ba81a50dda2dae6a21d36, < 626bda8cfe43dff19a9833ff6ba055a817b5455c; >= 15649fd5415eda664ef35780c2013adeb5d9c695, < be6aae9d1b91c603adb35872d37d40e83daf8758; >= 15649fd5415eda664ef35780c2013adeb5d9c695, < a50e73488e0bbdd262b3be3c9a1d8dd078382381; >= 15649fd5415eda664ef35780c2013adeb5d9c695, < f8d5e7846025f4ab15a461235f8ebae9094a361a; >= 5.4.290, < 5.4.292; >= 5.10.234, < 5.10.266; >= 5.15.177, < 5.15.217; >= 6.1.125, < 6.1.184; >= 6.6.72, < 6.6.151; >= 6.12.10, < 6.12.101 |
| Linux | Linux | 6.13 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-68162?
How severe is CVE-2026-68162?
How do I fix CVE-2026-68162?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-68157In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-68158In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-68159In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-6816An access bypass vulnerability in Drupal TFA Basic Plugins a…3.8
- CVE-2026-68160In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-68161In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-68163In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-68164In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68165In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68166In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68167In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68168In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-68162?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
