Executive Summary
Informations | |||
---|---|---|---|
Name | CVE-2024-42246 | First vendor Publication | 2024-08-07 |
Vendor | Cve | Last vendor Modification | 2024-09-12 |
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: net, sunrpc: Remap EPERM in case of connection failure in xs_tcp_setup_socket When using a BPF program on kernel_connect(), the call can return -EPERM. This causes xs_tcp_setup_socket() to loop forever, filling up the syslog and causing the kernel to potentially freeze up. Neil suggested: This will propagate -EPERM up into other layers which might not be ready ECONNREFUSED as error seems reasonable. For programs setting a different error can be out of reach (see handling in 4fbac77d2d09) in particular on kernels which do not have f10d05966196 ("bpf: Make BPF_PROG_RUN_ARRAY return -err instead of allow boolean"), thus given that it is better to simply remap for consistent behavior. UDP does handle EPERM in xs_udp_send_request(). |
Original Source
Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-42246 |
CPE : Common Platform Enumeration
Sources (Detail)
Alert History
Date | Informations |
---|---|
2025-03-29 03:39:04 |
|
2025-03-28 13:43:54 |
|
2025-03-28 03:17:28 |
|
2025-03-19 03:12:51 |
|
2025-03-18 03:25:46 |
|
2025-03-14 03:13:04 |
|
2025-03-06 14:09:36 |
|
2025-02-22 03:23:07 |
|
2025-01-08 03:04:14 |
|
2025-01-07 03:03:47 |
|
2024-12-25 03:02:25 |
|
2024-12-12 03:05:21 |
|
2024-11-23 03:02:25 |
|
2024-11-22 03:00:36 |
|
2024-11-20 02:58:57 |
|
2024-11-14 02:59:15 |
|
2024-11-09 02:59:16 |
|
2024-10-26 02:56:40 |
|
2024-10-25 02:58:34 |
|
2024-10-23 02:57:47 |
|
2024-10-03 02:53:05 |
|
2024-10-02 02:51:29 |
|
2024-09-14 21:30:05 |
|
2024-09-12 17:28:08 |
|
2024-09-12 02:48:44 |
|
2024-09-07 02:47:43 |
|
2024-09-06 02:46:53 |
|
2024-09-04 02:50:05 |
|
2024-08-22 02:47:57 |
|
2024-08-08 21:27:28 |
|
2024-08-08 00:27:22 |
|
2024-08-07 21:27:25 |
|