Vulnerability · Published May 21, 2024 · Assigned by Linux

CVE-2021-47304tcp: fix tcp_init_transfer() to not reset icsk_ca_initialized

Medium 5.5

In plain English

A medium-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 15% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS NVD)5.5Medium
Exploit odds (30 days)0.2%top 85.4% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: tcp: fix tcp_init_transfer() to not reset icsk_ca_initialized This commit fixes a bug (found by syzkaller) that could cause spurious double-initializations for congestion control modules, which could cause memory leaks or other problems for congestion control modules (like CDG) that allocate memory in their init functions. The buggy scenario constructed by syzkaller was something like: (1) create a TCP socket (2) initiate a TFO connect via sendto() (3) while socket is in TCP_SYN_SENT, call setsockopt(TCP_CONGESTION), which calls: tcp_set_congestion_control() -> tcp_reinit_congestion_control() -> tcp_init_congestion_control() (4) receive ACK, connection is established, call tcp_init_transfer(), set icsk_ca_initialized=0 (without first calling cc->release()), call tcp_init_congestion_control() again. Note that in this sequence tcp_init_congestion_control() is called twice without a cc->release() call in between. Thus, for CC modules that allocate memory in their init() function, e.g, CDG, a memory leak may occur. The syzkaller tool managed to find a reproducer that triggered such a leak in CDG. The bug was introduced when that commit 8919a9b31eb4 ("tcp: Only init congestion control if not initialized already") introduced icsk_ca_initialized and set icsk_ca_initialized to 0 in tcp_init_transfer(), missing the possibility for a sequence like the one above, where a process could call setsockopt(TCP_CONGESTION) in state TCP_SYN_SENT (i.e. after the connect() or TFO open sendmsg()), which would call tcp_init_congestion_control(). It did not intend to reset any initialization that the user had already explicitly made; it just missed the possibility of that particular sequence (which syzkaller managed to find).

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
AlmaLinux:8bpftool4.18.0-553.16.1.el8_10ALSA-2024:5101
AlmaLinux:8kernel4.18.0-553.16.1.el8_10ALSA-2024:5101
AlmaLinux:8kernel-abi-stablelists4.18.0-553.16.1.el8_10ALSA-2024:5101
AlmaLinux:8kernel-core4.18.0-553.16.1.el8_10ALSA-2024:5101
AlmaLinux:8kernel-cross-headers4.18.0-553.16.1.el8_10ALSA-2024:5101
AlmaLinux:8kernel-debug4.18.0-553.16.1.el8_10ALSA-2024:5101
AlmaLinux:8kernel-debug-core4.18.0-553.16.1.el8_10ALSA-2024:5101
AlmaLinux:8kernel-debug-devel4.18.0-553.16.1.el8_10ALSA-2024:5101
AlmaLinux:8kernel-debug-modules4.18.0-553.16.1.el8_10ALSA-2024:5101
AlmaLinux:8kernel-debug-modules-extra4.18.0-553.16.1.el8_10ALSA-2024:5101
AlmaLinux:8kernel-devel4.18.0-553.16.1.el8_10ALSA-2024:5101
AlmaLinux:8kernel-doc4.18.0-553.16.1.el8_10ALSA-2024:5101
AlmaLinux:8kernel-headers4.18.0-553.16.1.el8_10ALSA-2024:5101
AlmaLinux:8kernel-modules4.18.0-553.16.1.el8_10ALSA-2024:5101
AlmaLinux:8kernel-modules-extra4.18.0-553.16.1.el8_10ALSA-2024:5101
AlmaLinux:8kernel-rt4.18.0-553.16.1.rt7.357.el8_10ALSA-2024:5102
AlmaLinux:8kernel-rt-core4.18.0-553.16.1.rt7.357.el8_10ALSA-2024:5102
AlmaLinux:8kernel-rt-debug4.18.0-553.16.1.rt7.357.el8_10ALSA-2024:5102
AlmaLinux:8kernel-rt-debug-core4.18.0-553.16.1.rt7.357.el8_10ALSA-2024:5102
AlmaLinux:8kernel-rt-debug-devel4.18.0-553.16.1.rt7.357.el8_10ALSA-2024:5102
AlmaLinux:8kernel-rt-debug-kvm4.18.0-553.16.1.rt7.357.el8_10ALSA-2024:5102
AlmaLinux:8kernel-rt-debug-modules4.18.0-553.16.1.rt7.357.el8_10ALSA-2024:5102
AlmaLinux:8kernel-rt-debug-modules-extra4.18.0-553.16.1.rt7.357.el8_10ALSA-2024:5102
AlmaLinux:8kernel-rt-devel4.18.0-553.16.1.rt7.357.el8_10ALSA-2024:5102
AlmaLinux:8kernel-rt-kvm4.18.0-553.16.1.rt7.357.el8_10ALSA-2024:5102
AlmaLinux:8kernel-rt-modules4.18.0-553.16.1.rt7.357.el8_10ALSA-2024:5102
AlmaLinux:8kernel-rt-modules-extra4.18.0-553.16.1.rt7.357.el8_10ALSA-2024:5102
AlmaLinux:8kernel-tools4.18.0-553.16.1.el8_10ALSA-2024:5101
AlmaLinux:8kernel-tools-libs4.18.0-553.16.1.el8_10ALSA-2024:5101
AlmaLinux:8kernel-tools-libs-devel4.18.0-553.16.1.el8_10ALSA-2024:5101
AlmaLinux:8kernel-zfcpdump4.18.0-553.16.1.el8_10ALSA-2024:5101
AlmaLinux:8kernel-zfcpdump-core4.18.0-553.16.1.el8_10ALSA-2024:5101
AlmaLinux:8kernel-zfcpdump-devel4.18.0-553.16.1.el8_10ALSA-2024:5101
AlmaLinux:8kernel-zfcpdump-modules4.18.0-553.16.1.el8_10ALSA-2024:5101
AlmaLinux:8kernel-zfcpdump-modules-extra4.18.0-553.16.1.el8_10ALSA-2024:5101
AlmaLinux:8perf4.18.0-553.16.1.el8_10ALSA-2024:5101
AlmaLinux:8python3-perf4.18.0-553.16.1.el8_10ALSA-2024:5101
Debian:12linux5.14.6-1DEBIAN-CVE-2021-47304
Debian:13linux5.14.6-1DEBIAN-CVE-2021-47304
Debian:14linux5.14.6-1DEBIAN-CVE-2021-47304
Rocky Linux:8kernel0:4.18.0-553.16.1.el8_10RLSA-2024:5101
Rocky Linux:8kernel0:4.18.0-553.16.1.el8_10.cloud.0.1RXSA-2024:5101
Rocky Linux:8kernel-rt0:4.18.0-553.16.1.rt7.357.el8_10RLSA-2024:5102
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2021-47304
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2021-47304
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2021-47304
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2021-47304
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2021-47304
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2021-47304
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2021-47304
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2021-47304
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2021-47304
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2021-47304
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2021-47304
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2021-47304
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2021-47304
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2021-47304
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2021-47304
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2021-47304
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2021-47304
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2021-47304
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2021-47304
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2021-47304
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2021-47304

Affected products (as reported)

VendorProductVersions
Linux Linux 8919a9b31eb4fb4c0a93e5fb350a626924302aa6 – before ad4ba3404931745a5977ad12db4f0c34080e52f78919a9b31eb4fb4c0a93e5fb350a626924302aa6 – before fe77b85828ca9ddc42977b79de9e40d18545b4fe8919a9b31eb4fb4c0a93e5fb350a626924302aa6 – before be5d1b61a2ad28c7e57fe8bfa277373e8ecffcdc
Linux Linux 5.10

References