CVE-2022-49372
published 2025-02-26CVE-2022-49372: In the Linux kernel, the following vulnerability has been resolved: tcp: tcp_rtx_synack() can be called from process context Laurent reported the enclosed…
PriorityP422medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.29%
21.3th percentile
In the Linux kernel, the following vulnerability has been resolved:
tcp: tcp_rtx_synack() can be called from process context
Laurent reported the enclosed report [1]
This bug triggers with following coditions:
0) Kernel built with CONFIG_DEBUG_PREEMPT=y
1) A new passive FastOpen TCP socket is created.
This FO socket waits for an ACK coming from client to be a complete
ESTABLISHED one.
2) A socket operation on this socket goes through lock_sock()
release_sock() dance.
3) While the socket is owned by the user in step 2),
a retransmit of the SYN is received and stored in socket backlog.
4) At release_sock() time, the socket backlog is processed while
in process context.
5) A SYNACK packet is cooked in response of the SYN retransmit.
6) -> tcp_rtx_synack() is called in process context.
Before blamed commit, tcp_rtx_synack() was always called from BH handler,
from a timer handler.
Fix this by using TCP_INC_STATS() & NET_INC_STATS()
which do not assume caller is in non preemptible context.
[1]
BUG: using __this_cpu_add() in preemptible [00000000] code: epollpep/2180
caller is tcp_rtx_synack.part.0+0x36/0xc0
CPU: 10 PID: 2180 Comm: epollpep Tainted: G OE 5.16.0-0.bpo.4-amd64 #1 Debian 5.16.12-1~bpo11+1
Hardware name: Supermicro SYS-5039MC-H8TRF/X11SCD-F, BIOS 1.7 11/23/2021
Call Trace:
dump_stack_lvl+0x48/0x5e
check_preemption_disabled+0xde/0xe0
tcp_rtx_synack.part.0+0x36/0xc0
tcp_rtx_synack+0x8d/0xa0
? kmem_cache_alloc+0x2e0/0x3e0
? apparmor_file_alloc_security+0x3b/0x1f0
inet_rtx_syn_ack+0x16/0x30
tcp_check_req+0x367/0x610
tcp_rcv_state_process+0x91/0xf60
? get_nohz_timer_target+0x18/0x1a0
? lock_timer_base+0x61/0x80
? preempt_count_add+0x68/0xa0
tcp_v4_do_rcv+0xbd/0x270
__release_sock+0x6d/0xb0
release_sock+0x2b/0x90
sock_setsockopt+0x138/0x1140
? __sys_getsockname+0x7e/0xc0
? aa_sk_perm+0x3e/0x1a0
__sys_setsockopt+0x198/0x1e0
__x64_sys_setsockopt+0x21/0x30
do_syscall_64+0x38/0xc0
entry_SYSCALL_64_after_hwframe+0x44/0xae
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 | >= 168a8f58059a22feb9e9a2dcc1b8053dbbbc12ef < 3db889f883e65bbd3b1401279bfc1e9ed255c481 | 3db889f883e65bbd3b1401279bfc1e9ed255c481 |
| linux | linux | >= 168a8f58059a22feb9e9a2dcc1b8053dbbbc12ef < c348b0f8d035fc4bdc040796889beec7218bd1b8 | c348b0f8d035fc4bdc040796889beec7218bd1b8 |
| linux | linux | >= 168a8f58059a22feb9e9a2dcc1b8053dbbbc12ef < 58bd38cbc961fd799842b7be8c5222310f04b908 | 58bd38cbc961fd799842b7be8c5222310f04b908 |
| linux | linux | >= 168a8f58059a22feb9e9a2dcc1b8053dbbbc12ef < d05c2fdf8e10528bb6751bd95243e862d5402a9b | d05c2fdf8e10528bb6751bd95243e862d5402a9b |
| linux | linux | >= 168a8f58059a22feb9e9a2dcc1b8053dbbbc12ef < 0a0f7f84148445c9f02f226928803a870139d820 | 0a0f7f84148445c9f02f226928803a870139d820 |
| linux | linux | >= 168a8f58059a22feb9e9a2dcc1b8053dbbbc12ef < 88cd232146207ff1d41dededed5e77c0d4438113 | 88cd232146207ff1d41dededed5e77c0d4438113 |
| linux | linux | >= 168a8f58059a22feb9e9a2dcc1b8053dbbbc12ef < bdc28a8fb43cc476e33b11519235adb816ce00e8 | bdc28a8fb43cc476e33b11519235adb816ce00e8 |
| linux | linux | >= 168a8f58059a22feb9e9a2dcc1b8053dbbbc12ef < d8e1bc6029acac796293310aacef7b7336f35b6a | d8e1bc6029acac796293310aacef7b7336f35b6a |
| linux | linux | >= 168a8f58059a22feb9e9a2dcc1b8053dbbbc12ef < 0a375c822497ed6ad6b5da0792a12a6f1af10c0b | 0a375c822497ed6ad6b5da0792a12a6f1af10c0b |
| 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 | >= 3.7 < 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-48pg-x75p-m28c: In the Linux kernel, the following vulnerability has been resolved:
tcp: tcp_rtx_synack() can be called from process context
Laurent reported the en
ghsa_unreviewed·2025-10-21
CVE-2022-49372 [MEDIUM] GHSA-48pg-x75p-m28c: In the Linux kernel, the following vulnerability has been resolved:
tcp: tcp_rtx_synack() can be called from process context
Laurent reported the en
In the Linux kernel, the following vulnerability has been resolved:
tcp: tcp_rtx_synack() can be called from process context
Laurent reported the enclosed report [1]
This bug triggers with following coditions:
0) Kernel built with CONFIG_DEBUG_PREEMPT=y
1) A new passive FastOpen TCP socket is created.
This FO socket waits for an ACK coming from client to be a complete
ESTABLISHED one.
2) A socket operation on this socket goes through lock_sock()
release_sock() dance.
3) While the socket is owned by the user in step 2),
a retransmit of the SYN is received and stored in socket backlog.
4) At release_sock() time, the socket backlog is processed while
in process context.
5) A SYNACK packet is cooked in response of the SYN retransmit.
6) -> tcp_rtx_synack() is called in process context.
B
OSV
CVE-2022-49372: In the Linux kernel, the following vulnerability has been resolved: tcp: tcp_rtx_synack() can be called from process context Laurent reported the encl
osv·2025-02-26·CVSS 5.5
CVE-2022-49372 [MEDIUM] CVE-2022-49372: In the Linux kernel, the following vulnerability has been resolved: tcp: tcp_rtx_synack() can be called from process context Laurent reported the encl
In the Linux kernel, the following vulnerability has been resolved: tcp: tcp_rtx_synack() can be called from process context Laurent reported the enclosed report [1] This bug triggers with following coditions: 0) Kernel built with CONFIG_DEBUG_PREEMPT=y 1) A new passive FastOpen TCP socket is created. This FO socket waits for an ACK coming from client to be a complete ESTABLISHED one. 2) A socket operation on this socket goes through lock_sock() release_sock() dance. 3) While the socket is owned by the user in step 2), a retransmit of the SYN is received and stored in socket backlog. 4) At release_sock() time, the socket backlog is processed while in process context. 5) A SYNACK packet is cooked in response of the SYN retransmit. 6) -> tcp_rtx_synack() is called in process context. Before
Red Hat
kernel: tcp: tcp_rtx_synack() can be called from process context
vendor_redhat·2025-02-26·CVSS 5.5
CVE-2022-49372 [MEDIUM] kernel: tcp: tcp_rtx_synack() can be called from process context
kernel: tcp: tcp_rtx_synack() can be called from process context
In the Linux kernel, the following vulnerability has been resolved:
tcp: tcp_rtx_synack() can be called from process context
Laurent reported the enclosed report [1]
This bug triggers with following coditions:
0) Kernel built with CONFIG_DEBUG_PREEMPT=y
1) A new passive FastOpen TCP socket is created.
This FO socket waits for an ACK coming from client to be a complete
ESTABLISHED one.
2) A socket operation on this socket goes through lock_sock()
release_sock() dance.
3) While the socket is owned by the user in step 2),
a retransmit of the SYN is received and stored in socket backlog.
4) At release_sock() time, the socket backlog is processed while
in process context.
5) A SYNACK packet is cooked in response of the SYN retran
Debian
CVE-2022-49372: linux - In the Linux kernel, the following vulnerability has been resolved: tcp: tcp_rt...
vendor_debian·2022·CVSS 5.5
CVE-2022-49372 [MEDIUM] CVE-2022-49372: linux - In the Linux kernel, the following vulnerability has been resolved: tcp: tcp_rt...
In the Linux kernel, the following vulnerability has been resolved: tcp: tcp_rtx_synack() can be called from process context Laurent reported the enclosed report [1] This bug triggers with following coditions: 0) Kernel built with CONFIG_DEBUG_PREEMPT=y 1) A new passive FastOpen TCP socket is created. This FO socket waits for an ACK coming from client to be a complete ESTABLISHED one. 2) A socket operation on this socket goes through lock_sock() release_sock() dance. 3) While the socket is owned by the user in step 2), a retransmit of the SYN is received and stored in socket backlog. 4) At release_sock() time, the socket backlog is processed while in process context. 5) A SYNACK packet is cooked in response of the SYN retransmit. 6) -> tcp_rtx_synack() is called in process context. Before
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/0a0f7f84148445c9f02f226928803a870139d820https://git.kernel.org/stable/c/0a375c822497ed6ad6b5da0792a12a6f1af10c0bhttps://git.kernel.org/stable/c/3db889f883e65bbd3b1401279bfc1e9ed255c481https://git.kernel.org/stable/c/58bd38cbc961fd799842b7be8c5222310f04b908https://git.kernel.org/stable/c/88cd232146207ff1d41dededed5e77c0d4438113https://git.kernel.org/stable/c/bdc28a8fb43cc476e33b11519235adb816ce00e8https://git.kernel.org/stable/c/c348b0f8d035fc4bdc040796889beec7218bd1b8https://git.kernel.org/stable/c/d05c2fdf8e10528bb6751bd95243e862d5402a9bhttps://git.kernel.org/stable/c/d8e1bc6029acac796293310aacef7b7336f35b6a
2025-02-26
Published