EUVD-2024-16361

Malicious code in bioql PyPI...

EUVD-2021-3215

Malicious code in bioql PyPI...

EUVD-2021-2989

Malicious code in bioql PyPI...

EUVD-2021-3549

Malicious code in bioql PyPI...

EUVD-2022-37690

Malicious code in bioql PyPI...

EUVD-2023-44491

Malicious code in bioql PyPI...

EUVD-2022-41554

Malicious code in bioql PyPI...

EUVD-2025-6571

Malicious code in bioql PyPI...

EUVD-2022-25787

Malicious code in bioql PyPI...

EUVD-2022-42292

Malicious code in bioql PyPI...

EUVD-2023-25594

Malicious code in bioql PyPI...

EUVD-2023-59697

Malicious code in bioql PyPI...

EUVD-2023-25595

Malicious code in bioql PyPI...

EUVD-2022-43654

Malicious code in bioql PyPI...

EUVD-2021-7327

Malicious code in bioql PyPI...

EUVD-2022-25242

Malicious code in bioql PyPI...

Linux Distros Unpatched Vulnerability : CVE-2023-53298

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - nfc: fix memory leak of seio context in nfcgenlseio The callback context for sending/receiving APDUs to/from the selected secure element is allocated inside...

SUSE CVE-2023-53298

In the Linux kernel, the following vulnerability has been resolved: nfc: fix memory leak of seio context in nfcgenlseio The callback context for sending/receiving APDUs to/from the selected secure element is allocated inside nfcgenlseio and supposed to be eventually freed in seiocb callback...

DEBIAN-CVE-2023-53298

In the Linux kernel, the following vulnerability has been resolved: nfc: fix memory leak of seio context in nfcgenlseio The callback context for sending/receiving APDUs to/from the selected secure element is allocated inside nfcgenlseio and supposed to be eventually freed in seiocb callback...

UBUNTU-CVE-2023-53298

In the Linux kernel, the following vulnerability has been resolved: nfc: fix memory leak of seio context in nfcgenlseio The callback context for sending/receiving APDUs to/from the selected secure element is allocated inside nfcgenlseio and supposed to be eventually freed in seiocb callback...