Security Resilience

CVE-2024-35910

Linux Kernel 4.2 – 4.19.312

Published
19 May 2024
Modified
15 October 2026
Patch / advisory
CVSS Score v3.1 7.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0026 18th percentile
Risk Priority 56 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS scores by FIRST (EPSS SIG), generated by Empirical Security. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2024-35910 is a high-severity an unspecified weakness vulnerability in Linux Kernel. Its CVSS base score is 7.8 (High).

Operationally, ranked at the 18th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability Data

In the Linux kernel, the following vulnerability has been resolved: tcp: properly terminate timers for kernel sockets We had various syzbot reports about tcp timers firing after the corresponding netns has been dismantled. Fortunately Josef Bacik could trigger the issue…

more

more often, and could test a patch I wrote two years ago. When TCP sockets are closed, we call inet_csk_clear_xmit_timers() to 'stop' the timers. inet_csk_clear_xmit_timers() can be called from any context, including when socket lock is held. This is the reason it uses sk_stop_timer(), aka del_timer(). This means that ongoing timers might finish much later. For user sockets, this is fine because each running timer holds a reference on the socket, and the user socket holds a reference on the netns. For kernel sockets, we risk that the netns is freed before timer can complete, because kernel sockets do not hold reference on the netns. This patch adds inet_csk_clear_xmit_timers_sync() function that using sk_stop_timer_sync() to make sure all timers are terminated before the kernel socket is released. Modules using kernel sockets close them in their netns exit() handler. Also add sock_not_owned_by_me() helper to get LOCKDEP support : inet_csk_clear_xmit_timers_sync() must not be called while socket lock is held. It is very possible we can revert in the future commit 3a58f13a881e ("net: rds: acquire refcount on TCP sockets") which attempted to solve the issue in rds only. (net/smc/af_smc.c and net/mptcp/subflow.c have similar code) We probably can remove the check_net() tests from tcp_out_of_resources() and __tcp_close() in the future.

CWE(s)

Related Threats

CVEs Like This One

CVE-2024-44974Same product: Debian Debian Linux
CVE-2024-35835Same product: Debian Debian Linux
CVE-2024-26698Same product: Debian Debian Linux
CVE-2024-49883Same product: Debian Debian Linux
CVE-2024-27413Same product: Debian Debian Linux
CVE-2024-26702Same product: Debian Debian Linux
CVE-2023-52670Same product: Debian Debian Linux
CVE-2024-42302Same product: Debian Debian Linux
CVE-2024-26861Same product: Debian Debian Linux
CVE-2024-36971Same product: Debian Debian Linux

Affected Assets

linux
linux kernel
6.9 · 4.2 — 4.19.312 · 4.20 — 5.4.274 · 5.5 — 5.10.215
debian
debian linux
10.0

Mitigating Controls

No mitigating controls mapped yet. The per-CVE control annotator has not reached this CVE.

References