CVE-2026-74282

tipc: prevent snt_unacked underflow on CONN_ACK

HIGH
7.5
CVSS Score
Published: August 15, 2026 at 05:57 AM UTC
Updated: October 16, 2026 at 07:17 PM 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
HIGH7.5
Exploit prediction
EPSS 0.7%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: tipc: prevent snt_unacked underflow on CONN_ACK tipc_sk_conn_proto_rcv() subtracts the peer-supplied connection ack count from the unsigned 16-bit send counter snt_unacked without checking that it does not exceed the number of messages actually outstanding: tsk->snt_unacked -= msg_conn_ack(hdr); msg_conn_ack() is read straight from a received CONN_MANAGER/CONN_ACK message. If the ack count is larger than snt_unacked, the subtraction wraps to a near-maximum value, leaving tsk_conn_cong() permanently true and starving the connection of further transmits. Validate the ACK count at the start of the CONN_ACK block and drop the message if it acknowledges more messages than are outstanding. A peer (or, for a local connection, the connected peer socket) can otherwise wedge a TIPC connection's send side by sending an oversized connection ack.

Affected

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

10724cc7bb7832b482df049c20fd824d928c5eaa4.7
Vendor states this is fixed in 1e2c956745777e6ffdee7f30da5935741c03ee1e (fixed)
Vendor states this is fixed in 3388145d258cf2c4c98278e3987296007d30672e (fixed)
Vendor states this is fixed in 3cfa3d8e0dc167850edeb5bf5a07757db83fd54e (fixed)
Vendor states this is fixed in 47ed873e4ceda34098bd46d8e96b4bb13cad3a04 (fixed)
Vendor states this is fixed in 67e55b054bf8025658dc0e255057f2a6236416bd (fixed)
Vendor states this is fixed in 96f91b8ae1a489b3eca137e7acf42cf985fb8939 (fixed)
Vendor states this is fixed in ab3e10b44ba5411779aac7afd2477917dd77750f (fixed)
Vendor states this is fixed in b44bebdd32c9ff66ee2aebfc317ced44bedd9335 (fixed)
Vendor states this is fixed in 4.7 (unaffected)
Vendor states this is fixed in 5.10.261 (unaffected)
Vendor states this is fixed in 5.15.212 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.97 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.5 (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.

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.5HIGHLinux
Vector?

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