EUVD-2025-19776

Malicious code in bioql PyPI...

EUVD-2025-27879

Malicious code in bioql PyPI...

EUVD-2025-27926

Malicious code in bioql PyPI...

EUVD-2025-22609

Malicious code in bioql PyPI...

EUVD-2022-55470

Malicious code in bioql PyPI...

EUVD-2022-55524

Malicious code in bioql PyPI...

EUVD-2025-26770

Malicious code in bioql PyPI...

EUVD-2024-54028

Malicious code in bioql PyPI...

EUVD-2022-55204

Malicious code in bioql PyPI...

CVE-2025-39921

In the Linux kernel, the following vulnerability has been resolved: spi: microchip-core-qspi: stop checking viability of op-maxfreq in supportsop callback In commit 13529647743d9 "spi: microchip-core-qspi: Support per spi-mem operation frequency switches" the logic for checking the viability of...

CVE-2025-39921

In the Linux kernel, the following vulnerability has been resolved: spi: microchip-core-qspi: stop checking viability of op-maxfreq in supportsop callback In commit 13529647743d9 "spi: microchip-core-qspi: Support per spi-mem operation frequency switches" the logic for checking the viability of...

CVE-2025-39921

The CVE affects the Linux kernel driver spi-microchip-core-qspi. During probe, op->max_freq is not valid (zero) in the supports_op callback, causing baud_rate_val to be INT_MAX and risking probe failure of the attached memory device. The root cause is that the per-op frequency switch logic add...

CVE-2025-39921 spi: microchip-core-qspi: stop checking viability of op->max_freq in supports_op callback

In the Linux kernel, the following vulnerability has been resolved: spi: microchip-core-qspi: stop checking viability of op-maxfreq in supportsop callback In commit 13529647743d9 "spi: microchip-core-qspi: Support per spi-mem operation frequency switches" the logic for checking the viability of...

CVE-2025-39921 spi: microchip-core-qspi: stop checking viability of op->max_freq in supports_op callback

In the Linux kernel, the following vulnerability has been resolved: spi: microchip-core-qspi: stop checking viability of op-maxfreq in supportsop callback In commit 13529647743d9 "spi: microchip-core-qspi: Support per spi-mem operation frequency switches" the logic for checking the viability of...

PT-2025-40095

Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description A flaw exists in the Linux kernel’s spi subsystem, specifically within the microchip-core-qspi driver. A logic error introduced during a modification to the supports op callback function...

kernel: firmware: arm_scpi: Ensure scpi_info is not assigned if the probe fails

In the Linux kernel, the following vulnerability has been resolved: firmware: armscpi: Ensure scpiinfo is not assigned if the probe fails When scpi probe fails, at any point, we need to ensure that the scpiinfo is not set and will remain NULL until the probe succeeds. If it is not taken care, the...

kernel: firmware: arm_scpi: Ensure scpi_info is not assigned if the probe fails

In the Linux kernel, the following vulnerability has been resolved: firmware: armscpi: Ensure scpiinfo is not assigned if the probe fails When scpi probe fails, at any point, we need to ensure that the scpiinfo is not set and will remain NULL until the probe succeeds. If it is not taken care, the...

PT-2025-42269

Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description The Linux kernel contains a flaw related to the handling of timers and work items within the tc358743 device driver. Specifically, the use of timer delete and cancel delayed work does no...

PT-2025-38021

Name of the Vulnerable Software and Affected Versions: Linux kernel affected versions not specified Description: The Linux kernel contains a flaw in the hnae ae register function within the networking subsystem. A memory leak can occur during module probing if device register fails, but the...

CVE-2022-50260

In the Linux kernel, the following vulnerability has been resolved: drm/msm: Make .remove and .shutdown HW shutdown consistent Drivers' .remove and .shutdown callbacks are executed on different code paths. The former is called when a device is removed from the bus, while the latter is called at...