Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources or documents need attention: 262/275 feeds/APIs · 469/469 docs · 9/9 advisories · checked 19:25 UTC Customize Public modeDiscuss ChangeIntel on Discord

tcp: fix use-after-free in do_tcp_getsockopt(TCP_CONGESTION)

Exact source revision recorded 28 Oct 2026 11:27:43 UTC. It does not establish the source's current position. Latest evidence.

cve-program · CVE-2026-99139

Published

In the Linux kernel, the following vulnerability has been resolved: tcp: fix use-after-free in do_tcp_getsockopt(TCP_CONGESTION) do_tcp_getsockopt() reads icsk->icsk_ca_ops->name without holding rcu_read_lock(). Since commit 0baf26b0fcd7 ("bpf: tcp: Support tcp_congestion_ops in bpf"), icsk_ca_ops can point to dynamically allocated BPF struct_ops memory that may be freed concurrently via setsockopt(TCP_CONGESTION), leading to a use-after-free. BUG: KASAN: slab-use-after-free in _copy_to_user+0x37/0x60 Read of size 16 at addr ffff888013505260 by task exploit/149 _copy_to_user+0x37/0x60 do_tcp_getsockopt+0x158a/0x2460 (net/ipv4/tcp.c:4585) tcp_getsockopt+0x91/0xf0 __sys_getsockopt+0xf7/0x170 Fix this by holding rcu_read_lock() around the ca_ops->name access, using READ_ONCE() to load icsk_ca_ops, and copying the name to a stack buffer before releasing the lock. Also annotate the relevant icsk_ca_ops stores with WRITE_ONCE() to fix the accompanying KCSAN data-race issue.

Source published
28 Oct 2026 10:34:50 UTC
Source modified
28 Oct 2026 10:34:50 UTC
Observed here
28 Oct 2026 11:27:43 UTC
Source terms
CVE Program Terms of Use

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: cve-program · CVE Program Terms of Use. Source text is retained; field grouping and change labels are provided by ChangeIntel.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 10 Nov 19:25 UTC · 262 of 275 readable · 261 fully read · documentation 469/469 current