https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 16 Oct 2026 00:01:20 +0000 https://cve.radiocsirt.org/vuln/cve-2025-21810 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>driver core: class: Fix wild pointer dereferences in API class_dev_iter_next()</p> <p>There are a potential wild pointer dereferences issue regarding APIs class_dev_iter_(init|next|exit)(), as explained by below typical usage:</p> <p>// All members of @iter are wild pointers. struct class_dev_iter iter;</p> <p>// class_dev_iter_init(@iter, @class, ...) checks parameter @class for // potential class_to_subsys() error, and it returns void type and does // not initialize its output parameter @iter, so caller can not detect // the error and continues to invoke class_dev_iter_next(@iter) even if // @iter still contains wild pointers. class_dev_iter_init(&amp;iter, ...);</p> <p>// Dereference these wild pointers in @iter here once suffer the error. while (dev = class_dev_iter_next(&amp;iter)) { ... };</p> <p>// Also dereference these wild pointers here. class_dev_iter_exit(&amp;iter);</p> <p>Actually, all callers of these APIs have such usage pattern in kernel tree. Fix by: - Initialize output parameter @iter by memset() in class_dev_iter_init() and give callers prompt by pr_crit() for the error. - Check if @iter is valid in class_dev_iter_next().</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>driver core: class: Fix wild pointer dereferences in API class_dev_iter_next()</p> <p>There are a potential wild pointer dereferences issue regarding APIs class_dev_iter_(init|next|exit)(), as explained by below typical usage:</p> <p>// All members of @iter are wild pointers. struct class_dev_iter iter;</p> <p>// class_dev_iter_init(@iter, @class, ...) checks parameter @class for // potential class_to_subsys() error, and it returns void type and does // not initialize its output parameter @iter, so caller can not detect // the error and continues to invoke class_dev_iter_next(@iter) even if // @iter still contains wild pointers. class_dev_iter_init(&amp;iter, ...);</p> <p>// Dereference these wild pointers in @iter here once suffer the error. while (dev = class_dev_iter_next(&amp;iter)) { ... };</p> <p>// Also dereference these wild pointers here. class_dev_iter_exit(&amp;iter);</p> <p>Actually, all callers of these APIs have such usage pattern in kernel tree. Fix by: - Initialize output parameter @iter by memset() in class_dev_iter_init() and give callers prompt by pr_crit() for the error. - Check if @iter is valid in class_dev_iter_next().</p> https://cve.radiocsirt.org/vuln/cve-2025-21810 https://cve.radiocsirt.org/vuln/usn-7521-1 <p><strong>Affected:</strong> Ubuntu:24.04:LTS: linux-azure-6.11, Ubuntu:24.04:LTS: linux-gcp-6.11, Ubuntu:24.04:LTS: linux-hwe-6.11, Ubuntu:24.04:LTS: linux-oem-6.11</p> <p>Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems: - ARM64 architecture; - PowerPC architecture; - x86 architecture; - Block layer subsystem; - Serial ATA and Parallel ATA drivers; - Drivers core; - Network block device driver; - Bluetooth drivers; - Character device driver; - TPM device driver; - Clock framework and drivers; - Hardware crypto device drivers; - FireWire subsystem; - EFI core; - Qualcomm firmware drivers; - GPIO subsystem; - GPU drivers; - HID subsystem; - I2C subsystem; - I3C subsystem; - InfiniBand drivers; - Input Device (Mouse) drivers; - IOMMU subsystem; - Multiple devices driver; - Media drivers; - NVIDIA Tegra memory controller driver; - Fastrpc Driver; - Network drivers; - Operating Performance Points (OPP) driver; - PCI subsystem; - x86 platform drivers; - PPS (Pulse Per Second) driver; - PTP clock framework; - Remote Processor subsystem; - Real Time Clock drivers; - S/390 drivers; - SCSI subsystem; - QCOM SoC drivers; - SPI subsystem; - Media staging drivers; - Trusted Execution Environment drivers; - TTY drivers; - UFS subsystem; - USB Device Class drivers; - USB core drivers; - USB Gadget drivers; - USB Host Controller drivers; - Framebuffer layer; - File systems infrastructure; - BTRFS file system; - Ceph distributed fi…</p> <p><strong>Affected:</strong> Ubuntu:24.04:LTS: linux-azure-6.11, Ubuntu:24.04:LTS: linux-gcp-6.11, Ubuntu:24.04:LTS: linux-hwe-6.11, Ubuntu:24.04:LTS: linux-oem-6.11</p> <p>Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems: - ARM64 architecture; - PowerPC architecture; - x86 architecture; - Block layer subsystem; - Serial ATA and Parallel ATA drivers; - Drivers core; - Network block device driver; - Bluetooth drivers; - Character device driver; - TPM device driver; - Clock framework and drivers; - Hardware crypto device drivers; - FireWire subsystem; - EFI core; - Qualcomm firmware drivers; - GPIO subsystem; - GPU drivers; - HID subsystem; - I2C subsystem; - I3C subsystem; - InfiniBand drivers; - Input Device (Mouse) drivers; - IOMMU subsystem; - Multiple devices driver; - Media drivers; - NVIDIA Tegra memory controller driver; - Fastrpc Driver; - Network drivers; - Operating Performance Points (OPP) driver; - PCI subsystem; - x86 platform drivers; - PPS (Pulse Per Second) driver; - PTP clock framework; - Remote Processor subsystem; - Real Time Clock drivers; - S/390 drivers; - SCSI subsystem; - QCOM SoC drivers; - SPI subsystem; - Media staging drivers; - Trusted Execution Environment drivers; - TTY drivers; - UFS subsystem; - USB Device Class drivers; - USB core drivers; - USB Gadget drivers; - USB Host Controller drivers; - Framebuffer layer; - File systems infrastructure; - BTRFS file system; - Ceph distributed fi…</p> https://cve.radiocsirt.org/vuln/usn-7521-1