NVD / CVE Program· CNA Linux

CVE-2026-68117: tipc: clear sock->sk on the failed-insert path in tipc_sk_create()

Noroxi assessment

Priority: Monitor (action score 39/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.52% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
According to CISA the attack is automatable: targets can be found by mass scanning.
Fixed version: Linux Linux 4.10, 4.15, 4.20; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.1-1.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 4.10, 4.15, 4.20; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.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: 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)

CriticalCVSS 9.8 · v3.1—No exploit Fix available

Published: Aug 10, 2026
Updated: Oct 19, 2026
EPSS: 0.5% · 44th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 39 / 40 · 9.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.5%

CISA SSVC decision

Exploitation: none
Automatable: yes
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · Linux: 9.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

Is your version affected? Check it

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 help

Affected 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
- 638fa20b618b2bbcf86da71231624cc82121a036, 7bc9e7f70bc57d8f02ffea2a42094281effb15ef, ef488669b2652bde5b6ee5a409a5b048a2a50db4, 4919d82f7041157a421ca9bf39a78551d5ad8a1b, 3b2957fc09fe1ac7f07f40dd50dd5f93e3f3a7a2, 5.19affected
- efa78f2ae363428525fb4981bb63c555ee79f3c7 and later · before efebc23e9b29e3e5a9e2127dd066929f7f0d315eaffected · git
- 833ecd0eae76eadf81d6d747bb5bc992d1151867 and later · before 8d6f26d48e61ef34f1921289401dbf36b10816afaffected · git
- 00aff3590fc0a73bddd3b743863c14e76fd35c0c and later · before 82f59aa27f33bd014a7d8739371ab5712d15e33baffected · git
- 00aff3590fc0a73bddd3b743863c14e76fd35c0c and later · before b07d87b31631edb6529e6cdcca790a7489d1250daffected · git
- 00aff3590fc0a73bddd3b743863c14e76fd35c0c and later · before dd29891ed840f6b8d020b759d0dc4a00b1d6e4eaaffected · git
- 00aff3590fc0a73bddd3b743863c14e76fd35c0c and later · before 5f5a41a48dbf9eda57b67ce23e548602cf7195a6affected · git
- 00aff3590fc0a73bddd3b743863c14e76fd35c0c and later · before f9596b1566616a8be0592dbceccb6344a7c6f6bbaffected · git
- 00aff3590fc0a73bddd3b743863c14e76fd35c0c and later · before ba0533fc163f905fe817cfabdf8ed4058da44800affected · git
- 5.10.132 and later · before 5.10.265affected · semver

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 records

Other highest-scoring records for the same primary product.

CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
40Plan
CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
40Plan
CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
40Plan

Published before and after this one in the same product

← EarlierCVE-2026-68115Aug 10, 2026 · drm/amdgpu/gfx10: replace BUG_ON() with WARN_ON()
0Monitor
← EarlierCVE-2026-68116Aug 10, 2026 · vxlan: mdb: Fix source list corruption on a failed replace
31Monitor
Later →CVE-2026-68118Aug 10, 2026 · tcp: challenge ACK for non-exact RST in SYN-RECEIVED
32Monitor

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	4.10	Vendor (CNA)
Linux Linux	4.15	Vendor (CNA)
Linux Linux	4.20	Vendor (CNA)
Linux Linux	5.10.265	Vendor (CNA)
Linux Linux	5.15.216	Vendor (CNA)
Linux Linux	5.19	Vendor (CNA)
Linux Linux	5.5	Vendor (CNA)
Linux Linux	5f5a41a48dbf9eda57b67ce23e548602cf7195a6	Vendor (CNA)
Linux Linux	82f59aa27f33bd014a7d8739371ab5712d15e33b	Vendor (CNA)
Linux Linux	8d6f26d48e61ef34f1921289401dbf36b10816af	Vendor (CNA)
Linux Linux	b07d87b31631edb6529e6cdcca790a7489d1250d	Vendor (CNA)
Linux Linux	ba0533fc163f905fe817cfabdf8ed4058da44800	Vendor (CNA)
Linux Linux	dd29891ed840f6b8d020b759d0dc4a00b1d6e4ea	Vendor (CNA)
Linux Linux	efebc23e9b29e3e5a9e2127dd066929f7f0d315e	Vendor (CNA)
Linux Linux	f9596b1566616a8be0592dbceccb6344a7c6f6bb	Vendor (CNA)
azl3 kernel 6.6.143.1-1 on Azure Linux 3.0	6.6.150.1-1 · CBL-Mariner Releases	Microsoft (MSRC)
almalinux:bpftool	4.18.0-553.162.1.el8_10 · AlmaLinux:8	Package registry (OSV)
almalinux:kernel	4.18.0-553.162.1.el8_10 · AlmaLinux:8	Package registry (OSV)
almalinux:kernel-rt	4.18.0-553.162.1.rt7.503.el8_10 · AlmaLinux:8	Package registry (OSV)
almalinux:kernel-rt-core	4.18.0-553.162.1.rt7.503.el8_10 · AlmaLinux:8	Package registry (OSV)
almalinux:kernel-rt-debug	4.18.0-553.162.1.rt7.503.el8_10 · AlmaLinux:8	Package registry (OSV)
almalinux:kernel-rt-debug-core	4.18.0-553.162.1.rt7.503.el8_10 · AlmaLinux:8	Package registry (OSV)
almalinux:kernel-rt-debug-devel	4.18.0-553.162.1.rt7.503.el8_10 · AlmaLinux:8	Package registry (OSV)
almalinux:kernel-rt-debug-modules	4.18.0-553.162.1.rt7.503.el8_10 · AlmaLinux:8	Package registry (OSV)
almalinux:kernel-rt-debug-modules-extra	4.18.0-553.162.1.rt7.503.el8_10 · AlmaLinux:8	Package registry (OSV)
almalinux:kernel-rt-devel	4.18.0-553.162.1.rt7.503.el8_10 · AlmaLinux:8	Package registry (OSV)
almalinux:kernel-rt-modules	4.18.0-553.162.1.rt7.503.el8_10 · AlmaLinux:8	Package registry (OSV)
almalinux:kernel-rt-modules-extra	4.18.0-553.162.1.rt7.503.el8_10 · AlmaLinux:8	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)

+14

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.

EPSS, last 120 days

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 researchers

Finders, 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-681270 days apartila: reload IPv6 header after pskb_may_pull in checksum adjust
39Monitor
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 update
39Monitor
CVE-2026-683810 days apartksmbd: pin conn during async oplock break notification
39Monitor
CVE-2026-684260 days apartxfrm: fix stale skb->prev after async crypto steals a GSO segment
39Monitor
CVE-2026-720835 days apartscsi: target: core: Fix iSCSI ISID use-after-free in REGISTER AND MOVE
39Monitor

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)

All national notices →

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
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: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/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 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&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— → noneOct 16, 2026, 5:07 PM UTC
Fix✗ → ✓Sep 28, 2026, 10:07 PM UTC

For records you follow, these changes also arrive as notifications. →

References

git.kernel.org/stable/c/5f5a41a48dbf9eda57b67ce23e548602cf7195a6

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records