| CVE-2022-22659 |
A logic issue was addressed with improved state management
|
Non notée
|
18 mars 2022 |
| CVE-2022-22667 |
A use after free issue was addressed with improved memory management
|
Non notée
|
18 mars 2022 |
| CVE-2022-22671 |
An authentication issue was addressed with improved state management
|
Non notée
|
18 mars 2022 |
| CVE-2022-22666 |
A memory corruption issue was addressed with improved validation
|
Non notée
|
18 mars 2022 |
| CVE-2022-22653 |
A logic issue was addressed with improved restrictions
|
Non notée
|
18 mars 2022 |
| CVE-2022-22642 |
This issue was addressed with improved checks
|
Non notée
|
18 mars 2022 |
| CVE-2022-22652 |
The GSMA authentication panel could be presented on the lock screen
|
Non notée
|
18 mars 2022 |
| CVE-2022-22638 |
A null pointer dereference was addressed with improved validation
|
Non notée
|
18 mars 2022 |
| CVE-2022-22640 |
A memory corruption issue was addressed with improved validation
|
Non notée
|
18 mars 2022 |
| CVE-2022-22641 |
A use after free issue was addressed with improved memory management
|
Non notée
|
18 mars 2022 |
| CVE-2022-22635 |
An out-of-bounds write issue was addressed with improved bounds checking
|
Non notée
|
18 mars 2022 |
| CVE-2022-22633 |
A memory corruption issue was addressed with improved state management
|
Non notée
|
18 mars 2022 |
| CVE-2022-22639 |
A logic issue was addressed with improved state management
|
Non notée
|
18 mars 2022 |
| CVE-2022-22636 |
An out-of-bounds write issue was addressed with improved bounds checking
|
Non notée
|
18 mars 2022 |
| CVE-2022-22632 |
A logic issue was addressed with improved state management
|
Non notée
|
18 mars 2022 |
| CVE-2022-22634 |
A buffer overflow was addressed with improved bounds checking
|
Non notée
|
18 mars 2022 |
| CVE-2022-22621 |
This issue was addressed with improved checks
|
Non notée
|
18 mars 2022 |
| CVE-2022-22622 |
This issue was addressed with improved checks
|
Non notée
|
18 mars 2022 |
| CVE-2022-22618 |
This issue was addressed with improved checks
|
Non notée
|
18 mars 2022 |
| CVE-2022-22612 |
A memory consumption issue was addressed with improved memory handling
|
Non notée
|
18 mars 2022 |
| CVE-2022-22614 |
A use after free issue was addressed with improved memory management
|
Non notée
|
18 mars 2022 |
| CVE-2022-22609 |
The issue was addressed with additional permissions checks
|
Non notée
|
18 mars 2022 |
| CVE-2022-22615 |
A use after free issue was addressed with improved memory management
|
Non notée
|
18 mars 2022 |
| CVE-2022-22613 |
An out-of-bounds write issue was addressed with improved bounds checking
|
Non notée
|
18 mars 2022 |
| CVE-2022-22611 |
An out-of-bounds read was addressed with improved input validation
|
Non notée
|
18 mars 2022 |