| CVE-2024-40852 |
This issue was addressed by restricting options offered on a locked device
|
7.5
High
|
Sep 16, 2024 |
| CVE-2024-44169 |
The issue was addressed with improved memory handling
|
8.1
High
|
Sep 16, 2024 |
| CVE-2024-27874 |
This issue was addressed through improved state management
|
7.5
High
|
Sep 16, 2024 |
| CVE-2024-44167 |
This issue was addressed by removing the vulnerable code
|
8.1
High
|
Sep 16, 2024 |
| CVE-2024-44147 |
This issue was addressed through improved state management
|
7.7
High
|
Sep 16, 2024 |
| CVE-2024-27869 |
The issue was addressed with improved checks
|
7.5
High
|
Sep 16, 2024 |
| CVE-2023-42843 |
An inconsistent user interface issue was addressed with improved state management
|
7.5
High
|
Feb 21, 2024 |
| CVE-2023-40423 |
The issue was addressed with improved memory handling
|
Not rated
|
Oct 25, 2023 |
| CVE-2023-42845 |
An authentication issue was addressed with improved state management
|
Not rated
|
Oct 25, 2023 |
| CVE-2023-41984 |
The issue was addressed with improved memory handling
|
Not rated
|
Sep 26, 2023 |
| CVE-2023-32441 |
The issue was addressed with improved memory handling
|
Not rated
|
Jul 27, 2023 |