CVE-2026-43411

tipc: fix divide-by-zero in tipc_sk_filter_connect()

MEDIUM
5.5
CVSS Score
Published: May 8, 2026 at 02:21 PM UTC
Updated: June 17, 2026 at 10:49 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
MEDIUM5.5
Exploit prediction
EPSS 0.1%

Description

In the Linux kernel, the following vulnerability has been resolved: tipc: fix divide-by-zero in tipc_sk_filter_connect() A user can set conn_timeout to any value via setsockopt(TIPC_CONN_TIMEOUT), including values less than 4. When a SYN is rejected with TIPC_ERR_OVERLOAD and the retry path in tipc_sk_filter_connect() executes: delay %= (tsk->conn_timeout / 4); If conn_timeout is in the range [0, 3], the integer division yields 0, and the modulo operation triggers a divide-by-zero exception, causing a kernel oops/panic. Fix this by clamping conn_timeout to a minimum of 4 at the point of use in tipc_sk_filter_connect(). Oops: divide error: 0000 [#1] SMP KASAN NOPTI CPU: 0 UID: 0 PID: 119 Comm: poc-F144 Not tainted 7.0.0-rc2+ RIP: 0010:tipc_sk_filter_rcv (net/tipc/socket.c:2236 net/tipc/socket.c:2362) Call Trace: tipc_sk_backlog_rcv (include/linux/instrumented.h:82 include/linux/atomic/atomic-instrumented.h:32 include/net/sock.h:2357 net/tipc/socket.c:2406) __release_sock (include/net/sock.h:1185 net/core/sock.c:3213) release_sock (net/core/sock.c:3797) tipc_connect (net/tipc/socket.c:2570) __sys_connect (include/linux/file.h:62 include/linux/file.h:83 net/socket.c:2098)

Affected

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

4.20 ≤ v < 5.10.2534.20 ≤ v < 5.15.2034.20 ≤ v < 6.1.1674.20 ≤ v < 6.12.784.20 ≤ v < 6.18.194.20 ≤ v < 6.19.94.20 ≤ v < 6.6.1304.20 ≤ v < 7.05.11 ≤ v < 5.15.2035.16 ≤ v < 6.1.1676.13 ≤ v < 6.18.196.19 ≤ v < 6.19.96.2 ≤ v < 6.6.1306.7 ≤ v < 6.12.784.206787927475e52f6933e3affce365dabb2aa2fadf7.0 rc17.0 rc27.0 rc3
Vendor states this is fixed in 2754e7b3d64748643df867d1ea6fec522914b635 (fixed)
Vendor states this is fixed in 338c5edeb6ae3f12a4b84dff9d71f6f7f8c202c3 (fixed)
Vendor states this is fixed in 3bc9998041076ee05d3f312a22cee6b2ca35527f (fixed)
Vendor states this is fixed in 579956f9f297eb1b6a5d24de313f3acccee1f9d5 (fixed)
Vendor states this is fixed in 600feb0a66a98c6b7f6f02b5f3612e75f9b8540f (fixed)
Vendor states this is fixed in 6c5a9baa15de240e747263aba435a0951da8d8d2 (fixed)
Vendor states this is fixed in a360d3815aae1f00dd71b7714a846482e85cc1f7 (fixed)
Vendor states this is fixed in c2ebfbe63deb7bfd4dc2532bae62a7ed67713272 (fixed)
Vendor states this is fixed in 4.20 (unaffected)
Vendor states this is fixed in 5.10.253 (unaffected)
Vendor states this is fixed in 5.15.203 (unaffected)
Vendor states this is fixed in 6.1.167 (unaffected)
Vendor states this is fixed in 6.12.78 (unaffected)
Vendor states this is fixed in 6.18.19 (unaffected)
Vendor states this is fixed in 6.19.9 (unaffected)
Vendor states this is fixed in 6.6.130 (unaffected)
Vendor states this is fixed in 7.0 (unaffected)

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-369

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