<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 01:09:36 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-31749 — comedi: ni_atmio16d: Fix invalid clean-up after failed attach</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-31749</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;comedi: ni_atmio16d: Fix invalid clean-up after failed attach&lt;/p&gt;
&lt;p&gt;If the driver&amp;#39;s COMEDI &amp;#34;attach&amp;#34; handler function (`atmio16d_attach()`)
returns an error, the COMEDI core will call the driver&amp;#39;s &amp;#34;detach&amp;#34;
handler function (`atmio16d_detach()`) to clean up.  This calls
`reset_atmio16d()` unconditionally, but depending on where the error
occurred in the attach handler, the device may not have been
sufficiently initialized to call `reset_atmio16d()`.  It uses
`dev-&amp;gt;iobase` as the I/O port base address and `dev-&amp;gt;private` as the
pointer to the COMEDI device&amp;#39;s private data structure.  `dev-&amp;gt;iobase`
may still be set to its initial value of 0, which would result in
undesired writes to low I/O port addresses.  `dev-&amp;gt;private` may still be
`NULL`, which would result in null pointer dereferences.&lt;/p&gt;
&lt;p&gt;Fix `atmio16d_detach()` by checking that `dev-&amp;gt;private` is valid
(non-null) before calling `reset_atmio16d()`.  This implies that
`dev-&amp;gt;iobase` was set correctly since that is set up before
`dev-&amp;gt;private`.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;comedi: ni_atmio16d: Fix invalid clean-up after failed attach&lt;/p&gt;
&lt;p&gt;If the driver&amp;#39;s COMEDI &amp;#34;attach&amp;#34; handler function (`atmio16d_attach()`)
returns an error, the COMEDI core will call the driver&amp;#39;s &amp;#34;detach&amp;#34;
handler function (`atmio16d_detach()`) to clean up.  This calls
`reset_atmio16d()` unconditionally, but depending on where the error
occurred in the attach handler, the device may not have been
sufficiently initialized to call `reset_atmio16d()`.  It uses
`dev-&amp;gt;iobase` as the I/O port base address and `dev-&amp;gt;private` as the
pointer to the COMEDI device&amp;#39;s private data structure.  `dev-&amp;gt;iobase`
may still be set to its initial value of 0, which would result in
undesired writes to low I/O port addresses.  `dev-&amp;gt;private` may still be
`NULL`, which would result in null pointer dereferences.&lt;/p&gt;
&lt;p&gt;Fix `atmio16d_detach()` by checking that `dev-&amp;gt;private` is valid
(non-null) before calling `reset_atmio16d()`.  This implies that
`dev-&amp;gt;iobase` was set correctly since that is set up before
`dev-&amp;gt;private`.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-31749</guid>
    </item>
  </channel>
</rss>
