<?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>Wed, 30 Sep 2026 03:55:43 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-68387 — can: raw: add locking for raw flags bitfield</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-68387</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: raw: add locking for raw flags bitfield&lt;/p&gt;
&lt;p&gt;With commit 890e5198a6e5 (&amp;#34;can: raw: use bitfields to store flags in
struct raw_sock&amp;#34;) the formerly separate integer values have been integrated
into a single bitfield. This led to a read-modify-write operation when
changing a flag in raw_setsockopt() which now needs a locking to prevent
concurrent access.&lt;/p&gt;
&lt;p&gt;Instead of adding a lock/unlock hell in each of the flag manipulations this
patch introduces a wrapper for a new raw_setsockopt_locked() function
analogue to the isotp_setsockopt[_locked]() approach in net/can/isotp.c&lt;/p&gt;
&lt;p&gt;[mkl: use Closes tag instead of Link]&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: raw: add locking for raw flags bitfield&lt;/p&gt;
&lt;p&gt;With commit 890e5198a6e5 (&amp;#34;can: raw: use bitfields to store flags in
struct raw_sock&amp;#34;) the formerly separate integer values have been integrated
into a single bitfield. This led to a read-modify-write operation when
changing a flag in raw_setsockopt() which now needs a locking to prevent
concurrent access.&lt;/p&gt;
&lt;p&gt;Instead of adding a lock/unlock hell in each of the flag manipulations this
patch introduces a wrapper for a new raw_setsockopt_locked() function
analogue to the isotp_setsockopt[_locked]() approach in net/can/isotp.c&lt;/p&gt;
&lt;p&gt;[mkl: use Closes tag instead of Link]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-68387</guid>
    </item>
  </channel>
</rss>
