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-68284bpf, sockmap: Fix cork use-after-free in tcp_bpf_sendmsg()

Description

In the Linux kernel, the following vulnerability has been resolved: bpf, sockmap: Fix cork use-after-free in tcp_bpf_sendmsg() tcp_bpf_sendmsg() keeps msg_tx across sk_stream_wait_memory(), which drops and reacquires the socket lock. Its error path tries to decide whether msg_tx names the local temporary message by comparing it with the current value of psock->cork. This comparison is unsafe when two threads send on the same socket: Thread A Thread B msg_tx = psock->cork sk_msg_alloc() fails sk_stream_wait_memory() releases the socket lock acquires the socket lock completes the cork psock->cork = NULL frees the cork reacquires the socket lock msg_tx != psock->cork sk_msg_free(msg_tx) The stale cork is therefore mistaken for the local temporary message and freed again. KASAN reported: BUG: KASAN: slab-use-after-free in sk_msg_free+0x49/0x50 Read of size 4 at addr ffff88810c908800 by task poc/90 Call Trace: sk_msg_free+0x49/0x50 tcp_bpf_sendmsg+0x14f5/0x1cc0 __sys_sendto+0x32c/0x3a0 __x64_sys_sendto+0xdb/0x1b0 Allocated by task 89: __kasan_kmalloc+0x8f/0xa0 tcp_bpf_sendmsg+0x16b3/0x1cc0 Freed by task 91: __kasan_slab_free+0x43/0x70 kfree+0x131/0x3c0 tcp_bpf_sendmsg+0xec3/0x1cc0 msg_tx can only name the stack-local tmp or the shared cork. Check for tmp directly so a changed psock->cork cannot turn a shared message into an apparent local one.

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 2 months 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

CVSS scores of CVE-2026-68284, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.14% · top 97% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 604326b41a6fb9b4a78b6179335decee0365cd8c – < 0688e6fe599d2d39147ae9ece97944c6e1815ebf
    • affected 604326b41a6fb9b4a78b6179335decee0365cd8c – < b2bcbeabfd843d47468fa095b1bd08ddb90cf616
    • affected 604326b41a6fb9b4a78b6179335decee0365cd8c – < 54be47e7cbb936429c3bbdfc526ea943954aaf80
    • affected 604326b41a6fb9b4a78b6179335decee0365cd8c – < ee762f684eefa59de34d9ed93cab08336e834f47
    • affected 604326b41a6fb9b4a78b6179335decee0365cd8c – < cde4d6bcd9b73073c66498f6723c7b364c4dbc18
    • affected 604326b41a6fb9b4a78b6179335decee0365cd8c – < 786d690257ec7a0c839f8710456e444ce3f1348b
    • affected 604326b41a6fb9b4a78b6179335decee0365cd8c – < 752b1159ed5d0c48fe169a3721b96660a9822aa1
    • affected 604326b41a6fb9b4a78b6179335decee0365cd8c – < 2d66a033864e27ab8d5e44cb36f31d9d2413bee4
  • Linux · Linux

    • affected 4.20
    • unaffected < 4.20
    • unaffected 5.10.265 – ≤ 5.10.*
    • unaffected 5.15.216 – ≤ 5.15.*
    • unaffected 6.1.183 – ≤ 6.1.*
    • unaffected 6.6.148 – ≤ 6.6.*
    • unaffected 6.12.101 – ≤ 6.12.*
    • unaffected 6.18.42 – ≤ 6.18.*
    • unaffected 7.1.6 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .