CVE-2026-68289

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

N/A
Published: August 10, 2026 at 12:02 PM UTC
Updated: October 3, 2026 at 11:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.12 ≤ v < 6.1.1894.12 ≤ v < 6.12.1114.12 ≤ v < 6.18.534.12 ≤ v < 6.6.1584.12 ≤ v < 7.1.64.12 ≤ v < 7.24.12e9f8b10101c6da3ab000a2fb17162374c9bd2c69
Vendor states this is fixed in 1b6066313b9b8fac870483bf7a26d6bd56579747 (fixed)
Vendor states this is fixed in 47f42ff521b4eeb46e82f9a46a4783a99f7570d7 (fixed)
Vendor states this is fixed in 7364014fdc289225229eb08de8bcbf4580e78e4d (fixed)
Vendor states this is fixed in 93580911f02d1f4a506ec0a6fc4354140c53ffe8 (fixed)
Vendor states this is fixed in 9fd4f92671146b068809b6c34b50346cb30cf8f7 (fixed)
Vendor states this is fixed in fe9bf32bb18f2d35789d4960fb007d1059bbaa38 (fixed)
Vendor states this is fixed in 4.12 (unaffected)
Vendor states this is fixed in 6.1.189 (unaffected)
Vendor states this is fixed in 6.12.111 (unaffected)
Vendor states this is fixed in 6.18.53 (unaffected)
Vendor states this is fixed in 6.6.158 (unaffected)
Vendor states this is fixed in 7.1.6 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card