Linux Kernel up to 6.19.8 tipc tipc_sk_filter_connect divide by zero

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.0$0-$5k0.00

Summaryinfo

A vulnerability was found in Linux Kernel up to 6.19.8. It has been rated as critical. This issue affects the function tipc_sk_filter_connect of the component tipc. The manipulation leads to divide by zero. This vulnerability is documented as CVE-2026-43411. There is not any exploit available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability was found in Linux Kernel up to 6.19.8 and classified as critical. This issue affects the function tipc_sk_filter_connect of the component tipc. The manipulation with an unknown input leads to a divide by zero vulnerability. Using CWE to declare the problem leads to CWE-369. The product divides a value by zero. Impacted is availability. The summary by CVE is:

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)

The advisory is shared at git.kernel.org. The identification of this vulnerability is CVE-2026-43411 since 05/01/2026. The exploitation is known to be difficult. Technical details are known, but no exploit is available.

The vulnerability scanner Nessus provides a plugin with the ID 321588 (SUSE SLES16 Security Update : kernel (SUSE-SU-2026:22127-1)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 5.10.253, 5.15.203, 6.1.167, 6.6.130, 6.12.78, 6.18.19 or 6.19.9 eliminates this vulnerability. Applying the patch 600feb0a66a98c6b7f6f02b5f3612e75f9b8540f/3bc9998041076ee05d3f312a22cee6b2ca35527f/579956f9f297eb1b6a5d24de313f3acccee1f9d5/a360d3815aae1f00dd71b7714a846482e85cc1f7/c2ebfbe63deb7bfd4dc2532bae62a7ed67713272/2754e7b3d64748643df867d1ea6fec522914b635/338c5edeb6ae3f12a4b84dff9d71f6f7f8c202c3/6c5a9baa15de240e747263aba435a0951da8d8d2 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at Tenable (321588). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.1
VulDB Meta Temp Score: 5.0

VulDB Base Score: 4.8
VulDB Temp Score: 4.6
VulDB Vector: 🔒
VulDB Reliability: 🔍

NVD Base Score: 5.5
NVD Vector: 🔒

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Divide by zero
CWE: CWE-369 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 321588
Nessus Name: SUSE SLES16 Security Update : kernel (SUSE-SU-2026:22127-1)

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.10.253/5.15.203/6.1.167/6.6.130/6.12.78/6.18.19/6.19.9
Patch: 600feb0a66a98c6b7f6f02b5f3612e75f9b8540f/3bc9998041076ee05d3f312a22cee6b2ca35527f/579956f9f297eb1b6a5d24de313f3acccee1f9d5/a360d3815aae1f00dd71b7714a846482e85cc1f7/c2ebfbe63deb7bfd4dc2532bae62a7ed67713272/2754e7b3d64748643df867d1ea6fec522914b635/338c5edeb6ae3f12a4b84dff9d71f6f7f8c202c3/6c5a9baa15de240e747263aba435a0951da8d8d2

Timelineinfo

05/01/2026 CVE reserved
05/08/2026 +7 days Advisory disclosed
05/08/2026 +0 days VulDB entry created
06/20/2026 +43 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-43411 (🔒)
GCVE (CVE): GCVE-0-2026-43411
GCVE (VulDB): GCVE-100-362201

Entryinfo

Created: 05/08/2026 18:22
Updated: 06/20/2026 21:47
Changes: 05/08/2026 18:22 (59), 05/22/2026 02:33 (11), 06/20/2026 21:47 (2)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you want to use VulDB in your project?

Use the official API to access entries easily!