Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 33 days later

    Published

  3. · 2 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.17% · top 93% of all CVEs (16 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 0baf26b0fcd74bbfcef53c5d5e8bad2b99c8d0d2 – < a60e62705c17534d6b6539de7b3a40c259e6827f
    • affected 0baf26b0fcd74bbfcef53c5d5e8bad2b99c8d0d2 – < 4b0930d66dde0a1d1898f0edbbb5496c4dfa5f03
    • affected 0baf26b0fcd74bbfcef53c5d5e8bad2b99c8d0d2 – < 08dc5c62c09653d1c4ba67a009beb138486c2604
    • affected 0baf26b0fcd74bbfcef53c5d5e8bad2b99c8d0d2 – < c1804ef016392dd91267d2207ee43b1de34302ca
    • affected 0baf26b0fcd74bbfcef53c5d5e8bad2b99c8d0d2 – < a8e45471afa230c1431c26c8e99ec24377e3b514
    • affected 0baf26b0fcd74bbfcef53c5d5e8bad2b99c8d0d2 – < 5271b79b7ad68dcb222e893773f92bdabf7750f3
  • Linux · Linux

    • affected 5.6
    • unaffected < 5.6
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.161 – ≤ 6.6.*
    • unaffected 6.12.115 – ≤ 6.12.*
    • unaffected 6.18.59 – ≤ 6.18.*
    • unaffected 7.2.13 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-99139 badge
[![CVE-2026-99139](https://cveledger.app/badge/CVE-2026-99139.svg)](https://cveledger.app/cve/CVE-2026-99139)

Record last updated .