Executive Summary
Informations | |||
---|---|---|---|
Name | CVE-2024-38664 | First vendor Publication | 2024-06-24 |
Vendor | Cve | Last vendor Modification | 2025-05-30 |
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: drm: zynqmp_dpsub: Always register bridge We must always register the DRM bridge, since zynqmp_dp_hpd_work_func calls drm_bridge_hpd_notify, which in turn expects hpd_mutex to be initialized. We do this before zynqmp_dpsub_drm_init since that calls drm_bridge_attach. This fixes the following lockdep warning: [ 19.217084] ------------[ cut here ]------------ [ 19.227530] DEBUG_LOCKS_WARN_ON(lock->magic != lock) [ 19.227768] WARNING: CPU: 0 PID: 140 at kernel/locking/mutex.c:582 __mutex_lock+0x4bc/0x550 [ 19.241696] Modules linked in: [ 19.244937] CPU: 0 PID: 140 Comm: kworker/0:4 Not tainted 6.6.20+ #96 [ 19.252046] Hardware name: xlnx,zynqmp (DT) [ 19.256421] Workqueue: events zynqmp_dp_hpd_work_func [ 19.261795] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 19.269104] pc : __mutex_lock+0x4bc/0x550 [ 19.273364] lr : __mutex_lock+0x4bc/0x550 [ 19.277592] sp : ffffffc085c5bbe0 [ 19.281066] x29: ffffffc085c5bbe0 x28: 0000000000000000 x27: ffffff88009417f8 [ 19.288624] x26: ffffff8800941788 x25: ffffff8800020008 x24: ffffffc082aa3000 [ 19.296227] x23: ffffffc080d90e3c x22: 0000000000000002 x21: 0000000000000000 [ 19.303744] x20: 0000000000000000 x19: ffffff88002f5210 x18: 0000000000000000 [ 19.311295] x17: 6c707369642e3030 x16: 3030613464662072 x15: 0720072007200720 [ 19.318922] x14: 0000000000000000 x13: 284e4f5f4e524157 x12: 0000000000000001 [ 19.326442] x11: 0001ffc085c5b940 x10: 0001ff88003f388b x9 : 0001ff88003f3888 [ 19.334003] x8 : 0001ff88003f3888 x7 : 0000000000000000 x6 : 0000000000000000 [ 19.341537] x5 : 0000000000000000 x4 : 0000000000001668 x3 : 0000000000000000 [ 19.349054] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffffff88003f3880 [ 19.356581] Call trace: [ 19.359160] __mutex_lock+0x4bc/0x550 [ 19.363032] mutex_lock_nested+0x24/0x30 [ 19.367187] drm_bridge_hpd_notify+0x2c/0x6c [ 19.371698] zynqmp_dp_hpd_work_func+0x44/0x54 [ 19.376364] process_one_work+0x3ac/0x988 [ 19.380660] worker_thread+0x398/0x694 [ 19.384736] kthread+0x1bc/0x1c0 [ 19.388241] ret_from_fork+0x10/0x20 [ 19.392031] irq event stamp: 183 [ 19.395450] hardirqs last enabled at (183): [ (cherry picked from commit 61ba791c4a7a09a370c45b70a81b8c7d4cf6b2ae) |
Original Source
Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-38664 |
CWE : Common Weakness Enumeration
% | Id | Name |
---|---|---|
100 % | CWE-667 | Insufficient Locking |
CPE : Common Platform Enumeration
Sources (Detail)
Alert History
Date | Informations |
---|---|
2025-06-26 02:32:18 |
|
2025-06-25 12:31:44 |
|
2025-06-24 02:36:57 |
|
2025-05-31 00:20:47 |
|
2025-05-27 02:41:24 |
|
2025-03-29 03:37:41 |
|
2025-03-28 13:43:08 |
|
2025-03-28 03:16:20 |
|
2025-03-19 03:11:46 |
|
2025-03-18 03:24:38 |
|
2025-03-14 03:12:01 |
|
2025-03-06 14:08:24 |
|
2025-02-22 03:21:50 |
|
2025-01-08 03:03:16 |
|
2025-01-07 03:02:50 |
|
2024-12-25 03:01:28 |
|
2024-12-12 03:04:25 |
|
2024-11-25 09:24:29 |
|
2024-11-22 21:23:28 |
|
2024-11-21 21:23:05 |
|
2024-11-20 02:58:05 |
|
2024-11-14 02:58:23 |
|
2024-11-09 02:58:23 |
|
2024-10-26 02:55:48 |
|
2024-10-25 02:57:42 |
|
2024-10-23 02:56:56 |
|
2024-10-03 02:52:16 |
|
2024-10-02 02:50:40 |
|
2024-09-15 02:48:30 |
|
2024-09-12 02:48:04 |
|
2024-09-07 02:47:04 |
|
2024-09-06 02:46:16 |
|
2024-09-04 02:49:29 |
|
2024-08-22 02:47:30 |
|
2024-08-02 13:56:32 |
|
2024-08-02 01:35:45 |
|
2024-06-26 17:27:26 |
|
2024-06-25 00:27:27 |
|
2024-06-24 21:27:25 |
|