<?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>Thu, 01 Oct 2026 11:33:25 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-52936 — crypto: jitterentropy - replace long-held spinlock with mutex</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-52936</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;crypto: jitterentropy - replace long-held spinlock with mutex&lt;/p&gt;
&lt;p&gt;jent_kcapi_random() serializes the shared jitterentropy state, but it
currently holds a spinlock across the jent_read_entropy() call. That
path performs expensive jitter collection and SHA3 conditioning, so
parallel readers can trigger stalls as contending waiters spin for
the same lock.&lt;/p&gt;
&lt;p&gt;To prevent non-preemptible lock hold, replace rng-&amp;gt;jent_lock with a
mutex so contended readers sleep instead of spinning on a shared lock
held across expensive entropy generation.&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;crypto: jitterentropy - replace long-held spinlock with mutex&lt;/p&gt;
&lt;p&gt;jent_kcapi_random() serializes the shared jitterentropy state, but it
currently holds a spinlock across the jent_read_entropy() call. That
path performs expensive jitter collection and SHA3 conditioning, so
parallel readers can trigger stalls as contending waiters spin for
the same lock.&lt;/p&gt;
&lt;p&gt;To prevent non-preemptible lock hold, replace rng-&amp;gt;jent_lock with a
mutex so contended readers sleep instead of spinning on a shared lock
held across expensive entropy generation.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-52936</guid>
    </item>
  </channel>
</rss>
