<?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 10:46:58 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-68250 — hung_task: fix warnings caused by unaligned lock pointers</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-68250</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;hung_task: fix warnings caused by unaligned lock pointers&lt;/p&gt;
&lt;p&gt;The blocker tracking mechanism assumes that lock pointers are at least
4-byte aligned to use their lower bits for type encoding.&lt;/p&gt;
&lt;p&gt;However, as reported by Eero Tamminen, some architectures like m68k
only guarantee 2-byte alignment of 32-bit values. This breaks the
assumption and causes two related WARN_ON_ONCE checks to trigger.&lt;/p&gt;
&lt;p&gt;To fix this, the runtime checks are adjusted to silently ignore any lock
that is not 4-byte aligned, effectively disabling the feature in such
cases and avoiding the related warnings.&lt;/p&gt;
&lt;p&gt;Thanks to Geert Uytterhoeven for bisecting!&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;hung_task: fix warnings caused by unaligned lock pointers&lt;/p&gt;
&lt;p&gt;The blocker tracking mechanism assumes that lock pointers are at least
4-byte aligned to use their lower bits for type encoding.&lt;/p&gt;
&lt;p&gt;However, as reported by Eero Tamminen, some architectures like m68k
only guarantee 2-byte alignment of 32-bit values. This breaks the
assumption and causes two related WARN_ON_ONCE checks to trigger.&lt;/p&gt;
&lt;p&gt;To fix this, the runtime checks are adjusted to silently ignore any lock
that is not 4-byte aligned, effectively disabling the feature in such
cases and avoiding the related warnings.&lt;/p&gt;
&lt;p&gt;Thanks to Geert Uytterhoeven for bisecting!&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-68250</guid>
    </item>
  </channel>
</rss>
