|
CVE-2023-42832
|
2024-01-10 |
|
A race condition was addressed with improved... |
|
198
|
|
CVE-2023-42833
|
2024-01-10 |
|
A correctness issue was addressed with... |
|
222
|
|
CVE-2023-42862
|
2024-01-10 |
|
An out-of-bounds read was addressed with... |
|
215
|
|
CVE-2023-42865
|
2024-01-10 |
|
An out-of-bounds read was addressed with... |
|
219
|
|
CVE-2023-42866
|
2024-01-10 |
|
The issue was addressed with improved memory... |
|
204
|
|
CVE-2023-42869
|
2024-01-10 |
|
Multiple memory corruption issues were... |
|
205
|
|
CVE-2023-42870
|
2024-01-10 |
|
A use-after-free issue was addressed with... |
|
220
|
|
CVE-2023-42871
|
2024-01-10 |
|
The issue was addressed with improved memory... |
|
215
|
|
CVE-2023-42872
|
2024-01-10 |
|
The issue was addressed with additional... |
|
209
|
|
CVE-2023-42876
|
2024-01-10 |
|
The issue was addressed with improved bounds... |
|
192
|
