<?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://cve.radiocsirt.org</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, 07 Oct 2026 07:00:03 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-49675 — tick/nohz: unexport __init-annotated tick_nohz_full_setup()</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2022-49675</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;tick/nohz: unexport __init-annotated tick_nohz_full_setup()&lt;/p&gt;
&lt;p&gt;EXPORT_SYMBOL and __init is a bad combination because the .init.text
section is freed up after the initialization. Hence, modules cannot
use symbols annotated __init. The access to a freed symbol may end up
with kernel panic.&lt;/p&gt;
&lt;p&gt;modpost used to detect it, but it had been broken for a decade.&lt;/p&gt;
&lt;p&gt;Commit 28438794aba4 (&amp;#34;modpost: fix section mismatch check for exported
init/exit sections&amp;#34;) fixed it so modpost started to warn it again, then
this showed up:&lt;/p&gt;
&lt;p&gt;MODPOST vmlinux.symvers
  WARNING: modpost: vmlinux.o(___ksymtab_gpl+tick_nohz_full_setup+0x0): Section mismatch in reference from the variable __ksymtab_tick_nohz_full_setup to the function .init.text:tick_nohz_full_setup()
  The symbol tick_nohz_full_setup is exported and annotated __init
  Fix this by removing the __init annotation of tick_nohz_full_setup or drop the export.&lt;/p&gt;
&lt;p&gt;Drop the export because tick_nohz_full_setup() is only called from the
built-in code in kernel/sched/isolation.c.&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;tick/nohz: unexport __init-annotated tick_nohz_full_setup()&lt;/p&gt;
&lt;p&gt;EXPORT_SYMBOL and __init is a bad combination because the .init.text
section is freed up after the initialization. Hence, modules cannot
use symbols annotated __init. The access to a freed symbol may end up
with kernel panic.&lt;/p&gt;
&lt;p&gt;modpost used to detect it, but it had been broken for a decade.&lt;/p&gt;
&lt;p&gt;Commit 28438794aba4 (&amp;#34;modpost: fix section mismatch check for exported
init/exit sections&amp;#34;) fixed it so modpost started to warn it again, then
this showed up:&lt;/p&gt;
&lt;p&gt;MODPOST vmlinux.symvers
  WARNING: modpost: vmlinux.o(___ksymtab_gpl+tick_nohz_full_setup+0x0): Section mismatch in reference from the variable __ksymtab_tick_nohz_full_setup to the function .init.text:tick_nohz_full_setup()
  The symbol tick_nohz_full_setup is exported and annotated __init
  Fix this by removing the __init annotation of tick_nohz_full_setup or drop the export.&lt;/p&gt;
&lt;p&gt;Drop the export because tick_nohz_full_setup() is only called from the
built-in code in kernel/sched/isolation.c.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2022-49675</guid>
    </item>
  </channel>
</rss>
