EUVD-2025-31941

Malicious code in bioql PyPI...

EUVD-2025-11216

Malicious code in bioql PyPI...

EUVD-2025-20037

Malicious code in bioql PyPI...

EUVD-2025-5990

Malicious code in bioql PyPI...

EUVD-2025-13165

Malicious code in bioql PyPI...

EUVD-2025-25093

Malicious code in bioql PyPI...

EUVD-2025-19838

Malicious code in bioql PyPI...

CVE-2022-50448 mm/uffd: fix warning without PTE_MARKER_UFFD_WP compiled in

In the Linux kernel, the following vulnerability has been resolved: mm/uffd: fix warning without PTEMARKERUFFDWP compiled in When PTEMARKERUFFDWP not configured, it's still possible to reach pte marker code and trigger an warning. Add a few CONFIGPTEMARKERUFFDWP ifdefs to make sure the code won't...

CVE-2022-50430

CVE-2022-50430 affects the Linux kernel mmc vub300 driver. The fix prevents calling blocking operations when the current task is not TASK_RUNNING by ensuring vub300_enable_sdio_irq() uses proper mutex usage and marks the current task as TASK_RUNNING in a sleepable context. This reduces a potentia...

PT-2025-40133

Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description A flaw exists in the Linux kernel’s mm/uffd module. Specifically, a warning can occur when PTE MARKER UFFD WP is not compiled in, potentially leading to unexpected behavior. The issue...

Linux kernel 安全漏洞

Linux kernel is the kernel used by Linux, the open source operating system of the Linux Foundation in the United States. A security vulnerability exists in the Linux kernel that stems from the brnflocalin function improperly checking the acknowledgement bit after acknowledgement, which could resu...

tipc: fix kernel warning when sending SYN message

...

CVE-2023-53427

In the Linux kernel, the following vulnerability has been resolved: cifs: Fix warning and UAF when destroy the MR list If the MR allocate failed, the MR recovery work not initialized and list not cleared. Then will be warning and UAF when release the MR: WARNING: CPU: 4 PID: 824 at...

CVE-2023-53431

In the Linux kernel, the following vulnerability has been resolved: scsi: ses: Handle enclosure with just a primary component gracefully This reverts commit 3fe97ff3d949 "scsi: ses: Don't attach if enclosure has no components" and introduces proper handling of case where there are no detected...

CVE-2023-53427 cifs: Fix warning and UAF when destroy the MR list

In the Linux kernel, the following vulnerability has been resolved: cifs: Fix warning and UAF when destroy the MR list If the MR allocate failed, the MR recovery work not initialized and list not cleared. Then will be warning and UAF when release the MR: WARNING: CPU: 4 PID: 824 at...

SUSE CVE-2025-39813

In the Linux kernel, the following vulnerability has been resolved: ftrace: Fix potential warning in traceprintkseq during ftracedump When calling ftracedumpone concurrently with reading tracepipe, a WARNONONCE in traceprintkseq can be triggered due to a race condition. The issue occurs because:...

DEBIAN-CVE-2022-50340

In the Linux kernel, the following vulnerability has been resolved: media: vimc: Fix wrong function called when vimcinit fails In vimcinit, when platformdriverregister&vimcpdrv fails, platformdriverunregister&vimcpdrv is wrongly called rather than platformdeviceunregister&vimcpdev, which causes...

CVE-2022-50340

In the Linux kernel, the following vulnerability has been resolved: media: vimc: Fix wrong function called when vimcinit fails In vimcinit, when platformdriverregister&vimcpdrv fails, platformdriverunregister&vimcpdrv is wrongly called rather than platformdeviceunregister&vimcpdev, which causes...

CVE-2022-50340 media: vimc: Fix wrong function called when vimc_init() fails

In the Linux kernel, the following vulnerability has been resolved: media: vimc: Fix wrong function called when vimcinit fails In vimcinit, when platformdriverregister&vimcpdrv fails, platformdriverunregister&vimcpdrv is wrongly called rather than platformdeviceunregister&vimcpdev, which causes...

CVE-2023-53286

CVE-2023-53286 affects the Linux kernel’s RDMA mlx5 path. The issue is: when destroying QP/RQ, the firmware destruction result was ignored, so upper layers could proceed as if destruction succeeded, potentially triggering kernel WARNs. The description specifies that the kernel now returns the fir...