7 matches found
CVE-2026-43211
A flaw was found in the Linux kernel. An error in the PCI Peripheral Component Interconnect subsystem's lock management, specifically within the pcislottrylock function, can lead to system instability. This occurs when a lock is incorrectly released, potentially causing warnings or interfering wi...
EUVD-2026-27773
In the Linux kernel, the following vulnerability has been resolved: PCI: Fix pcislottrylock error handling Commit a4e772898f8b "PCI: Add missing bridge lock to pcibuslock" delegates the bridge device's pcidevtrylock to pcibustrylock in pcislottrylock, but it forgets to remove the corresponding...
Linux Distros Unpatched Vulnerability : CVE-2026-43211
"The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - PCI: Fix pcislottrylock error handling Commit a4e772898f8b PCI: Add missing bridge lock to pcibuslock delegates the bridge device's pcidevtrylock to...
SUSE CVE-2025-39941
In the Linux kernel, the following vulnerability has been resolved: zram: fix slot write race condition Parallel concurrent writes to the same zram index result in leaked zsmalloc handles. Schematically we can have something like this: CPU0 CPU1 zramslotlock zsfreehandle zramslotlock zramslotlock...
CVE-2025-39941
In the Linux kernel, the following vulnerability has been resolved: zram: fix slot write race condition Parallel concurrent writes to the same zram index result in leaked zsmalloc handles. Schematically we can have something like this: CPU0 CPU1 zramslotlock zsfreehandle zramslotlock zramslotlock...
CVE-2025-39941
CVE-2025-39941 describes a race in zram slot handling in the Linux kernel. Parallel writes to the same zram index can leak zsmalloc handles because zs_free() may run too early; the fix requires resetting the zram entry right before assigning a new handle within the same slot lock scope. Documents...
CVE-2025-39941 zram: fix slot write race condition
In the Linux kernel, the following vulnerability has been resolved: zram: fix slot write race condition Parallel concurrent writes to the same zram index result in leaked zsmalloc handles. Schematically we can have something like this: CPU0 CPU1 zramslotlock zsfreehandle zramslotlock zramslotlock...