<?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>Mon, 05 Oct 2026 06:28:50 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-43340 — comedi: Reinit dev-&gt;spinlock between attachments to low-level drivers</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-43340</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: Reinit dev-&amp;gt;spinlock between attachments to low-level drivers&lt;/p&gt;
&lt;p&gt;`struct comedi_device` is the main controlling structure for a COMEDI
device created by the COMEDI subsystem.  It contains a member `spinlock`
containing a spin-lock that is initialized by the COMEDI subsystem, but
is reserved for use by a low-level driver attached to the COMEDI device
(at least since commit 25436dc9d84f (&amp;#34;Staging: comedi: remove RT
code&amp;#34;)).&lt;/p&gt;
&lt;p&gt;Some COMEDI devices (those created on initialization of the COMEDI
subsystem when the &amp;#34;comedi.comedi_num_legacy_minors&amp;#34; parameter is
non-zero) can be attached to different low-level drivers over their
lifetime using the `COMEDI_DEVCONFIG` ioctl command.  This can result in
inconsistent lock states being reported when there is a mismatch in the
spin-lock locking levels used by each low-level driver to which the
COMEDI device has been attached.  Fix it by reinitializing
`dev-&amp;gt;spinlock` before calling the low-level driver&amp;#39;s `attach` function
pointer if `CONFIG_LOCKDEP` is enabled.&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: Reinit dev-&amp;gt;spinlock between attachments to low-level drivers&lt;/p&gt;
&lt;p&gt;`struct comedi_device` is the main controlling structure for a COMEDI
device created by the COMEDI subsystem.  It contains a member `spinlock`
containing a spin-lock that is initialized by the COMEDI subsystem, but
is reserved for use by a low-level driver attached to the COMEDI device
(at least since commit 25436dc9d84f (&amp;#34;Staging: comedi: remove RT
code&amp;#34;)).&lt;/p&gt;
&lt;p&gt;Some COMEDI devices (those created on initialization of the COMEDI
subsystem when the &amp;#34;comedi.comedi_num_legacy_minors&amp;#34; parameter is
non-zero) can be attached to different low-level drivers over their
lifetime using the `COMEDI_DEVCONFIG` ioctl command.  This can result in
inconsistent lock states being reported when there is a mismatch in the
spin-lock locking levels used by each low-level driver to which the
COMEDI device has been attached.  Fix it by reinitializing
`dev-&amp;gt;spinlock` before calling the low-level driver&amp;#39;s `attach` function
pointer if `CONFIG_LOCKDEP` is enabled.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-43340</guid>
    </item>
  </channel>
</rss>
