CVE-2026-68162: sctp: avoid auth_enable sysctl UAF during netns teardown
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 158f3cc332dc53f43ec20060233d7c3cecd6d912, 19573dcddb8819fd68d6cd1f916c1c99c3fa4ff4, 5.10.266; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 6.6.152.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 158f3cc332dc53f43ec20060233d7c3cecd6d912, 19573dcddb8819fd68d6cd1f916c1c99c3fa4ff4, 5.10.266; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 6.6.152.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 10, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 9th percentile
- CWE
- CWE-416
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.13affected
- 10c869a52f266e40f548cc3c565d14930a5edafc and later · before 19573dcddb8819fd68d6cd1f916c1c99c3fa4ff4affected · git
- dc583e7e5f8515ca489c0df28e4362a70eade382 and later · before ceb7190b5c873d4a1267a1600c5aa52c600e929faffected · git
- bd2a2939423566c654545fa3e96a656662a0af9e and later · before fd66854a22661929245f3d2b244c432bc8b1a150affected · git
- 1b67030d39f2b00f94ac1f0af11ba6657589e4d3 and later · before 158f3cc332dc53f43ec20060233d7c3cecd6d912affected · git
- 7ec30c54f339c640aa7e49d7e9f7bbed6bd42bf6 and later · before 66700c0719675e0e118ae83b2d7168dacd69dd3daffected · git
- c184bc621e3cef03ac9ba81a50dda2dae6a21d36 and later · before 626bda8cfe43dff19a9833ff6ba055a817b5455caffected · git
- 15649fd5415eda664ef35780c2013adeb5d9c695 and later · before be6aae9d1b91c603adb35872d37d40e83daf8758affected · git
- 15649fd5415eda664ef35780c2013adeb5d9c695 and later · before a50e73488e0bbdd262b3be3c9a1d8dd078382381affected · git
- 15649fd5415eda664ef35780c2013adeb5d9c695 and later · before f8d5e7846025f4ab15a461235f8ebae9094a361aaffected · git
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | kernel | before 6.12.0-211.67.1.el10_2 | 6.12.0-211.67.1.el10_2 |
| AlmaLinux:10 | kernel-64k | before 6.12.0-211.67.1.el10_2 | 6.12.0-211.67.1.el10_2 |
| AlmaLinux:10 | kernel-64k-core | before 6.12.0-211.67.1.el10_2 | 6.12.0-211.67.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug | before 6.12.0-211.67.1.el10_2 | 6.12.0-211.67.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-core | before 6.12.0-211.67.1.el10_2 | 6.12.0-211.67.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel | before 6.12.0-211.67.1.el10_2 | 6.12.0-211.67.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel-matched | before 6.12.0-211.67.1.el10_2 | 6.12.0-211.67.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules | before 6.12.0-211.67.1.el10_2 | 6.12.0-211.67.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-core | before 6.12.0-211.67.1.el10_2 | 6.12.0-211.67.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-extra | before 6.12.0-211.67.1.el10_2 | 6.12.0-211.67.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel | before 6.12.0-211.67.1.el10_2 | 6.12.0-211.67.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel-matched | before 6.12.0-211.67.1.el10_2 | 6.12.0-211.67.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules | before 6.12.0-211.67.1.el10_2 | 6.12.0-211.67.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-core | before 6.12.0-211.67.1.el10_2 | 6.12.0-211.67.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-extra | before 6.12.0-211.67.1.el10_2 | 6.12.0-211.67.1.el10_2 |
| AlmaLinux:10 | kernel-abi-stablelists | before 6.12.0-211.67.1.el10_2 | 6.12.0-211.67.1.el10_2 |
| AlmaLinux:10 | kernel-core | before 6.12.0-211.67.1.el10_2 | 6.12.0-211.67.1.el10_2 |
| AlmaLinux:10 | kernel-cross-headers | before 6.12.0-211.67.1.el10_2 | 6.12.0-211.67.1.el10_2 |
| AlmaLinux:10 | kernel-debug | before 6.12.0-211.67.1.el10_2 | 6.12.0-211.67.1.el10_2 |
| AlmaLinux:10 | kernel-debug-core | before 6.12.0-211.67.1.el10_2 | 6.12.0-211.67.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel | before 6.12.0-211.67.1.el10_2 | 6.12.0-211.67.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel-matched | before 6.12.0-211.67.1.el10_2 | 6.12.0-211.67.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules | before 6.12.0-211.67.1.el10_2 | 6.12.0-211.67.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules-core | before 6.12.0-211.67.1.el10_2 | 6.12.0-211.67.1.el10_2 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-68160Aug 10, 2026 · ceph: fix pre-auth out-of-bounds read on snaptrace in ceph_handle_caps()39Monitor
- ← EarlierCVE-2026-68161Aug 10, 2026 · sctp: close UDP tunnel sockets during netns teardown39Monitor
- Later →CVE-2026-68178Aug 10, 2026 · misc: nsm: pin the module while the device is open31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 158f3cc332dc53f43ec20060233d7c3cecd6d912 | Vendor (CNA) |
| Linux Linux | 19573dcddb8819fd68d6cd1f916c1c99c3fa4ff4 | Vendor (CNA) |
| Linux Linux | 5.10.266 | Vendor (CNA) |
| Linux Linux | 5.15.217 | Vendor (CNA) |
| Linux Linux | 5.4.292 | Vendor (CNA) |
| Linux Linux | 6.1.184 | Vendor (CNA) |
| Linux Linux | 6.12.101 | Vendor (CNA) |
| Linux Linux | 6.6.151 | Vendor (CNA) |
| Linux Linux | 626bda8cfe43dff19a9833ff6ba055a817b5455c | Vendor (CNA) |
| Linux Linux | 66700c0719675e0e118ae83b2d7168dacd69dd3d | Vendor (CNA) |
| Linux Linux | a50e73488e0bbdd262b3be3c9a1d8dd078382381 | Vendor (CNA) |
| Linux Linux | be6aae9d1b91c603adb35872d37d40e83daf8758 | Vendor (CNA) |
| Linux Linux | ceb7190b5c873d4a1267a1600c5aa52c600e929f | Vendor (CNA) |
| Linux Linux | f8d5e7846025f4ab15a461235f8ebae9094a361a | Vendor (CNA) |
| Linux Linux | fd66854a22661929245f3d2b244c432bc8b1a150 | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | 6.6.152.1-1 · Release Notes | Microsoft (MSRC) |
| almalinux:kernel | 6.12.0-211.67.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k | 6.12.0-211.67.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-core | 6.12.0-211.67.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 6.12.0-211.67.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 6.12.0-211.67.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 6.12.0-211.67.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 6.12.0-211.67.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 6.12.0-211.67.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 6.12.0-211.67.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 6.12.0-211.67.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 6.12.0-211.67.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-devel-matched | 6.12.0-211.67.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.101-1~deb12u1 · Debian:12 | Package registry (OSV) |
+22
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-681170 days aparttipc: clear sock->sk on the failed-insert path in tipc_sk_create()39Monitor
- CVE-2026-681270 days apartila: reload IPv6 header after pskb_may_pull in checksum adjust39Monitor
- CVE-2026-681440 days apartphonet: pep: fix use-after-free in pep_get_sb()39Monitor
- CVE-2026-681560 days apartlibceph: refresh auth->authorizer_buf{,_len} after authorizer update39Monitor
- CVE-2026-683810 days apartksmbd: pin conn during async oplock break notification39Monitor
- CVE-2026-684260 days apartxfrm: fix stale skb->prev after async crypto steals a GSO segment39Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0800 · Aug 11, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- git.kernel.org/stable/c/19573dcddb8819fd68d6cd1f916c1c99c3fa4ff4
- git.kernel.org/stable/c/626bda8cfe43dff19a9833ff6ba055a817b5455c
- git.kernel.org/stable/c/66700c0719675e0e118ae83b2d7168dacd69dd3d
- git.kernel.org/stable/c/a50e73488e0bbdd262b3be3c9a1d8dd078382381
- git.kernel.org/stable/c/be6aae9d1b91c603adb35872d37d40e83daf8758
- git.kernel.org/stable/c/ceb7190b5c873d4a1267a1600c5aa52c600e929f
- git.kernel.org/stable/c/f8d5e7846025f4ab15a461235f8ebae9094a361a
- git.kernel.org/stable/c/fd66854a22661929245f3d2b244c432bc8b1a150
Vendor advisories and official records. Exploit/PoC links are deliberately left out.