https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 01 Oct 2026 21:41:01 +0000 https://vulnerability.circl.lu/vuln/cve-2025-23155 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net: stmmac: Fix accessing freed irq affinity_hint</p> <p>In stmmac_request_irq_multi_msi(), a pointer to the stack variable cpu_mask is passed to irq_set_affinity_hint(). This value is stored in irq_desc-&gt;affinity_hint, but once stmmac_request_irq_multi_msi() returns, the pointer becomes dangling.</p> <p>The affinity_hint is exposed via procfs with S_IRUGO permissions, allowing any unprivileged process to read it. Accessing this stale pointer can lead to:</p> <p>- a kernel oops or panic if the referenced memory has been released and unmapped, or - leakage of kernel data into userspace if the memory is re-used for other purposes.</p> <p>All platforms that use stmmac with PCI MSI (Intel, Loongson, etc) are affected.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net: stmmac: Fix accessing freed irq affinity_hint</p> <p>In stmmac_request_irq_multi_msi(), a pointer to the stack variable cpu_mask is passed to irq_set_affinity_hint(). This value is stored in irq_desc-&gt;affinity_hint, but once stmmac_request_irq_multi_msi() returns, the pointer becomes dangling.</p> <p>The affinity_hint is exposed via procfs with S_IRUGO permissions, allowing any unprivileged process to read it. Accessing this stale pointer can lead to:</p> <p>- a kernel oops or panic if the referenced memory has been released and unmapped, or - leakage of kernel data into userspace if the memory is re-used for other purposes.</p> <p>All platforms that use stmmac with PCI MSI (Intel, Loongson, etc) are affected.</p> https://vulnerability.circl.lu/vuln/cve-2025-23155