<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-04T07:44:42.625368+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2022-50466</id>
    <title>CVE-2022-50466 — fs/binfmt_elf: Fix memory leak in load_elf_binary()</title>
    <updated>2026-10-04T07:44:42.627915+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>fs/binfmt_elf: Fix memory leak in load_elf_binary()</p>
<p>There is a memory leak reported by kmemleak:</p>
<p>unreferenced object 0xffff88817104ef80 (size 224):
    comm "xfs_admin", pid 47165, jiffies 4298708825 (age 1333.476s)
    hex dump (first 32 bytes):
      00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
      60 a8 b3 00 81 88 ff ff a8 10 5a 00 81 88 ff ff  `.........Z.....
    backtrace:
      [&lt;ffffffff819171e1&gt;] __alloc_file+0x21/0x250
      [&lt;ffffffff81918061&gt;] alloc_empty_file+0x41/0xf0
      [&lt;ffffffff81948cda&gt;] path_openat+0xea/0x3d30
      [&lt;ffffffff8194ec89&gt;] do_filp_open+0x1b9/0x290
      [&lt;ffffffff8192660e&gt;] do_open_execat+0xce/0x5b0
      [&lt;ffffffff81926b17&gt;] open_exec+0x27/0x50
      [&lt;ffffffff81a69250&gt;] load_elf_binary+0x510/0x3ed0
      [&lt;ffffffff81927759&gt;] bprm_execve+0x599/0x1240
      [&lt;ffffffff8192a997&gt;] do_execveat_common.isra.0+0x4c7/0x680
      [&lt;ffffffff8192b078&gt;] __x64_sys_execve+0x88/0xb0
      [&lt;ffffffff83bbf0a5&gt;] do_syscall_64+0x35/0x80</p>
<p>If "interp_elf_ex" fails to allocate memory in load_elf_binary(),
the program will take the "out_free_ph" error handing path,
resulting in "interpreter" file resource is not released.</p>
<p>Fix it by adding an error handing path "out_free_file", which will
release the file resource when "interp_elf_ex" failed to allocate
memory.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2022-50466"/>
  </entry>
</feed>
