https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 07:54:46 +0000 https://vulnerability.circl.lu/vuln/cve-2023-54065 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net: dsa: realtek: fix out-of-bounds access</p> <p>The probe function sets priv-&gt;chip_data to (void *)priv + sizeof(*priv) with the expectation that priv has enough trailing space.</p> <p>However, only realtek-smi actually allocated this chip_data space. Do likewise in realtek-mdio to fix out-of-bounds accesses.</p> <p>These accesses likely went unnoticed so far, because of an (unused) buf[4096] member in struct realtek_priv, which caused kmalloc to round up the allocated buffer to a big enough size, so nothing of value was overwritten. With a different allocator (like in the barebox bootloader port of the driver) or with KASAN, the memory corruption becomes quickly apparent.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net: dsa: realtek: fix out-of-bounds access</p> <p>The probe function sets priv-&gt;chip_data to (void *)priv + sizeof(*priv) with the expectation that priv has enough trailing space.</p> <p>However, only realtek-smi actually allocated this chip_data space. Do likewise in realtek-mdio to fix out-of-bounds accesses.</p> <p>These accesses likely went unnoticed so far, because of an (unused) buf[4096] member in struct realtek_priv, which caused kmalloc to round up the allocated buffer to a big enough size, so nothing of value was overwritten. With a different allocator (like in the barebox bootloader port of the driver) or with KASAN, the memory corruption becomes quickly apparent.</p> https://vulnerability.circl.lu/vuln/cve-2023-54065