<?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:38:26 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-53491 — start_kernel: Add __no_stack_protector function attribute</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-53491</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;start_kernel: Add __no_stack_protector function attribute&lt;/p&gt;
&lt;p&gt;Back during the discussion of
commit a9a3ed1eff36 (&amp;#34;x86: Fix early boot crash on gcc-10, third try&amp;#34;)
we discussed the need for a function attribute to control the omission
of stack protectors on a per-function basis; at the time Clang had
support for no_stack_protector but GCC did not. This was fixed in
gcc-11. Now that the function attribute is available, let&amp;#39;s start using
it.&lt;/p&gt;
&lt;p&gt;Callers of boot_init_stack_canary need to use this function attribute
unless they&amp;#39;re compiled with -fno-stack-protector, otherwise the canary
stored in the stack slot of the caller will differ upon the call to
boot_init_stack_canary. This will lead to a call to __stack_chk_fail()
then panic.&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;start_kernel: Add __no_stack_protector function attribute&lt;/p&gt;
&lt;p&gt;Back during the discussion of
commit a9a3ed1eff36 (&amp;#34;x86: Fix early boot crash on gcc-10, third try&amp;#34;)
we discussed the need for a function attribute to control the omission
of stack protectors on a per-function basis; at the time Clang had
support for no_stack_protector but GCC did not. This was fixed in
gcc-11. Now that the function attribute is available, let&amp;#39;s start using
it.&lt;/p&gt;
&lt;p&gt;Callers of boot_init_stack_canary need to use this function attribute
unless they&amp;#39;re compiled with -fno-stack-protector, otherwise the canary
stored in the stack slot of the caller will differ upon the call to
boot_init_stack_canary. This will lead to a call to __stack_chk_fail()
then panic.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-53491</guid>
    </item>
  </channel>
</rss>
