Executive Summary
Informations | |||
---|---|---|---|
Name | CVE-2023-52827 | First vendor Publication | 2024-05-21 |
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:N/A:H | |||
---|---|---|---|
Overall CVSS Score | 7.1 | ||
Base Score | 7.1 | Environmental Score | 7.1 |
impact SubScore | 5.2 | Temporal Score | 7.1 |
Exploitabality Sub Score | 1.8 | ||
Attack Vector | Local | Attack Complexity | Low |
Privileges Required | Low | User Interaction | None |
Scope | Unchanged | Confidentiality Impact | High |
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: wifi: ath12k: fix possible out-of-bound read in ath12k_htt_pull_ppdu_stats() len is extracted from HTT message and could be an unexpected value in case errors happen, so add validation before using to avoid possible out-of-bound read in the following message iteration and parsing. The same issue also applies to ppdu_info->ppdu_stats.common.num_users, so validate it before using too. These are found during code review. Compile test only. |
Original Source
Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-52827 |
CWE : Common Weakness Enumeration
% | Id | Name |
---|---|---|
100 % | CWE-125 | Out-of-bounds Read |
CPE : Common Platform Enumeration
Sources (Detail)
Alert History
Date | Informations |
---|---|
2025-06-26 02:24:42 |
|
2025-06-25 12:27:39 |
|
2025-06-24 02:29:19 |
|
2025-05-27 13:39:22 |
|
2025-05-27 02:28:16 |
|
2025-03-29 03:30:32 |
|
2025-03-28 13:39:38 |
|
2025-03-28 03:10:34 |
|
2025-03-19 03:06:22 |
|
2025-03-18 03:18:51 |
|
2025-03-14 03:06:46 |
|
2025-02-22 03:16:38 |
|
2025-01-08 02:59:26 |
|
2025-01-07 02:59:02 |
|
2024-12-25 02:57:48 |
|
2024-12-12 03:00:52 |
|
2024-11-25 09:25:25 |
|
2024-11-21 21:23:50 |
|
2024-11-20 02:54:59 |
|
2024-11-14 02:55:08 |
|
2024-11-09 02:55:23 |
|
2024-10-26 02:52:48 |
|
2024-10-25 02:54:45 |
|
2024-10-23 02:54:02 |
|
2024-10-03 02:49:39 |
|
2024-10-02 02:48:03 |
|
2024-09-15 02:46:04 |
|
2024-09-12 02:45:36 |
|
2024-09-04 02:47:11 |
|
2024-08-22 02:45:16 |
|
2024-08-02 13:54:16 |
|
2024-08-02 01:34:38 |
|
2024-05-24 09:27:28 |
|
2024-05-21 21:27:25 |
|