EUVD-2023-54722

Malicious code in bioql PyPI...

EUVD-2022-27338

Malicious code in bioql PyPI...

EUVD-2023-26098

Malicious code in bioql PyPI...

EUVD-2023-32633

Malicious code in bioql PyPI...

EUVD-2024-2705

Malicious code in bioql PyPI...

EUVD-2024-16791

Malicious code in bioql PyPI...

EUVD-2024-19778

Malicious code in bioql PyPI...

EUVD-2021-2876

Malicious code in bioql PyPI...

EUVD-2023-59876

Malicious code in bioql PyPI...

EUVD-2024-50277

Malicious code in bioql PyPI...

EUVD-2023-32627

Malicious code in bioql PyPI...

EUVD-2024-18215

Malicious code in bioql PyPI...

EUVD-2024-18090

Malicious code in bioql PyPI...

EUVD-2021-2833

Malicious code in bioql PyPI...

EUVD-2024-29360

Malicious code in bioql PyPI...

EUVD-2024-30746

Malicious code in bioql PyPI...

EUVD-2023-59866

Malicious code in bioql PyPI...

UBUNTU-CVE-2023-53508

In the Linux kernel, the following vulnerability has been resolved: ublk: fail to start device if queue setup is interrupted In ublkctrlstartdev, if waitforcompletioninterruptible is interrupted by signal, queues aren't setup successfully yet, so we have to fail UBLKCMDSTARTDEV, otherwise kernel...

CVE-2023-53508

Technical details for CVE-2023-53508 are not provided in the supplied documents. Monitor for official updates from vendors/advisories; current sources only reiterate a kernel fix without specifics.

CVE-2023-53508 ublk: fail to start device if queue setup is interrupted

In the Linux kernel, the following vulnerability has been resolved: ublk: fail to start device if queue setup is interrupted In ublkctrlstartdev, if waitforcompletioninterruptible is interrupted by signal, queues aren't setup successfully yet, so we have to fail UBLKCMDSTARTDEV, otherwise kernel...