<?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>Fri, 02 Oct 2026 17:51:56 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-74487 — binfmt_misc: restore write access when removing an entry</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-74487</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_misc: restore write access when removing an entry&lt;/p&gt;
&lt;p&gt;Registering an entry with the MISC_FMT_OPEN_FILE flag opens the
interpreter via open_exec() which denies write access to it for as
long as the entry exists. Removing the entry closes the interpreter
file via filp_close() but never restores write access, leaving the
inode&amp;#39;s i_writecount permanently negative. Opening the interpreter
for writing keeps failing with ETXTBSY long after the entry is gone
until the inode is evicted from the inode cache.&lt;/p&gt;
&lt;p&gt;Commit 90f601b497d7 (&amp;#34;binfmt_misc: restore write access before
closing files opened by open_exec()&amp;#34;) fixed the same imbalance in the
error path of bm_register_write() but the actual removal path has
been leaking the write denial since the introduction of the flag.&lt;/p&gt;
&lt;p&gt;Restore write access in put_binfmt_handler() before closing the
interpreter file.&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_misc: restore write access when removing an entry&lt;/p&gt;
&lt;p&gt;Registering an entry with the MISC_FMT_OPEN_FILE flag opens the
interpreter via open_exec() which denies write access to it for as
long as the entry exists. Removing the entry closes the interpreter
file via filp_close() but never restores write access, leaving the
inode&amp;#39;s i_writecount permanently negative. Opening the interpreter
for writing keeps failing with ETXTBSY long after the entry is gone
until the inode is evicted from the inode cache.&lt;/p&gt;
&lt;p&gt;Commit 90f601b497d7 (&amp;#34;binfmt_misc: restore write access before
closing files opened by open_exec()&amp;#34;) fixed the same imbalance in the
error path of bm_register_write() but the actual removal path has
been leaking the write denial since the introduction of the flag.&lt;/p&gt;
&lt;p&gt;Restore write access in put_binfmt_handler() before closing the
interpreter file.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-74487</guid>
    </item>
  </channel>
</rss>
