tipc: prevent snt_unacked underflow on CONN_ACK
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.97, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From 10724cc7bb7832b482df049c20fd824d928c5eaa · fixed in 3388145d258cf2c4c98278e3987296007d30672e; From 10724cc7bb7832b482df049c20fd824d928c5eaa · fixed in 67e55b054bf8025658dc0e255057f2a6236416bd; From 10724cc7bb7832b482df049c20fd824d928c5eaa · fixed in 96f91b8ae1a489b3eca137e7acf42cf985fb8939; From 10724cc7bb7832b482df049c20fd824d928c5eaa · fixed in 47ed873e4ceda34098bd46d8e96b4bb13cad3a04; From 10724cc7bb7832b482df049c20fd824d928c5eaa · fixed in b44bebdd32c9ff66ee2aebfc317ced44bedd9335; From 10724cc7bb7832b482df049c20fd824d928c5eaa · fixed in 3cfa3d8e0dc167850edeb5bf5a07757db83fd54e; From 10724cc7bb7832b482df049c20fd824d928c5eaa · fixed in 1e2c956745777e6ffdee7f30da5935741c03ee1e; From 10724cc7bb7832b482df049c20fd824d928c5eaa · fixed in ab3e10b44ba5411779aac7afd2477917dd77750f
- Linux Linux
4.7
- KernelLinux
From 4.7.0 · fixed in 5.10.261; From 5.11.0 · fixed in 5.15.212; From 5.16.0 · fixed in 6.1.178; From 6.2.0 · fixed in 6.6.145; From 6.7.0 · fixed in 6.12.97; From 6.13.0 · fixed in 6.18.40; From 6.19.0 · fixed in 7.1.5
References 8
git.kernel.org
- stable/c/3388145d258cf2c4c98278e3987296007d30672e
- stable/c/67e55b054bf8025658dc0e255057f2a6236416bd
- stable/c/96f91b8ae1a489b3eca137e7acf42cf985fb8939
- stable/c/47ed873e4ceda34098bd46d8e96b4bb13cad3a04
- stable/c/b44bebdd32c9ff66ee2aebfc317ced44bedd9335
- stable/c/3cfa3d8e0dc167850edeb5bf5a07757db83fd54e
- stable/c/1e2c956745777e6ffdee7f30da5935741c03ee1e
- stable/c/ab3e10b44ba5411779aac7afd2477917dd77750f