CVE-2024-56694
Linux Kernel BPF Recursive Lock Deadlock in Stream Verdict Program
Description
In the Linux kernel, the following vulnerability has been resolved: bpf: fix recursive lock when verdict program return SK_PASS When the stream_verdict program returns SK_PASS, it places the received skb into its own receive queue, but a recursive lock eventually occurs, leading to an operating system deadlock. This issue has been present since v6.9. ''' sk_psock_strp_data_ready write_lock_bh(&sk->sk_callback_lock) strp_data_ready strp_read_sock read_sock -> tcp_read_sock strp_recv cb.rcv_msg -> sk_psock_strp_read # now stream_verdict return SK_PASS without peer sock assign __SK_PASS = sk_psock_map_verd(SK_PASS, NULL) sk_psock_verdict_apply sk_psock_skb_ingress_self sk_psock_skb_ingress_enqueue sk_psock_data_ready read_lock_bh(&sk->sk_callback_lock) <= dead lock ''' This topic has been discussed before, but it has not been fixed. Previous discussion: https://lore.kernel.org/all/[email protected]
INFO
Published Date :
Dec. 28, 2024, 10:15 a.m.
Last Modified :
Jan. 9, 2025, 4:16 p.m.
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Remotely Exploitable :
No
Impact Score :
3.6
Exploitability Score :
1.8
Public PoC/Exploit Available at Github
CVE-2024-56694 has a 1 public PoC/Exploit available at Github.
Go to the Public Exploits tab to see the list.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2024-56694.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
None
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2024-56694 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2024-56694 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jan. 09, 2025
Action Type Old Value New Value Added Reference https://git.kernel.org/stable/c/078f7e1521442a55db4bed812a2fbaf02ac33819 Added Reference https://git.kernel.org/stable/c/221109ba2127eabd0aa64718543638b58b15df56 -
Initial Analysis by [email protected]
Jan. 08, 2025
Action Type Old Value New Value Added CVSS V3.1 NIST AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Added CWE NIST CWE-667 Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.10.223 up to (excluding) 5.11 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.15.159 up to (excluding) 5.15.174 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.1.91 up to (excluding) 6.1.120 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.6.31 up to (excluding) 6.6.64 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.8.10 up to (excluding) 6.11.11 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.12 up to (excluding) 6.12.2 Changed Reference Type https://git.kernel.org/stable/c/01f1b88acfd79103da0610b45471f6c88ea98d72 No Types Assigned https://git.kernel.org/stable/c/01f1b88acfd79103da0610b45471f6c88ea98d72 Patch Changed Reference Type https://git.kernel.org/stable/c/386efa339e08563dd33e83bc951aea5d407fe578 No Types Assigned https://git.kernel.org/stable/c/386efa339e08563dd33e83bc951aea5d407fe578 Patch Changed Reference Type https://git.kernel.org/stable/c/6694f7acd625ed854bf6342926e771d65dad7f69 No Types Assigned https://git.kernel.org/stable/c/6694f7acd625ed854bf6342926e771d65dad7f69 Patch Changed Reference Type https://git.kernel.org/stable/c/8ca2a1eeadf09862190b2810697702d803ceef2d No Types Assigned https://git.kernel.org/stable/c/8ca2a1eeadf09862190b2810697702d803ceef2d Patch Changed Reference Type https://git.kernel.org/stable/c/da2bc8a0c8f3ac66fdf980fc59936f851a083561 No Types Assigned https://git.kernel.org/stable/c/da2bc8a0c8f3ac66fdf980fc59936f851a083561 Patch Changed Reference Type https://git.kernel.org/stable/c/f84c5ef6ca23cc2f72f3b830d74f67944684bb05 No Types Assigned https://git.kernel.org/stable/c/f84c5ef6ca23cc2f72f3b830d74f67944684bb05 Patch -
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Dec. 28, 2024
Action Type Old Value New Value Added Description In the Linux kernel, the following vulnerability has been resolved: bpf: fix recursive lock when verdict program return SK_PASS When the stream_verdict program returns SK_PASS, it places the received skb into its own receive queue, but a recursive lock eventually occurs, leading to an operating system deadlock. This issue has been present since v6.9. ''' sk_psock_strp_data_ready write_lock_bh(&sk->sk_callback_lock) strp_data_ready strp_read_sock read_sock -> tcp_read_sock strp_recv cb.rcv_msg -> sk_psock_strp_read # now stream_verdict return SK_PASS without peer sock assign __SK_PASS = sk_psock_map_verd(SK_PASS, NULL) sk_psock_verdict_apply sk_psock_skb_ingress_self sk_psock_skb_ingress_enqueue sk_psock_data_ready read_lock_bh(&sk->sk_callback_lock) <= dead lock ''' This topic has been discussed before, but it has not been fixed. Previous discussion: https://lore.kernel.org/all/[email protected] Added Reference https://git.kernel.org/stable/c/01f1b88acfd79103da0610b45471f6c88ea98d72 Added Reference https://git.kernel.org/stable/c/386efa339e08563dd33e83bc951aea5d407fe578 Added Reference https://git.kernel.org/stable/c/6694f7acd625ed854bf6342926e771d65dad7f69 Added Reference https://git.kernel.org/stable/c/8ca2a1eeadf09862190b2810697702d803ceef2d Added Reference https://git.kernel.org/stable/c/da2bc8a0c8f3ac66fdf980fc59936f851a083561 Added Reference https://git.kernel.org/stable/c/f84c5ef6ca23cc2f72f3b830d74f67944684bb05
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2024-56694 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2024-56694
weaknesses.