<?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 15:41:12 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-38004 — can: bcm: add locking for bcm_op runtime updates</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-38004</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;can: bcm: add locking for bcm_op runtime updates&lt;/p&gt;
&lt;p&gt;The CAN broadcast manager (CAN BCM) can send a sequence of CAN frames via
hrtimer. The content and also the length of the sequence can be changed
resp reduced at runtime where the &amp;#39;currframe&amp;#39; counter is then set to zero.&lt;/p&gt;
&lt;p&gt;Although this appeared to be a safe operation the updates of &amp;#39;currframe&amp;#39;
can be triggered from user space and hrtimer context in bcm_can_tx().
Anderson Nascimento created a proof of concept that triggered a KASAN
slab-out-of-bounds read access which can be prevented with a spin_lock_bh.&lt;/p&gt;
&lt;p&gt;At the rework of bcm_can_tx() the &amp;#39;count&amp;#39; variable has been moved into
the protected section as this variable can be modified from both contexts
too.&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;can: bcm: add locking for bcm_op runtime updates&lt;/p&gt;
&lt;p&gt;The CAN broadcast manager (CAN BCM) can send a sequence of CAN frames via
hrtimer. The content and also the length of the sequence can be changed
resp reduced at runtime where the &amp;#39;currframe&amp;#39; counter is then set to zero.&lt;/p&gt;
&lt;p&gt;Although this appeared to be a safe operation the updates of &amp;#39;currframe&amp;#39;
can be triggered from user space and hrtimer context in bcm_can_tx().
Anderson Nascimento created a proof of concept that triggered a KASAN
slab-out-of-bounds read access which can be prevented with a spin_lock_bh.&lt;/p&gt;
&lt;p&gt;At the rework of bcm_can_tx() the &amp;#39;count&amp;#39; variable has been moved into
the protected section as this variable can be modified from both contexts
too.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-38004</guid>
    </item>
  </channel>
</rss>
