Executive Summary
Informations | |||
---|---|---|---|
Name | CVE-2024-44946 | First vendor Publication | 2024-08-31 |
Vendor | Cve | Last vendor Modification | 2024-09-04 |
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: kcm: Serialise kcm_sendmsg() for the same socket. syzkaller reported UAF in kcm_release(). [0] The scenario is 1. Thread A builds a skb with MSG_MORE and sets kcm->seq_skb. 2. Thread A resumes building skb from kcm->seq_skb but is blocked 3. Thread B calls sendmsg() concurrently, finishes building kcm->seq_skb 4. Thread A faces an error and finally frees skb that is already in the 5. kcm_release() does double-free the skb in the write queue When a thread is building a MSG_MORE skb, another thread must not touch it. Let's add a per-sk mutex and serialise kcm_sendmsg(). [0]: BUG: KASAN: slab-use-after-free in __skb_unlink include/linux/skbuff.h:2366 [inline] BUG: KASAN: slab-use-after-free in __skb_dequeue include/linux/skbuff.h:2385 [inline] BUG: KASAN: slab-use-after-free in __skb_queue_purge_reason include/linux/skbuff.h:3175 [inline] BUG: KASAN: slab-use-after-free in __skb_queue_purge include/linux/skbuff.h:3181 [inline] BUG: KASAN: slab-use-after-free in kcm_release+0x170/0x4c8 net/kcm/kcmsock.c:1691 Read of size 8 at addr ffff0000ced0fc80 by task syz-executor329/6167 CPU: 1 PID: 6167 Comm: syz-executor329 Tainted: G B 6.8.0-rc5-syzkaller-g9abbc24128bc #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024 Call trace: Allocated by task 6166: |
Original Source
Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-44946 |
CWE : Common Weakness Enumeration
% | Id | Name |
---|---|---|
100 % | CWE-416 | Use After Free |
CPE : Common Platform Enumeration
Sources (Detail)
Alert History
Date | Informations |
---|---|
2025-03-29 03:39:55 |
|
2025-03-28 13:44:27 |
|
2025-03-28 03:18:07 |
|
2025-03-19 03:13:29 |
|
2025-03-18 03:26:25 |
|
2025-03-14 03:13:42 |
|
2025-03-06 14:10:14 |
|
2025-02-22 03:23:47 |
|
2025-01-08 03:04:50 |
|
2025-01-07 03:04:22 |
|
2024-12-25 03:03:00 |
|
2024-12-12 03:05:57 |
|
2024-11-23 03:02:58 |
|
2024-11-22 03:01:09 |
|
2024-11-20 02:59:29 |
|
2024-11-14 02:59:47 |
|
2024-11-09 02:59:47 |
|
2024-10-26 02:57:10 |
|
2024-10-25 02:59:03 |
|
2024-10-23 02:58:15 |
|
2024-10-03 02:53:31 |
|
2024-10-02 02:51:54 |
|
2024-09-15 02:49:30 |
|
2024-09-12 00:27:33 |
|
2024-09-06 21:27:49 |
|
2024-09-06 00:27:32 |
|
2024-09-04 17:27:23 |
|
2024-09-03 17:27:27 |
|
2024-08-31 21:27:25 |
|