Executive Summary
| Informations | |||
|---|---|---|---|
| Name | CVE-2024-46868 | First vendor Publication | 2024-09-27 |
| Vendor | Cve | Last vendor Modification | 2024-10-01 |
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: firmware: qcom: uefisecapp: Fix deadlock in qcuefi_acquire() If the __qcuefi pointer is not set, then in the original code, we would hold onto the lock. That means that if we tried to set it later, then it would cause a deadlock. Drop the lock on the error path. That's what all the callers are expecting. |
Original Source
| Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-46868 |
CWE : Common Weakness Enumeration
| % | Id | Name |
|---|---|---|
| 100 % | CWE-667 | Insufficient Locking |
CPE : Common Platform Enumeration
Sources (Detail)
| Source | Url |
|---|
Alert History
| Date | Informations |
|---|---|
| 2024-11-23 03:03:38 |
|
| 2024-11-22 03:01:48 |
|
| 2024-11-20 03:00:06 |
|
| 2024-11-14 03:00:25 |
|
| 2024-11-09 03:00:25 |
|
| 2024-10-26 02:57:47 |
|
| 2024-10-25 02:59:39 |
|
| 2024-10-23 02:58:52 |
|
| 2024-10-02 21:27:25 |
|
| 2024-10-02 02:52:46 |
|
| 2024-10-02 00:27:32 |
|
| 2024-09-30 17:27:26 |
|
| 2024-09-27 17:27:23 |
|
