https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 07:03:59 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-02569 bdu:2026-02569 https://cve.radiocsirt.org/vuln/bdu:2026-02569 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0252 certfr-2025-avi-0252 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0252 https://cve.radiocsirt.org/vuln/euvd-2026-310550 EUVD-2026-310550 https://cve.radiocsirt.org/vuln/euvd-2026-310550 https://cve.radiocsirt.org/vuln/fkie_cve-2022-49434 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>PCI: Avoid pci_dev_lock() AB/BA deadlock with sriov_numvfs_store()</p> <p>The sysfs sriov_numvfs_store() path acquires the device lock before the config space access lock:</p> <p>sriov_numvfs_store device_lock # A (1) acquire device lock sriov_configure vfio_pci_sriov_configure # (for example) vfio_pci_core_sriov_configure pci_disable_sriov sriov_disable pci_cfg_access_lock pci_wait_cfg # B (4) wait for dev-&gt;block_cfg_access == 0</p> <p>Previously, pci_dev_lock() acquired the config space access lock before the device lock:</p> <p>pci_dev_lock pci_cfg_access_lock dev-&gt;block_cfg_access = 1 # B (2) set dev-&gt;block_cfg_access = 1 device_lock # A (3) wait for device lock</p> <p>Any path that uses pci_dev_lock(), e.g., pci_reset_function(), may deadlock with sriov_numvfs_store() if the operations occur in the sequence (1) (2) (3) (4).</p> <p>Avoid the deadlock by reversing the order in pci_dev_lock() so it acquires the device lock before the config space access lock, the same as the sriov_numvfs_store() path.</p> <p>[bhelgaas: combined and adapted commit log from Jay Zhou&#39;s independent subsequent posting: https://lore.kernel.org/r/20220404062539.1710-1-jianjay.zhou@huawei.com]</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>PCI: Avoid pci_dev_lock() AB/BA deadlock with sriov_numvfs_store()</p> <p>The sysfs sriov_numvfs_store() path acquires the device lock before the config space access lock:</p> <p>sriov_numvfs_store device_lock # A (1) acquire device lock sriov_configure vfio_pci_sriov_configure # (for example) vfio_pci_core_sriov_configure pci_disable_sriov sriov_disable pci_cfg_access_lock pci_wait_cfg # B (4) wait for dev-&gt;block_cfg_access == 0</p> <p>Previously, pci_dev_lock() acquired the config space access lock before the device lock:</p> <p>pci_dev_lock pci_cfg_access_lock dev-&gt;block_cfg_access = 1 # B (2) set dev-&gt;block_cfg_access = 1 device_lock # A (3) wait for device lock</p> <p>Any path that uses pci_dev_lock(), e.g., pci_reset_function(), may deadlock with sriov_numvfs_store() if the operations occur in the sequence (1) (2) (3) (4).</p> <p>Avoid the deadlock by reversing the order in pci_dev_lock() so it acquires the device lock before the config space access lock, the same as the sriov_numvfs_store() path.</p> <p>[bhelgaas: combined and adapted commit log from Jay Zhou&#39;s independent subsequent posting: https://lore.kernel.org/r/20220404062539.1710-1-jianjay.zhou@huawei.com]</p> https://cve.radiocsirt.org/vuln/fkie_cve-2022-49434 https://cve.radiocsirt.org/vuln/ghsa-fxw3-5jmj-82p9 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>PCI: Avoid pci_dev_lock() AB/BA deadlock with sriov_numvfs_store()</p> <p>The sysfs sriov_numvfs_store() path acquires the device lock before the config space access lock:</p> <p>sriov_numvfs_store device_lock # A (1) acquire device lock sriov_configure vfio_pci_sriov_configure # (for example) vfio_pci_core_sriov_configure pci_disable_sriov sriov_disable pci_cfg_access_lock pci_wait_cfg # B (4) wait for dev-&gt;block_cfg_access == 0</p> <p>Previously, pci_dev_lock() acquired the config space access lock before the device lock:</p> <p>pci_dev_lock pci_cfg_access_lock dev-&gt;block_cfg_access = 1 # B (2) set dev-&gt;block_cfg_access = 1 device_lock # A (3) wait for device lock</p> <p>Any path that uses pci_dev_lock(), e.g., pci_reset_function(), may deadlock with sriov_numvfs_store() if the operations occur in the sequence (1) (2) (3) (4).</p> <p>Avoid the deadlock by reversing the order in pci_dev_lock() so it acquires the device lock before the config space access lock, the same as the sriov_numvfs_store() path.</p> <p>[bhelgaas: combined and adapted commit log from Jay Zhou&#39;s independent subsequent posting: https://lore.kernel.org/r/20220404062539.1710-1-jianjay.zhou@huawei.com]</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>PCI: Avoid pci_dev_lock() AB/BA deadlock with sriov_numvfs_store()</p> <p>The sysfs sriov_numvfs_store() path acquires the device lock before the config space access lock:</p> <p>sriov_numvfs_store device_lock # A (1) acquire device lock sriov_configure vfio_pci_sriov_configure # (for example) vfio_pci_core_sriov_configure pci_disable_sriov sriov_disable pci_cfg_access_lock pci_wait_cfg # B (4) wait for dev-&gt;block_cfg_access == 0</p> <p>Previously, pci_dev_lock() acquired the config space access lock before the device lock:</p> <p>pci_dev_lock pci_cfg_access_lock dev-&gt;block_cfg_access = 1 # B (2) set dev-&gt;block_cfg_access = 1 device_lock # A (3) wait for device lock</p> <p>Any path that uses pci_dev_lock(), e.g., pci_reset_function(), may deadlock with sriov_numvfs_store() if the operations occur in the sequence (1) (2) (3) (4).</p> <p>Avoid the deadlock by reversing the order in pci_dev_lock() so it acquires the device lock before the config space access lock, the same as the sriov_numvfs_store() path.</p> <p>[bhelgaas: combined and adapted commit log from Jay Zhou&#39;s independent subsequent posting: https://lore.kernel.org/r/20220404062539.1710-1-jianjay.zhou@huawei.com]</p> https://cve.radiocsirt.org/vuln/ghsa-fxw3-5jmj-82p9 https://cve.radiocsirt.org/vuln/rhsa-2023:2458 <p>hw: cpu: AMD CPUs may transiently execute beyond unconditional direct branch kernel: ext4: kernel bug in ext4_write_inline_data_end() kernel: malicious data for FBIOPUT_VSCREENINFO ioctl may cause OOB write memory kernel: hwmon: (mlxreg-fan) Return non-zero value when fan current state is enforced from sysfs kernel: mlxsw: thermal: Fix out-of-bounds memory accesses kernel: mlxsw: spectrum: Protect driver from buggy firmware kernel: net: stmmac: fix tc flower deletion for VLAN priority Rx steering kernel: can: etas_es58x: es58x_rx_err_msg(): fix memory leak in error path kernel: possible race condition in drivers/tty/tty_buffers.c kernel: KVM: NULL pointer dereference in kvm_mmu_invpcid_gva kernel: use-after-free in free_pipe_info() could lead to privilege escalation kernel: KVM: nVMX: missing IBPB when exiting from nested guest can lead to Spectre v2 attacks kernel: netfilter: nf_conntrack_irc message handling issue kernel: race condition in xfrm_probe_algs can lead to OOB read/write kernel: out-of-bounds read in fib_nh_match of the file net/ipv4/fib_semantics.c kernel: race condition in hugetlb_no_page() in mm/hugetlb.c kernel: memory leak in ipv6_renew_options() kernel: data races around icsk-&gt;icsk_af_ops in do_ipv6_setsockopt kernel: data races around sk-&gt;sk_prot kernel: memory leak in l2cap_recv_acldata of the file net/bluetooth/l2cap_core.c kernel: denial of service in follow_page_pte in mm/gup.c due to poisoned pte entry kernel: use-after-free after failed devlink relo…</p> <p>hw: cpu: AMD CPUs may transiently execute beyond unconditional direct branch kernel: ext4: kernel bug in ext4_write_inline_data_end() kernel: malicious data for FBIOPUT_VSCREENINFO ioctl may cause OOB write memory kernel: hwmon: (mlxreg-fan) Return non-zero value when fan current state is enforced from sysfs kernel: mlxsw: thermal: Fix out-of-bounds memory accesses kernel: mlxsw: spectrum: Protect driver from buggy firmware kernel: net: stmmac: fix tc flower deletion for VLAN priority Rx steering kernel: can: etas_es58x: es58x_rx_err_msg(): fix memory leak in error path kernel: possible race condition in drivers/tty/tty_buffers.c kernel: KVM: NULL pointer dereference in kvm_mmu_invpcid_gva kernel: use-after-free in free_pipe_info() could lead to privilege escalation kernel: KVM: nVMX: missing IBPB when exiting from nested guest can lead to Spectre v2 attacks kernel: netfilter: nf_conntrack_irc message handling issue kernel: race condition in xfrm_probe_algs can lead to OOB read/write kernel: out-of-bounds read in fib_nh_match of the file net/ipv4/fib_semantics.c kernel: race condition in hugetlb_no_page() in mm/hugetlb.c kernel: memory leak in ipv6_renew_options() kernel: data races around icsk-&gt;icsk_af_ops in do_ipv6_setsockopt kernel: data races around sk-&gt;sk_prot kernel: memory leak in l2cap_recv_acldata of the file net/bluetooth/l2cap_core.c kernel: denial of service in follow_page_pte in mm/gup.c due to poisoned pte entry kernel: use-after-free after failed devlink relo…</p> https://cve.radiocsirt.org/vuln/rhsa-2023:2458 https://cve.radiocsirt.org/vuln/suse-su-2025:1176-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/suse-su-2025:1176-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49434 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:16.04:LTS: linux and 144 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: PCI: Avoid pci_dev_lock() AB/BA deadlock with sriov_numvfs_store() The sysfs sriov_numvfs_store() path acquires the device lock before the config space access lock: sriov_numvfs_store device_lock # A (1) acquire device lock sriov_configure vfio_pci_sriov_configure # (for example) vfio_pci_core_sriov_configure pci_disable_sriov sriov_disable pci_cfg_access_lock pci_wait_cfg # B (4) wait for dev-&gt;block_cfg_access == 0 Previously, pci_dev_lock() acquired the config space access lock before the device lock: pci_dev_lock pci_cfg_access_lock dev-&gt;block_cfg_access = 1 # B (2) set dev-&gt;block_cfg_access = 1 device_lock # A (3) wait for device lock Any path that uses pci_dev_lock(), e.g., pci_reset_function(), may deadlock with sriov_numvfs_store() if the operations occur in the sequence (1) (2) (3) (4). Avoid the deadlock by reversing the order in pci_dev_lock() so it acquires the device lock before the config space access lock, the same as the sriov_numvfs_store() path. [bhelgaas: combined and adapted commit log from Jay Zhou&#39;s independent subsequent posting: https://lore.kernel.org/r/20220404062539.1710-1-jianjay.zhou@huawei.com]</p> <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:16.04:LTS: linux and 144 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: PCI: Avoid pci_dev_lock() AB/BA deadlock with sriov_numvfs_store() The sysfs sriov_numvfs_store() path acquires the device lock before the config space access lock: sriov_numvfs_store device_lock # A (1) acquire device lock sriov_configure vfio_pci_sriov_configure # (for example) vfio_pci_core_sriov_configure pci_disable_sriov sriov_disable pci_cfg_access_lock pci_wait_cfg # B (4) wait for dev-&gt;block_cfg_access == 0 Previously, pci_dev_lock() acquired the config space access lock before the device lock: pci_dev_lock pci_cfg_access_lock dev-&gt;block_cfg_access = 1 # B (2) set dev-&gt;block_cfg_access = 1 device_lock # A (3) wait for device lock Any path that uses pci_dev_lock(), e.g., pci_reset_function(), may deadlock with sriov_numvfs_store() if the operations occur in the sequence (1) (2) (3) (4). Avoid the deadlock by reversing the order in pci_dev_lock() so it acquires the device lock before the config space access lock, the same as the sriov_numvfs_store() path. [bhelgaas: combined and adapted commit log from Jay Zhou&#39;s independent subsequent posting: https://lore.kernel.org/r/20220404062539.1710-1-jianjay.zhou@huawei.com]</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49434