Skip to main content
VulnerabilityPublished Updated

CVE-2026-43411: Linux kernel · tipc: fix divide-by-zero in tipc_sk_filter_connect()

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in c2ebfbe63deb7bfd4dc2532bae62a7ed67713272 : update Linux kernel when convenient.

Data as of 6 Nov 2026, 15:49 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in c2ebfbe63deb7bfd4dc2532bae62a7ed67713272, a360d3815aae1f00dd71b7714a846482e85cc1f7, 579956f9f297eb1b6a5d24de313f3acccee1f9d5 +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 6787927475e52f6933e3affce365dabb2aa2fadf, < c2ebfbe63deb7bfd4dc2532bae62a7ed67713272
Fixed in
  • c2ebfbe63deb7bfd4dc2532bae62a7ed67713272
LinuxLinuxAffected
  • ≥ 6787927475e52f6933e3affce365dabb2aa2fadf, < a360d3815aae1f00dd71b7714a846482e85cc1f7
Fixed in
  • a360d3815aae1f00dd71b7714a846482e85cc1f7
LinuxLinuxAffected
  • ≥ 6787927475e52f6933e3affce365dabb2aa2fadf, < 579956f9f297eb1b6a5d24de313f3acccee1f9d5
Fixed in
  • 579956f9f297eb1b6a5d24de313f3acccee1f9d5
LinuxLinuxAffected
  • ≥ 6787927475e52f6933e3affce365dabb2aa2fadf, < 2754e7b3d64748643df867d1ea6fec522914b635
Fixed in
  • 2754e7b3d64748643df867d1ea6fec522914b635
LinuxLinuxAffected
  • ≥ 6787927475e52f6933e3affce365dabb2aa2fadf, < 600feb0a66a98c6b7f6f02b5f3612e75f9b8540f
Fixed in
  • 600feb0a66a98c6b7f6f02b5f3612e75f9b8540f
LinuxLinuxAffected
  • ≥ 6787927475e52f6933e3affce365dabb2aa2fadf, < 338c5edeb6ae3f12a4b84dff9d71f6f7f8c202c3
Fixed in
  • 338c5edeb6ae3f12a4b84dff9d71f6f7f8c202c3

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)

References

Community reviews

Loading reviews…