395 matches found
EUVD-2023-49398
Malicious code in bioql PyPI...
EUVD-2023-25000
Malicious code in bioql PyPI...
EUVD-2022-42808
Malicious code in bioql PyPI...
EUVD-2024-20757
Malicious code in bioql PyPI...
EUVD-2022-31331
Malicious code in bioql PyPI...
EUVD-2023-49396
Malicious code in bioql PyPI...
EUVD-2023-58185
Malicious code in bioql PyPI...
EUVD-2022-44608
Malicious code in bioql PyPI...
EUVD-2023-12296
Malicious code in bioql PyPI...
EUVD-2023-49397
Malicious code in bioql PyPI...
EUVD-2025-30326
Malicious code in bioql PyPI...
EUVD-2023-29449
Malicious code in bioql PyPI...
EUVD-2023-49400
Malicious code in bioql PyPI...
EUVD-2022-42806
Malicious code in bioql PyPI...
EUVD-2024-54342
Malicious code in bioql PyPI...
EUVD-2025-31892
Malicious code in bioql PyPI...
SUSE CVE-2023-53509
In the Linux kernel, the following vulnerability has been resolved: qed: allow sleep in qedmcptracedump By default, qedmcpcmdandunion delays 10us at a time in a loop that can run 500K times, so calls to qedmcpnvmrdcmd may block the current thread for over 5s. We observed thread scheduling delays...
AZL-75107 CVE-2023-53509 affecting package kernel 5.15.200.1-1
In the Linux kernel, the following vulnerability has been resolved: qed: allow sleep in qedmcptracedump By default, qedmcpcmdandunion delays 10us at a time in a loop that can run 500K times, so calls to qedmcpnvmrdcmd may block the current thread for over 5s. We observed thread scheduling delays...
CVE-2023-53509
In the Linux kernel, the following vulnerability has been resolved: qed: allow sleep in qedmcptracedump By default, qedmcpcmdandunion delays 10us at a time in a loop that can run 500K times, so calls to qedmcpnvmrdcmd may block the current thread for over 5s. We observed thread scheduling delays...
UBUNTU-CVE-2023-53509
In the Linux kernel, the following vulnerability has been resolved: qed: allow sleep in qedmcptracedump By default, qedmcpcmdandunion delays 10us at a time in a loop that can run 500K times, so calls to qedmcpnvmrdcmd may block the current thread for over 5s. We observed thread scheduling delays...