<?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>Fri, 02 Oct 2026 10:35:37 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-36975 — KEYS: trusted: Do not use WARN when encode fails</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-36975</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;KEYS: trusted: Do not use WARN when encode fails&lt;/p&gt;
&lt;p&gt;When asn1_encode_sequence() fails, WARN is not the correct solution.&lt;/p&gt;
&lt;p&gt;1. asn1_encode_sequence() is not an internal function (located
   in lib/asn1_encode.c).
2. Location is known, which makes the stack trace useless.
3. Results a crash if panic_on_warn is set.&lt;/p&gt;
&lt;p&gt;It is also noteworthy that the use of WARN is undocumented, and it
should be avoided unless there is a carefully considered rationale to
use it.&lt;/p&gt;
&lt;p&gt;Replace WARN with pr_err, and print the return value instead, which is
only useful piece of information.&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;KEYS: trusted: Do not use WARN when encode fails&lt;/p&gt;
&lt;p&gt;When asn1_encode_sequence() fails, WARN is not the correct solution.&lt;/p&gt;
&lt;p&gt;1. asn1_encode_sequence() is not an internal function (located
   in lib/asn1_encode.c).
2. Location is known, which makes the stack trace useless.
3. Results a crash if panic_on_warn is set.&lt;/p&gt;
&lt;p&gt;It is also noteworthy that the use of WARN is undocumented, and it
should be avoided unless there is a carefully considered rationale to
use it.&lt;/p&gt;
&lt;p&gt;Replace WARN with pr_err, and print the return value instead, which is
only useful piece of information.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-36975</guid>
    </item>
  </channel>
</rss>
