CVE-2022-49372 json
tcp: tcp_rtx_synack() can be called from process context
published 2025-02-26 20 mo ago modified 2026-06-17 4 mo ago also EUVD-2022-54857
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 21%
- public exploits
- 0
- none known
Summary
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: <TASK> 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
Patch / fix
- Linux Linux 4.9.318, 4.14.283, 4.19.247, 5.4.198, 5.10.122, 5.15.47, 5.17.15, 5.18.4, 5.19
- linux Debian 14, Debian 13, Debian 12 5.18.5-1
debian advisories DEBIAN-CVE-2022-49372
- linux Ubuntu 18.04 LTS 4.15.0-192.203
- linux Ubuntu 20.04 LTS 5.4.0-126.142
- linux Ubuntu 22.04 LTS 5.15.0-48.54
- linux-aws Ubuntu 18.04 LTS 4.15.0-1140.151
- linux-aws Ubuntu 20.04 LTS 5.4.0-1085.92
- linux-aws Ubuntu 22.04 LTS 5.15.0-1020.24
- linux-gcp Ubuntu 20.04 LTS 5.4.0-1089.97
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1018.24
ubuntu advisories UBUNTU-CVE-2022-49372
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel RHEL 9 5.14.0-284.11.1.el9_2
- perf RHEL 9 5.14.0-284.11.1.el9_2
- rtla RHEL 9 5.14.0-284.11.1.el9_2
- bpftool RHEL 9 7.0.0-284.11.1.el9_2
- kernel-64k RHEL 9 5.14.0-284.11.1.el9_2
- kernel-core RHEL 9 5.14.0-284.11.1.el9_2
- kernel-tools RHEL 9 5.14.0-284.11.1.el9_2
- python3-perf RHEL 9 5.14.0-284.11.1.el9_2
red hat advisories RHSA-2023:2458RHSA-2023:2951
- kernel-syms SLES LTSS Extended Security 12 SP5, SLES 12 SP5-LTSS 4.12.14-122.255.1
- kernel-source SLES LTSS Extended Security 12 SP5, SLES 12 SP5-LTSS 4.12.14-122.255.1
- kernel-default SLES LTSS Extended Security 12 SP5, SLES 12 SP5-LTSS, SLE Live Patching 12 SP5 4.12.14-122.255.1
- kgraft-patch-SLE12-SP5_Update_67 SLE Live Patching 12 SP5 1-8.5.1
suse advisories SUSE-SU-2025:1293-1
- git.kernel.org/stable/c/3db889f883e65bbd3b1401279bfc1e9ed255c481 commit
- git.kernel.org/stable/c/c348b0f8d035fc4bdc040796889beec7218bd1b8 commit
- git.kernel.org/stable/c/58bd38cbc961fd799842b7be8c5222310f04b908 commit
- git.kernel.org/stable/c/d05c2fdf8e10528bb6751bd95243e862d5402a9b commit
- git.kernel.org/stable/c/0a0f7f84148445c9f02f226928803a870139d820 commit
- git.kernel.org/stable/c/88cd232146207ff1d41dededed5e77c0d4438113 commit
- git.kernel.org/stable/c/bdc28a8fb43cc476e33b11519235adb816ce00e8 commit
- git.kernel.org/stable/c/d8e1bc6029acac796293310aacef7b7336f35b6a commit
- git.kernel.org/stable/c/0a375c822497ed6ad6b5da0792a12a6f1af10c0b commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2022-49372 updated cvss 5.5
kernel: tcp: tcp_rtx_synack() can be called from process context
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 moreaffected: no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 8 kernel-rt, kernel-rt-kvm, kernel-rt-core, kernel-rt-modules, kernel-rt-debug-kvm, kernel-rt-debug-core, +6 more Red Hat Enterprise Linux 9 kernel-rt, kernel-rt-kvm, kernel-rt-core, kernel-rt-modules, kernel-rt-debug-kvm, kernel-rt-debug-core, +12 moreaffected: no fix available
-
Red Hat Enterprise Linux AppStream (v. 9) perf 5.14.0-284.11.1.el9_2, rtla 5.14.0-284.11.1.el9_2, kernel-devel-matched 5.14.0-284.11.1.el9_2, kernel-64k-devel-matched 5.14.0-284.11.1.el9_2, kernel-debug-devel-matched 5.14.0-284.11.1.el9_2, kernel-debuginfo-common-s390x 5.14.0-284.11.1.el9_2, +5 morefixed: vendor fix RHSA-2023:2458
-
Red Hat Enterprise Linux BaseOS (v. 8) perf 4.18.0-477.10.1.el8_8, kernel 4.18.0-477.10.1.el8_8, bpftool 4.18.0-477.10.1.el8_8, kernel-core 4.18.0-477.10.1.el8_8, kernel-tools 4.18.0-477.10.1.el8_8, python3-perf 4.18.0-477.10.1.el8_8, +15 morefixed: vendor fix RHSA-2023:2951
-
Red Hat Enterprise Linux BaseOS (v. 9) bpftool 7.0.0-284.11.1.el9_2, kernel 5.14.0-284.11.1.el9_2, kernel-64k 5.14.0-284.11.1.el9_2, kernel-core 5.14.0-284.11.1.el9_2, kernel-tools 5.14.0-284.11.1.el9_2, python3-perf 5.14.0-284.11.1.el9_2, +28 morefixed: vendor fix RHSA-2023:2458
-
Red Hat Enterprise Linux CRB (v. 8) kernel-debuginfo-common-x86_64 4.18.0-477.10.1.el8_8, kernel-debuginfo-common-aarch64 4.18.0-477.10.1.el8_8, kernel-debuginfo-common-ppc64le 4.18.0-477.10.1.el8_8fixed: vendor fix RHSA-2023:2951
-
Red Hat Enterprise Linux CRB (v. 9) kernel-debuginfo-common-s390x 5.14.0-284.11.1.el9_2, kernel-debuginfo-common-x86_64 5.14.0-284.11.1.el9_2, kernel-debuginfo-common-aarch64 5.14.0-284.11.1.el9_2, kernel-debuginfo-common-ppc64le 5.14.0-284.11.1.el9_2fixed: vendor fix RHSA-2023:2458
-
Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.29% chance of exploitation in the next 30 days, higher than 21% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
-
git.kernel.org
/stable/c/3db889f883e65bbd3b1401279bfc1e9ed255c481
patch
-
git.kernel.org
/stable/c/c348b0f8d035fc4bdc040796889beec7218bd1b8
patch
-
git.kernel.org
/stable/c/58bd38cbc961fd799842b7be8c5222310f04b908
patch
-
git.kernel.org
/stable/c/d05c2fdf8e10528bb6751bd95243e862d5402a9b
patch
-
git.kernel.org
/stable/c/0a0f7f84148445c9f02f226928803a870139d820
patch
-
git.kernel.org
/stable/c/88cd232146207ff1d41dededed5e77c0d4438113
patch
-
git.kernel.org
/stable/c/bdc28a8fb43cc476e33b11519235adb816ce00e8
patch
-
git.kernel.org
/stable/c/d8e1bc6029acac796293310aacef7b7336f35b6a
patch
-
git.kernel.org
/stable/c/0a375c822497ed6ad6b5da0792a12a6f1af10c0b
patch
Sources
- CVE List CVE-2022-49372
- NVD CVE-2022-49372
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.