Executive Summary
Informations | |||
---|---|---|---|
Name | CVE-2024-42232 | First vendor Publication | 2024-08-07 |
Vendor | Cve | Last vendor Modification | 2024-08-08 |
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: libceph: fix race between delayed_work() and ceph_monc_stop() The way the delayed work is handled in ceph_monc_stop() is prone to races with mon_fault() and possibly also finish_hunting(). Both of these can requeue the delayed work which wouldn't be canceled by any of the following code in case that happens after cancel_delayed_work_sync() runs -- __close_session() doesn't mess with the delayed work in order to avoid interfering with the hunting interval logic. This part was missed in commit b5d91704f53e ("libceph: behave in mon_fault() if cur_mon < 0") and use-after-free can still ensue on monc and objects that hang off of it, with monc->auth and monc->monmap being particularly susceptible to quickly being reused. To fix this: - clear monc->cur_mon and monc->hunting as part of closing the session |
Original Source
Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-42232 |
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:02 |
|
2025-03-28 13:43:52 |
|
2025-03-28 03:17:25 |
|
2025-03-19 03:12:48 |
|
2025-03-18 03:25:43 |
|
2025-03-14 03:13:02 |
|
2025-03-06 14:09:34 |
|
2025-02-22 03:23:04 |
|
2025-01-08 03:04:12 |
|
2025-01-07 03:03:45 |
|
2024-12-25 03:02:23 |
|
2024-12-12 03:05:19 |
|
2024-11-23 03:02:23 |
|
2024-11-22 03:00:34 |
|
2024-11-20 02:58:55 |
|
2024-11-14 02:59:13 |
|
2024-11-09 02:59:14 |
|
2024-10-26 02:56:38 |
|
2024-10-25 02:58:33 |
|
2024-10-23 02:57:45 |
|
2024-10-03 02:53:03 |
|
2024-10-02 02:51:27 |
|
2024-09-15 02:49:10 |
|
2024-09-12 02:48:42 |
|
2024-09-07 02:47:41 |
|
2024-09-06 02:46:51 |
|
2024-09-04 02:50:03 |
|
2024-08-22 02:47:55 |
|
2024-08-08 21:27:45 |
|
2024-08-08 00:27:22 |
|
2024-08-07 21:27:25 |
|