<?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>Thu, 08 Oct 2026 22:36:24 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-49890 — capabilities: fix potential memleak on error path from vfs_getxattr_alloc()</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2022-49890</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;capabilities: fix potential memleak on error path from vfs_getxattr_alloc()&lt;/p&gt;
&lt;p&gt;In cap_inode_getsecurity(), we will use vfs_getxattr_alloc() to
complete the memory allocation of tmpbuf, if we have completed
the memory allocation of tmpbuf, but failed to call handler-&amp;gt;get(...),
there will be a memleak in below logic:&lt;/p&gt;
&lt;p&gt;|-- ret = (int)vfs_getxattr_alloc(mnt_userns, ...)
    |           /* ^^^ alloc for tmpbuf */
    |-- value = krealloc(*xattr_value, error + 1, flags)
    |           /* ^^^ alloc memory */
    |-- error = handler-&amp;gt;get(handler, ...)
    |           /* error! */
    |-- *xattr_value = value
    |           /* xattr_value is &amp;amp;tmpbuf (memory leak!) */&lt;/p&gt;
&lt;p&gt;So we will try to free(tmpbuf) after vfs_getxattr_alloc() fails to fix it.&lt;/p&gt;
&lt;p&gt;[PM: subject line and backtrace tweaks]&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;capabilities: fix potential memleak on error path from vfs_getxattr_alloc()&lt;/p&gt;
&lt;p&gt;In cap_inode_getsecurity(), we will use vfs_getxattr_alloc() to
complete the memory allocation of tmpbuf, if we have completed
the memory allocation of tmpbuf, but failed to call handler-&amp;gt;get(...),
there will be a memleak in below logic:&lt;/p&gt;
&lt;p&gt;|-- ret = (int)vfs_getxattr_alloc(mnt_userns, ...)
    |           /* ^^^ alloc for tmpbuf */
    |-- value = krealloc(*xattr_value, error + 1, flags)
    |           /* ^^^ alloc memory */
    |-- error = handler-&amp;gt;get(handler, ...)
    |           /* error! */
    |-- *xattr_value = value
    |           /* xattr_value is &amp;amp;tmpbuf (memory leak!) */&lt;/p&gt;
&lt;p&gt;So we will try to free(tmpbuf) after vfs_getxattr_alloc() fails to fix it.&lt;/p&gt;
&lt;p&gt;[PM: subject line and backtrace tweaks]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2022-49890</guid>
    </item>
  </channel>
</rss>
