IO
Product
Iot-yocto
15
CVEs
0
On KEV
6.7
Max CVSS
0
New 30D
Severity mix
Critical 0High 0Medium 15Low 0
Watch
Add Iot-yocto to your stack to get only the CVEs that touch what you run.
| CVE | CVSS | Published | Summary · affected versions |
|---|---|---|---|
| CVE-2023-20746 | 6.7 | Jun 6 | In vcu, there is a possible out of bounds write due to improper locking Affected: 22.2 |
| CVE-2023-20745 | 6.7 | Jun 6 | In vcu, there is a possible out of bounds write due to improper locking Affected: 22.2 |
| CVE-2023-20744 | 6.7 | Jun 6 | In vcu, there is a possible use after free due to a logic error Affected: 22.2 |
| CVE-2023-20743 | 6.7 | Jun 6 | In vcu, there is a possible out of bounds write due to improper locking Affected: 22.2 |
| CVE-2023-20740 | 6.7 | Jun 6 | In vcu, there is a possible memory corruption due to a logic error Affected: 22.2 |
| CVE-2023-20738 | 6.7 | Jun 6 | In vcu, there is a possible out of bounds write due to a missing bounds check Affected: 22.2 |
| CVE-2023-20737 | 6.7 | Jun 6 | In vcu, there is a possible use after free due to improper locking Affected: 22.2 |
| CVE-2023-20735 | 6.7 | Jun 6 | In vcu, there is a possible out of bounds write due to a missing bounds check Affected: 22.2 |
| CVE-2023-20734 | 6.7 | Jun 6 | In vcu, there is a possible out of bounds write due to a missing bounds check Affected: 22.2 |
| CVE-2023-20733 | 6.7 | Jun 6 | In vcu, there is a possible use after free due to improper locking Affected: 22.2 |
| CVE-2023-20716 | 6.7 | Jun 6 | In wlan, there is a possible out of bounds write due to a missing bounds check Affected: 22.2; 22.2 |
| CVE-2023-20715 | 6.7 | Jun 6 | In wlan, there is a possible out of bounds write due to a missing bounds check Affected: 22.2; 22.2 |
| CVE-2023-20712 | 6.7 | Jun 6 | In wlan, there is a possible out of bounds write due to a missing bounds check Affected: 22.2; 22.2 |
| CVE-2023-20736 | 6.4 | Jun 6 | In vcu, there is a possible out of bounds write due to a race condition Affected: 22.2 |
| CVE-2023-20747 | 4.4 | Jun 6 | In vcu, there is a possible memory corruption due to type confusion Affected: 22.2 |
Showing 15
