<?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>Thu, 01 Oct 2026 13:55:05 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-68151 — binfmt_elf_fdpic: only honour the first PT_INTERP</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-68151</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;binfmt_elf_fdpic: only honour the first PT_INTERP&lt;/p&gt;
&lt;p&gt;The program header scan handles PT_INTERP from a switch nested in the
scan loop, so its break leaves the switch and not the loop. A binary
carrying more than one PT_INTERP runs the case again and overwrites both
interpreter_name and interpreter. The previous name allocation leaks and
so does the previous interpreter reference, along with the write denial
open_exec() took on it. The denial is never released, so the file stays
unwritable for as long as the system runs.&lt;/p&gt;
&lt;p&gt;An unprivileged caller reaches this with a crafted binary and repeats it
at will. binfmt_elf stops at the first PT_INTERP. Do the same here.&lt;/p&gt;
&lt;p&gt;The flaw dates back to the driver&amp;#39;s introduction in the pre-git history
tree introduced in v2.6.11 by 91808d6ebe39 (&amp;#34;[PATCH] FRV: Add FDPIC ELF
binary format driver&amp;#34;).&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;binfmt_elf_fdpic: only honour the first PT_INTERP&lt;/p&gt;
&lt;p&gt;The program header scan handles PT_INTERP from a switch nested in the
scan loop, so its break leaves the switch and not the loop. A binary
carrying more than one PT_INTERP runs the case again and overwrites both
interpreter_name and interpreter. The previous name allocation leaks and
so does the previous interpreter reference, along with the write denial
open_exec() took on it. The denial is never released, so the file stays
unwritable for as long as the system runs.&lt;/p&gt;
&lt;p&gt;An unprivileged caller reaches this with a crafted binary and repeats it
at will. binfmt_elf stops at the first PT_INTERP. Do the same here.&lt;/p&gt;
&lt;p&gt;The flaw dates back to the driver&amp;#39;s introduction in the pre-git history
tree introduced in v2.6.11 by 91808d6ebe39 (&amp;#34;[PATCH] FRV: Add FDPIC ELF
binary format driver&amp;#34;).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-68151</guid>
    </item>
  </channel>
</rss>
