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-68289tipc: fix integer overflow in tipc_recvmsg() and tipc_recvstream()

Description

In the Linux kernel, the following vulnerability has been resolved: tipc: fix integer overflow in tipc_recvmsg() and tipc_recvstream() In tipc_recvmsg(), the copy length is computed as: copy = min_t(int, dlen - offset, buflen); buflen is size_t but min_t(int, ...) casts it to int. When buflen exceeds INT_MAX (e.g. 0xFFFFFFFF via io_uring provided buffers), it wraps negative, wins the comparison, and the negative copy length propagates to simple_copy_to_iter() where int-to-size_t promotion makes it SIZE_MAX, triggering a WARN_ON. tipc_recvstream() has the same pattern. Kernel panic - not syncing: kernel: panic_on_warn set ... RIP: 0010:simple_copy_to_iter+0x9e/0xd0 (net/core/datagram.c:521) Call Trace: __skb_datagram_iter+0x123/0x8b0 (net/core/datagram.c:402) skb_copy_datagram_iter+0x77/0x1a0 (net/core/datagram.c:534) tipc_recvmsg+0x3d7/0xe80 (net/tipc/socket.c:1934) io_recvmsg+0x47e/0xda0 Fix by changing min_t(int, ...) to min_t(size_t, ...) in both functions. The result is always <= (dlen - offset), which is bounded by TIPC maximum message size (0x1ffff bytes), so the implicit narrowing on assignment to int copy is always safe.

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 54 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.18% · top 92% 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 e9f8b10101c6da3ab000a2fb17162374c9bd2c69 – < 9fd4f92671146b068809b6c34b50346cb30cf8f7
    • affected e9f8b10101c6da3ab000a2fb17162374c9bd2c69 – < 93580911f02d1f4a506ec0a6fc4354140c53ffe8
    • affected e9f8b10101c6da3ab000a2fb17162374c9bd2c69 – < 1b6066313b9b8fac870483bf7a26d6bd56579747
    • affected e9f8b10101c6da3ab000a2fb17162374c9bd2c69 – < 7364014fdc289225229eb08de8bcbf4580e78e4d
    • affected e9f8b10101c6da3ab000a2fb17162374c9bd2c69 – < fe9bf32bb18f2d35789d4960fb007d1059bbaa38
    • affected e9f8b10101c6da3ab000a2fb17162374c9bd2c69 – < 47f42ff521b4eeb46e82f9a46a4783a99f7570d7
  • Linux · Linux

    • affected 4.12
    • unaffected < 4.12
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.111 – ≤ 6.12.*
    • unaffected 6.18.53 – ≤ 6.18.*
    • unaffected 7.1.6 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .