https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 28 Sep 2026 21:57:04 +0000 https://db.gcve.eu/vuln/cve-2022-49350 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net: mdio: unexport __init-annotated mdio_bus_init()</p> <p>EXPORT_SYMBOL and __init is a bad combination because the .init.text section is freed up after the initialization. Hence, modules cannot use symbols annotated __init. The access to a freed symbol may end up with kernel panic.</p> <p>modpost used to detect it, but it has been broken for a decade.</p> <p>Recently, I fixed modpost so it started to warn it again, then this showed up in linux-next builds.</p> <p>There are two ways to fix it:</p> <p>- Remove __init - Remove EXPORT_SYMBOL</p> <p>I chose the latter for this case because the only in-tree call-site, drivers/net/phy/phy_device.c is never compiled as modular. (CONFIG_PHYLIB is boolean)</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net: mdio: unexport __init-annotated mdio_bus_init()</p> <p>EXPORT_SYMBOL and __init is a bad combination because the .init.text section is freed up after the initialization. Hence, modules cannot use symbols annotated __init. The access to a freed symbol may end up with kernel panic.</p> <p>modpost used to detect it, but it has been broken for a decade.</p> <p>Recently, I fixed modpost so it started to warn it again, then this showed up in linux-next builds.</p> <p>There are two ways to fix it:</p> <p>- Remove __init - Remove EXPORT_SYMBOL</p> <p>I chose the latter for this case because the only in-tree call-site, drivers/net/phy/phy_device.c is never compiled as modular. (CONFIG_PHYLIB is boolean)</p> https://db.gcve.eu/vuln/cve-2022-49350