Total
92074 CVE
| CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
|---|---|---|---|---|---|
| CVE-2025-3463 | 2025-05-11 | N/A | N/A | ||
| "This issue is limited to motherboards and does not affect laptops, desktop computers, or other endpoints." An insufficient validation vulnerability in ASUS DriverHub may allow untrusted sources to affect system behavior via crafted HTTP requests. Refer to the 'Security Update for ASUS DriverHub' section on the ASUS Security Advisory for more information. | |||||
| CVE-2025-3462 | 2025-05-11 | N/A | N/A | ||
| "This issue is limited to motherboards and does not affect laptops, desktop computers, or other endpoints." An insufficient validation in ASUS DriverHub may allow unauthorized sources to interact with the software's features via crafted HTTP requests. Refer to the 'Security Update for ASUS DriverHub' section on the ASUS Security Advisory for more information. | |||||
| CVE-2025-37889 | 2025-05-10 | N/A | N/A | ||
| In the Linux kernel, the following vulnerability has been resolved: ASoC: ops: Consistently treat platform_max as control value This reverts commit 9bdd10d57a88 ("ASoC: ops: Shift tested values in snd_soc_put_volsw() by +min"), and makes some additional related updates. There are two ways the platform_max could be interpreted; the maximum register value, or the maximum value the control can be set to. The patch moved from treating the value as a control value to a register one. When the patch was applied it was technically correct as snd_soc_limit_volume() also used the register interpretation. However, even then most of the other usages treated platform_max as a control value, and snd_soc_limit_volume() has since been updated to also do so in commit fb9ad24485087 ("ASoC: ops: add correct range check for limiting volume"). That patch however, missed updating snd_soc_put_volsw() back to the control interpretation, and fixing snd_soc_info_volsw_range(). The control interpretation makes more sense as limiting is typically done from the machine driver, so it is appropriate to use the customer facing representation rather than the internal codec representation. Update all the code to consistently use this interpretation of platform_max. Finally, also add some comments to the soc_mixer_control struct to hopefully avoid further patches switching between the two approaches. | |||||
| CVE-2024-39501 | 2025-05-10 | N/A | N/A | ||
| Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | |||||
| CVE-2023-53145 | 2025-05-10 | N/A | N/A | ||
| In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btsdio: fix use after free bug in btsdio_remove due to race condition In btsdio_probe, the data->work is bound with btsdio_work. It will be started in btsdio_send_frame. If the btsdio_remove runs with a unfinished work, there may be a race condition that hdev is freed but used in btsdio_work. Fix it by canceling the work before do cleanup in btsdio_remove. | |||||
| CVE-2023-53063 | 2025-05-10 | N/A | N/A | ||
| Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | |||||
| CVE-2022-48917 | 2025-05-10 | N/A | N/A | ||
| Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | |||||
| CVE-2025-37835 | 2025-05-10 | N/A | N/A | ||
| Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | |||||
| CVE-2025-37795 | 2025-05-10 | N/A | N/A | ||
| Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | |||||
| CVE-2024-50016 | 2025-05-10 | N/A | N/A | ||
| Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | |||||
| CVE-2025-47770 | 2025-05-10 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-47769 | 2025-05-10 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-47768 | 2025-05-10 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-47767 | 2025-05-10 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-47766 | 2025-05-10 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-47765 | 2025-05-10 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-47764 | 2025-05-10 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-47763 | 2025-05-10 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-47762 | 2025-05-10 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-4447 | 2025-05-09 | N/A | N/A | ||
| In Eclipse OpenJ9 versions up to 0.51, when used with OpenJDK version 8 a stack based buffer overflow can be caused by modifying a file on disk that is read when the JVM starts. | |||||