Executive Summary
Informations | |||
---|---|---|---|
Name | CVE-2022-48787 | First vendor Publication | 2024-07-16 |
Vendor | Cve | Last vendor Modification | 2024-11-21 |
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: iwlwifi: fix use-after-free If no firmware was present at all (or, presumably, all of the firmware files failed to parse), we end up unbinding by calling device_release_driver(), which calls remove(), which then in iwlwifi calls iwl_drv_stop(), freeing the 'drv' struct. However the new code I added will still erroneously access it after it was freed. Set 'failure=false' in this case to avoid the access, all data was already freed anyway. |
Original Source
Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-48787 |
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:15 |
|
2025-01-07 02:46:52 |
|
2024-12-25 02:45:39 |
|
2024-12-12 02:48:31 |
|
2024-11-25 09:23:51 |
|
2024-11-21 21:22:33 |
|
2024-11-20 02:43:22 |
|
2024-11-14 02:43:14 |
|
2024-11-09 02:43:53 |
|
2024-10-26 02:41:39 |
|
2024-10-25 02:43:24 |
|
2024-10-23 02:42:48 |
|
2024-10-03 02:38:52 |
|
2024-10-02 02:37:15 |
|
2024-09-04 02:36:38 |
|
2024-08-22 02:35:00 |
|
2024-08-08 00:27:57 |
|
2024-07-16 17:27:24 |
|