| CVE-2025-31185 |
A logic issue was addressed with improved checks
|
3.3
Low
|
May 19, 2025 |
| CVE-2025-24223 |
The issue was addressed with improved memory handling
|
8.0
High
|
May 12, 2025 |
| CVE-2025-31241 |
A double free issue was addressed with improved memory management
|
5.3
Medium
|
May 12, 2025 |
| CVE-2025-31257 |
This issue was addressed with improved memory handling
|
4.7
Medium
|
May 12, 2025 |
| CVE-2025-31217 |
The issue was addressed with improved input validation
|
6.5
Medium
|
May 12, 2025 |
| CVE-2025-24111 |
A memory corruption issue was addressed with improved state management
|
5.5
Medium
|
May 12, 2025 |
| CVE-2025-31221 |
An integer overflow was addressed with improved input validation
|
7.5
High
|
May 12, 2025 |
| CVE-2025-31210 |
The issue was addressed with improved UI
|
6.5
Medium
|
May 12, 2025 |
| CVE-2025-31206 |
A type confusion issue was addressed with improved state handling
|
4.3
Medium
|
May 12, 2025 |
| CVE-2025-31251 |
The issue was addressed with improved input sanitization
|
5.5
Medium
|
May 12, 2025 |
| CVE-2025-31226 |
A logic issue was addressed with improved checks
|
5.5
Medium
|
May 12, 2025 |
| CVE-2025-24225 |
An injection issue was addressed with improved input validation
|
6.5
Medium
|
May 12, 2025 |
| CVE-2025-31227 |
A logic issue was addressed with improved checks
|
4.6
Medium
|
May 12, 2025 |
| CVE-2025-31196 |
An out-of-bounds read was addressed with improved input validation
|
5.5
Medium
|
May 12, 2025 |
| CVE-2025-30436 |
This issue was addressed by restricting options offered on a locked device
|
9.1
Critical
|
May 12, 2025 |
| CVE-2025-31207 |
A logic issue was addressed with improved checks
|
7.7
High
|
May 12, 2025 |
| CVE-2025-31253 |
This issue was addressed through improved state management
|
7.1
High
|
May 12, 2025 |
| CVE-2025-31204 |
The issue was addressed with improved memory handling
|
8.8
High
|
May 12, 2025 |
| CVE-2025-31212 |
This issue was addressed through improved state management
|
5.5
Medium
|
May 12, 2025 |
| CVE-2025-31245 |
The issue was addressed with improved checks
|
5.5
Medium
|
May 12, 2025 |
| CVE-2025-31228 |
The issue was addressed with improved authentication
|
6.8
Medium
|
May 12, 2025 |
| CVE-2025-31208 |
The issue was addressed with improved checks
|
7.5
High
|
May 12, 2025 |
| CVE-2025-31225 |
A privacy issue was addressed by removing sensitive data
|
7.1
High
|
May 12, 2025 |
| CVE-2025-31233 |
The issue was addressed with improved input sanitization
|
6.3
Medium
|
May 12, 2025 |
| CVE-2025-31209 |
An out-of-bounds read was addressed with improved bounds checking
|
6.3
Medium
|
May 12, 2025 |