CVE-2026-68289

published 10 Aug 2026 · updated 16 Nov 2026

tipc: fix integer overflow in tipc_recvmsg() and tipc_recvstream()

5.5MediumCVSS 5.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel fe9bf32bb18f2d35789d4960fb007d1059bbaa38, Kernel 1b6066313b9b8fac870483bf7a26d6bd56579747, Kernel 47f42ff521b4eeb46e82f9a46a4783a99f7570d7 and 8 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=e9f8b10101c6da3ab000a2fb17162374c9bd2c69 <fe9bf32bb18f2d35789d4960fb007d1059bbaa38, >=e9f8b10101c6da3ab000a2fb17162374c9bd2c69 <1b6066313b9b8fac870483bf7a26d6bd56579747, >=e9f8b10101c6da3ab000a2fb17162374c9bd2c69 <47f42ff521b4eeb46e82f9a46a4783a99f7570d7, >=e9f8b10101c6da3ab000a2fb17162374c9bd2c69 <7364014fdc289225229eb08de8bcbf4580e78e4d, >=e9f8b10101c6da3ab000a2fb17162374c9bd2c69 <93580911f02d1f4a506ec0a6fc4354140c53ffe8, >=e9f8b10101c6da3ab000a2fb17162374c9bd2c69 <9fd4f92671146b068809b6c34b50346cb30cf8f7, =4.12fe9bf32bb18f2d35789d4960fb007d1059bbaa38, 1b6066313b9b8fac870483bf7a26d6bd56579747, 47f42ff521b4eeb46e82f9a46a4783a99f7570d7, 7364014fdc289225229eb08de8bcbf4580e78e4d, 93580911f02d1f4a506ec0a6fc4354140c53ffe8, 9fd4f92671146b068809b6c34b50346cb30cf8f7
linux-kernel: Kernel>=6.13.0 <6.18.53, >=6.19.0 <7.1.6, >=6.2.0 <6.6.158, >=6.7.0 <6.12.111, >=4.12.0 <6.1.1896.18.53, 7.1.6, 6.6.158, 6.12.111, 6.1.189

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-68289 severity on Zeptric[![CVE-2026-68289](https://zeptric.io/badge/cve/CVE-2026-68289.svg)](https://zeptric.io/cve/CVE-2026-68289)