<?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://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-29T07:27:07.240004+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" 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://vulnerability.circl.lu/vuln/cve-2026-68327</id>
    <title>CVE-2026-68327 — wan: wanxl: Only reset hardware after BAR mapping</title>
    <updated>2026-09-29T07:27:07.241761+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>wan: wanxl: Only reset hardware after BAR mapping</p>
<p>wanxl_pci_init_one() stores the freshly allocated card in driver data
before the PLX BAR is mapped.  Several early probe failures then unwind
through wanxl_pci_remove_one(), including failure to allocate the coherent
status area or to restore the DMA mask.</p>
<p>wanxl_pci_remove_one() unconditionally calls wanxl_reset(), and
wanxl_reset() dereferences card-&gt;plx.  On those early failures card-&gt;plx
is still NULL, so the error path can dereference a NULL MMIO pointer.</p>
<p>Only issue the hardware reset once the BAR mapping exists.  The remaining
cleanup in wanxl_pci_remove_one() already checks whether later resources
were allocated.</p>
<p>This issue was found by a static analysis checker and confirmed by
manual source review.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-68327"/>
  </entry>
</feed>
