Executive Summary
Informations | |||
---|---|---|---|
Name | CVE-2022-48913 | First vendor Publication | 2024-08-22 |
Vendor | Cve | Last vendor Modification | 2024-08-27 |
Security-Database Scoring CVSS v3
Cvss vector : CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | |||
---|---|---|---|
Overall CVSS Score | 7.8 | ||
Base Score | 7.8 | Environmental Score | 7.8 |
impact SubScore | 5.9 | Temporal Score | 7.8 |
Exploitabality Sub Score | 1.8 | ||
Attack Vector | Local | Attack Complexity | Low |
Privileges Required | Low | User Interaction | None |
Scope | Unchanged | Confidentiality Impact | High |
Integrity Impact | High | 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: blktrace: fix use after free for struct blk_trace When tracing the whole disk, 'dropped' and 'msg' will be created under 'q->debugfs_dir' and 'bt->dir' is NULL, thus blk_trace_free() won't remove those files. What's worse, the following UAF can be triggered because of accessing stale 'dropped' and 'msg': ================================================================== BUG: KASAN: use-after-free in blk_dropped_read+0x89/0x100 Read of size 4 at addr ffff88816912f3d8 by task blktrace/1188 CPU: 27 PID: 1188 Comm: blktrace Not tainted 5.17.0-rc4-next-20220217+ #469 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS ?-20190727_073836-4 Call Trace: Allocated by task 1050: Freed by task 1050: The buggy address belongs to the object at ffff88816912f380 Memory state around the buggy address: |
Original Source
Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-48913 |
CWE : Common Weakness Enumeration
% | Id | Name |
---|---|---|
100 % | CWE-416 | Use After Free |
CPE : Common Platform Enumeration
Sources (Detail)
Alert History
Date | Informations |
---|---|
2025-01-08 02:47:29 |
|
2025-01-07 02:47:05 |
|
2024-12-25 02:45:52 |
|
2024-12-12 02:48:46 |
|
2024-11-22 02:46:11 |
|
2024-11-20 02:43:34 |
|
2024-11-14 02:43:27 |
|
2024-11-09 02:44:06 |
|
2024-10-26 02:41:51 |
|
2024-10-25 02:43:37 |
|
2024-10-23 02:43:01 |
|
2024-10-03 02:39:05 |
|
2024-10-02 02:37:28 |
|
2024-09-03 21:27:42 |
|
2024-08-27 21:27:52 |
|
2024-08-23 02:48:13 |
|
2024-08-23 02:34:45 |
|
2024-08-22 17:27:25 |
|
2024-08-22 09:27:26 |
|