Executive Summary
Informations | |||
---|---|---|---|
Name | CVE-2024-56694 | First vendor Publication | 2024-12-28 |
Vendor | Cve | Last vendor Modification | 2025-06-19 |
Security-Database Scoring CVSS v3
Cvss vector : CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H | |||
---|---|---|---|
Overall CVSS Score | 5.5 | ||
Base Score | 5.5 | Environmental Score | 5.5 |
impact SubScore | 3.6 | Temporal Score | 5.5 |
Exploitabality Sub Score | 1.8 | ||
Attack Vector | Local | Attack Complexity | Low |
Privileges Required | Low | User Interaction | None |
Scope | Unchanged | Confidentiality Impact | None |
Integrity Impact | None | Availability Impact | High |
Calculate full CVSS 3.0 Vectors scores |
Security-Database Scoring CVSS v2
Cvss vector : | |||
---|---|---|---|
Cvss Base Score | N/A | Attack Range | N/A |
Cvss Impact Score | N/A | Attack Complexity | N/A |
Cvss Expoit Score | N/A | Authentication | N/A |
Calculate full CVSS 2.0 Vectors scores |
Detail
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 ''' This topic has been discussed before, but it has not been fixed. Previous discussion: https://lore.kernel.org/all/6684a5864ec86_403d20898@john.notmuch |
Original Source
Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-56694 |
CWE : Common Weakness Enumeration
% | Id | Name |
---|---|---|
100 % | CWE-667 | Insufficient Locking |
CPE : Common Platform Enumeration
Sources (Detail)
Alert History
Date | Informations |
---|---|
2025-06-25 21:20:50 |
|
2025-06-25 12:36:36 |
|
2025-06-24 02:43:10 |
|
2025-06-19 17:21:07 |
|
2025-05-27 02:48:35 |
|
2025-03-29 03:44:29 |
|
2025-03-28 13:47:45 |
|
2025-03-28 03:22:18 |
|
2025-03-19 03:17:06 |
|
2025-03-18 03:30:06 |
|
2025-03-14 03:17:13 |
|
2025-03-06 14:13:46 |
|
2025-02-22 03:27:18 |
|
2025-01-09 21:20:33 |
|
2025-01-08 21:20:36 |
|
2024-12-28 13:20:29 |
|