CVE-2022-49330
published 2025-02-26CVE-2022-49330: In the Linux kernel, the following vulnerability has been resolved: tcp: fix tcp_mtup_probe_success vs wrong snd_cwnd syzbot got a new report [1] finally…
PriorityP422medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.82%
53.6th percentile
In the Linux kernel, the following vulnerability has been resolved:
tcp: fix tcp_mtup_probe_success vs wrong snd_cwnd
syzbot got a new report [1] finally pointing to a very old bug,
added in initial support for MTU probing.
tcp_mtu_probe() has checks about starting an MTU probe if
tcp_snd_cwnd(tp) >= 11.
But nothing prevents tcp_snd_cwnd(tp) to be reduced later
and before the MTU probe succeeds.
This bug would lead to potential zero-divides.
Debugging added in commit 40570375356c ("tcp: add accessors
to read/set tp->snd_cwnd") has paid off :)
While we are at it, address potential overflows in this code.
[1]
WARNING: CPU: 1 PID: 14132 at include/net/tcp.h:1219 tcp_mtup_probe_success+0x366/0x570 net/ipv4/tcp_input.c:2712
Modules linked in:
CPU: 1 PID: 14132 Comm: syz-executor.2 Not tainted 5.18.0-syzkaller-07857-gbabf0bb978e3 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:tcp_snd_cwnd_set include/net/tcp.h:1219 [inline]
RIP: 0010:tcp_mtup_probe_success+0x366/0x570 net/ipv4/tcp_input.c:2712
Code: 74 08 48 89 ef e8 da 80 17 f9 48 8b 45 00 65 48 ff 80 80 03 00 00 48 83 c4 30 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 aa b0 c5 f8 0b e9 16 fe ff ff 48 8b 4c 24 08 80 e1 07 38 c1 0f 8c c7 fc ff
RSP: 0018:ffffc900079e70f8 EFLAGS: 00010287
RAX: ffffffff88c0f7f6 RBX: ffff8880756e7a80 RCX: 0000000000040000
RDX: ffffc9000c6c4000 RSI: 0000000000031f9e RDI: 0000000000031f9f
RBP: 0000000000000000 R08: ffffffff88c0f606 R09: ffffc900079e7520
R10: ffffed101011226d R11: 1ffff1101011226c R12: 1ffff1100eadcf50
R13: ffff8880756e72c0 R14: 1ffff1100eadcf89 R15: dffffc0000000000
FS: 00007f643236e700(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f1ab3f1e2a0 CR3: 0000000064fe7000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
tcp_clean_rtx_queue+0x223a/0
Affected
23 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 5.18.5-1 (bookworm) | linux 5.18.5-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 5d424d5a674f782d0659a3b66d951f412901faee < 29e13f6b38f0816af2012e0725507754e8f4569c | 29e13f6b38f0816af2012e0725507754e8f4569c |
| linux | linux | >= 5d424d5a674f782d0659a3b66d951f412901faee < 42726877453afdbe1508a8a96884ea907741d9a7 | 42726877453afdbe1508a8a96884ea907741d9a7 |
| linux | linux | >= 5d424d5a674f782d0659a3b66d951f412901faee < f2845e1504a3bc4f3381394f057e8b63cb5f3f7a | f2845e1504a3bc4f3381394f057e8b63cb5f3f7a |
| linux | linux | >= 5d424d5a674f782d0659a3b66d951f412901faee < 602b338e3c3cd7f935f3f5011882961d074e5ac1 | 602b338e3c3cd7f935f3f5011882961d074e5ac1 |
| linux | linux | >= 5d424d5a674f782d0659a3b66d951f412901faee < 9ba2b4ac35935f05ac98cff722f36ba07d62270e | 9ba2b4ac35935f05ac98cff722f36ba07d62270e |
| linux | linux | >= 5d424d5a674f782d0659a3b66d951f412901faee < 90385f2b65d0cd2b3b1ac8909f0cc6dd31062cfc | 90385f2b65d0cd2b3b1ac8909f0cc6dd31062cfc |
| linux | linux | >= 5d424d5a674f782d0659a3b66d951f412901faee < aa7f333efd1138a68517a6a6a69ae540dd59d800 | aa7f333efd1138a68517a6a6a69ae540dd59d800 |
| linux | linux | >= 5d424d5a674f782d0659a3b66d951f412901faee < 38ca71a24cd4845021eed35fd2594d89dba9a5a8 | 38ca71a24cd4845021eed35fd2594d89dba9a5a8 |
| linux | linux | >= 5d424d5a674f782d0659a3b66d951f412901faee < 11825765291a93d8e7f44230da67b9f607c777bf | 11825765291a93d8e7f44230da67b9f607c777bf |
| linux | linux_kernel | >= 0 < 5.10.127-1 | 5.10.127-1 |
| linux | linux_kernel | >= 0 < 5.18.5-1 | 5.18.5-1 |
| linux | linux_kernel | >= 0 < 5.18.5-1 | 5.18.5-1 |
| linux | linux_kernel | >= 0 < 5.18.5-1 | 5.18.5-1 |
| linux | linux_kernel | >= 2.6.17 < 4.9.318 | 4.9.318 |
| linux | linux_kernel | >= 4.10 < 4.14.283 | 4.14.283 |
| linux | linux_kernel | >= 4.15 < 4.19.247 | 4.19.247 |
| linux | linux_kernel | >= 4.20 < 5.4.198 | 5.4.198 |
| linux | linux_kernel | >= 5.11 < 5.15.47 | 5.15.47 |
| linux | linux_kernel | >= 5.16 < 5.17.15 | 5.17.15 |
| linux | linux_kernel | >= 5.18 < 5.18.4 | 5.18.4 |
| linux | linux_kernel | >= 5.5 < 5.10.122 | 5.10.122 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-ff7q-8m86-737m: In the Linux kernel, the following vulnerability has been resolved:
tcp: fix tcp_mtup_probe_success vs wrong snd_cwnd
syzbot got a new report [1] fi
ghsa_unreviewed·2025-09-22
CVE-2022-49330 [MEDIUM] CWE-369 GHSA-ff7q-8m86-737m: In the Linux kernel, the following vulnerability has been resolved:
tcp: fix tcp_mtup_probe_success vs wrong snd_cwnd
syzbot got a new report [1] fi
In the Linux kernel, the following vulnerability has been resolved:
tcp: fix tcp_mtup_probe_success vs wrong snd_cwnd
syzbot got a new report [1] finally pointing to a very old bug,
added in initial support for MTU probing.
tcp_mtu_probe() has checks about starting an MTU probe if
tcp_snd_cwnd(tp) >= 11.
But nothing prevents tcp_snd_cwnd(tp) to be reduced later
and before the MTU probe succeeds.
This bug would lead to potential zero-divides.
Debugging added in commit 40570375356c ("tcp: add accessors
to read/set tp->snd_cwnd") has paid off :)
While we are at it, address potential overflows in this code.
[1]
WARNING: CPU: 1 PID: 14132 at include/net/tcp.h:1219 tcp_mtup_probe_success+0x366/0x570 net/ipv4/tcp_input.c:2712
Modules linked in:
CPU: 1 PID: 14132 Comm: syz-executor.2 Not t
OSV
CVE-2022-49330: In the Linux kernel, the following vulnerability has been resolved: tcp: fix tcp_mtup_probe_success vs wrong snd_cwnd syzbot got a new report [1] fina
osv·2025-02-26·CVSS 5.5
CVE-2022-49330 [MEDIUM] CVE-2022-49330: In the Linux kernel, the following vulnerability has been resolved: tcp: fix tcp_mtup_probe_success vs wrong snd_cwnd syzbot got a new report [1] fina
In the Linux kernel, the following vulnerability has been resolved: tcp: fix tcp_mtup_probe_success vs wrong snd_cwnd syzbot got a new report [1] finally pointing to a very old bug, added in initial support for MTU probing. tcp_mtu_probe() has checks about starting an MTU probe if tcp_snd_cwnd(tp) >= 11. But nothing prevents tcp_snd_cwnd(tp) to be reduced later and before the MTU probe succeeds. This bug would lead to potential zero-divides. Debugging added in commit 40570375356c ("tcp: add accessors to read/set tp->snd_cwnd") has paid off :) While we are at it, address potential overflows in this code. [1] WARNING: CPU: 1 PID: 14132 at include/net/tcp.h:1219 tcp_mtup_probe_success+0x366/0x570 net/ipv4/tcp_input.c:2712 Modules linked in: CPU: 1 PID: 14132 Comm: syz-executor.2 Not tainted 5
Red Hat
kernel: tcp: fix tcp_mtup_probe_success vs wrong snd_cwnd
vendor_redhat·2025-02-26·CVSS 5.5
CVE-2022-49330 [MEDIUM] kernel: tcp: fix tcp_mtup_probe_success vs wrong snd_cwnd
kernel: tcp: fix tcp_mtup_probe_success vs wrong snd_cwnd
In the Linux kernel, the following vulnerability has been resolved:
tcp: fix tcp_mtup_probe_success vs wrong snd_cwnd
syzbot got a new report [1] finally pointing to a very old bug,
added in initial support for MTU probing.
tcp_mtu_probe() has checks about starting an MTU probe if
tcp_snd_cwnd(tp) >= 11.
But nothing prevents tcp_snd_cwnd(tp) to be reduced later
and before the MTU probe succeeds.
This bug would lead to potential zero-divides.
Debugging added in commit 40570375356c ("tcp: add accessors
to read/set tp->snd_cwnd") has paid off :)
While we are at it, address potential overflows in this code.
[1]
WARNING: CPU: 1 PID: 14132 at include/net/tcp.h:1219 tcp_mtup_probe_success+0x366/0x570 net/ipv4/tcp_input.c:2712
Modules link
Debian
CVE-2022-49330: linux - In the Linux kernel, the following vulnerability has been resolved: tcp: fix tc...
vendor_debian·2022·CVSS 5.5
CVE-2022-49330 [MEDIUM] CVE-2022-49330: linux - In the Linux kernel, the following vulnerability has been resolved: tcp: fix tc...
In the Linux kernel, the following vulnerability has been resolved: tcp: fix tcp_mtup_probe_success vs wrong snd_cwnd syzbot got a new report [1] finally pointing to a very old bug, added in initial support for MTU probing. tcp_mtu_probe() has checks about starting an MTU probe if tcp_snd_cwnd(tp) >= 11. But nothing prevents tcp_snd_cwnd(tp) to be reduced later and before the MTU probe succeeds. This bug would lead to potential zero-divides. Debugging added in commit 40570375356c ("tcp: add accessors to read/set tp->snd_cwnd") has paid off :) While we are at it, address potential overflows in this code. [1] WARNING: CPU: 1 PID: 14132 at include/net/tcp.h:1219 tcp_mtup_probe_success+0x366/0x570 net/ipv4/tcp_input.c:2712 Modules linked in: CPU: 1 PID: 14132 Comm: syz-executor.2 Not tainted 5
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/11825765291a93d8e7f44230da67b9f607c777bfhttps://git.kernel.org/stable/c/29e13f6b38f0816af2012e0725507754e8f4569chttps://git.kernel.org/stable/c/38ca71a24cd4845021eed35fd2594d89dba9a5a8https://git.kernel.org/stable/c/42726877453afdbe1508a8a96884ea907741d9a7https://git.kernel.org/stable/c/602b338e3c3cd7f935f3f5011882961d074e5ac1https://git.kernel.org/stable/c/90385f2b65d0cd2b3b1ac8909f0cc6dd31062cfchttps://git.kernel.org/stable/c/9ba2b4ac35935f05ac98cff722f36ba07d62270ehttps://git.kernel.org/stable/c/aa7f333efd1138a68517a6a6a69ae540dd59d800https://git.kernel.org/stable/c/f2845e1504a3bc4f3381394f057e8b63cb5f3f7a
2025-02-26
Published