<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-28T17:53:11.333591+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/cve-2022-49350</id>
    <title>CVE-2022-49350 — net: mdio: unexport __init-annotated mdio_bus_init()</title>
    <updated>2026-09-28T17:53:11.335529+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><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></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2022-49350"/>
  </entry>
</feed>
