<?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 12:15:27 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-49878 — bpf, verifier: Fix memory leak in array reallocation for stack state</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2022-49878</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;bpf, verifier: Fix memory leak in array reallocation for stack state&lt;/p&gt;
&lt;p&gt;If an error (NULL) is returned by krealloc(), callers of realloc_array()
were setting their allocation pointers to NULL, but on error krealloc()
does not touch the original allocation. This would result in a memory
resource leak. Instead, free the old allocation on the error handling
path.&lt;/p&gt;
&lt;p&gt;The memory leak information is as follows as also reported by Zhengchao:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff888019801800 (size 256):
  comm &amp;#34;bpf_repo&amp;#34;, pid 6490, jiffies 4294959200 (age 17.170s)
  hex dump (first 32 bytes):
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace:
    [&amp;lt;00000000b211474b&amp;gt;] __kmalloc_node_track_caller+0x45/0xc0
    [&amp;lt;0000000086712a0b&amp;gt;] krealloc+0x83/0xd0
    [&amp;lt;00000000139aab02&amp;gt;] realloc_array+0x82/0xe2
    [&amp;lt;00000000b1ca41d1&amp;gt;] grow_stack_state+0xfb/0x186
    [&amp;lt;00000000cd6f36d2&amp;gt;] check_mem_access.cold+0x141/0x1341
    [&amp;lt;0000000081780455&amp;gt;] do_check_common+0x5358/0xb350
    [&amp;lt;0000000015f6b091&amp;gt;] bpf_check.cold+0xc3/0x29d
    [&amp;lt;000000002973c690&amp;gt;] bpf_prog_load+0x13db/0x2240
    [&amp;lt;00000000028d1644&amp;gt;] __sys_bpf+0x1605/0x4ce0
    [&amp;lt;00000000053f29bd&amp;gt;] __x64_sys_bpf+0x75/0xb0
    [&amp;lt;0000000056fedaf5&amp;gt;] do_syscall_64+0x35/0x80
    [&amp;lt;000000002bd58261&amp;gt;] entry_SYSCALL_64_after_hwframe+0x63/0xcd&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;bpf, verifier: Fix memory leak in array reallocation for stack state&lt;/p&gt;
&lt;p&gt;If an error (NULL) is returned by krealloc(), callers of realloc_array()
were setting their allocation pointers to NULL, but on error krealloc()
does not touch the original allocation. This would result in a memory
resource leak. Instead, free the old allocation on the error handling
path.&lt;/p&gt;
&lt;p&gt;The memory leak information is as follows as also reported by Zhengchao:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff888019801800 (size 256):
  comm &amp;#34;bpf_repo&amp;#34;, pid 6490, jiffies 4294959200 (age 17.170s)
  hex dump (first 32 bytes):
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace:
    [&amp;lt;00000000b211474b&amp;gt;] __kmalloc_node_track_caller+0x45/0xc0
    [&amp;lt;0000000086712a0b&amp;gt;] krealloc+0x83/0xd0
    [&amp;lt;00000000139aab02&amp;gt;] realloc_array+0x82/0xe2
    [&amp;lt;00000000b1ca41d1&amp;gt;] grow_stack_state+0xfb/0x186
    [&amp;lt;00000000cd6f36d2&amp;gt;] check_mem_access.cold+0x141/0x1341
    [&amp;lt;0000000081780455&amp;gt;] do_check_common+0x5358/0xb350
    [&amp;lt;0000000015f6b091&amp;gt;] bpf_check.cold+0xc3/0x29d
    [&amp;lt;000000002973c690&amp;gt;] bpf_prog_load+0x13db/0x2240
    [&amp;lt;00000000028d1644&amp;gt;] __sys_bpf+0x1605/0x4ce0
    [&amp;lt;00000000053f29bd&amp;gt;] __x64_sys_bpf+0x75/0xb0
    [&amp;lt;0000000056fedaf5&amp;gt;] do_syscall_64+0x35/0x80
    [&amp;lt;000000002bd58261&amp;gt;] entry_SYSCALL_64_after_hwframe+0x63/0xcd&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2022-49878</guid>
    </item>
  </channel>
</rss>
