Executive Summary
| Informations | |||
|---|---|---|---|
| Name | CVE-2024-44996 | First vendor Publication | 2024-09-04 |
| Vendor | Cve | Last vendor Modification | 2024-09-16 |
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: vsock: fix recursive ->recvmsg calls After a vsock socket has been added to a BPF sockmap, its prot->recvmsg has been replaced with vsock_bpf_recvmsg(). Thus the following recursiion could happen: vsock_bpf_recvmsg() We need to fix it by calling the original ->recvmsg() without any BPF sockmap logic in __vsock_recvmsg(). |
Original Source
| Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-44996 |
CWE : Common Weakness Enumeration
| % | Id | Name |
|---|---|---|
| 100 % | CWE-674 | Uncontrolled Recursion |
CPE : Common Platform Enumeration
Sources (Detail)
Alert History
| Date | Informations |
|---|---|
| 2025-01-08 03:04:57 |
|
| 2025-01-07 03:04:30 |
|
| 2024-12-25 03:03:08 |
|
| 2024-12-12 03:06:04 |
|
| 2024-11-23 03:03:05 |
|
| 2024-11-22 03:01:15 |
|
| 2024-11-20 02:59:35 |
|
| 2024-11-14 02:59:54 |
|
| 2024-11-09 02:59:54 |
|
| 2024-10-26 02:57:17 |
|
| 2024-10-25 02:59:10 |
|
| 2024-10-23 02:58:21 |
|
| 2024-10-03 02:53:33 |
|
| 2024-10-02 02:51:57 |
|
| 2024-09-16 17:27:33 |
|
| 2024-09-05 17:27:24 |
|
| 2024-09-05 00:27:25 |
|
