Description
In the Linux kernel, the following vulnerability has been resolved:

binfmt_misc: don't let an 'F' entry pin its own instance

An entry registered with 'F' opens its interpreter at registration time
and holds that file until the entry is freed. Any entry nobody removes
by hand only gets closed once the binfmt_misc superblock is shut down.
If the interpreter lives on a mount that keeps that superblock alive the
two pin each other:

binfmt_misc sb -> inode -> entry -> interp_file -> vfsmount -> binfmt_misc sb

TL;DR the file is never closed. Once the mount namespace is gone there
is nothing left to unregister through either.

There are two ways to trigger this bug:

- Point the interpreter at the instance itself. Its files are regular
files owned by the mounter and both bm_get_inode() and
simple_fill_super() leave i_op at empty_iops. So notify_change() falls
back to simple_setattr() and chmod +x works. We never set SB_I_NOEXEC
and so open_exec() accepts it.

- Use the instance as an overlayfs lower layer. The overlay superblock
holds a clone_private_mount() of every layer until it is destroyed and
that clone is in no namespace. So umount_tree() never reaches it.

That's a DoS. And it isn't only the superblock that leaks. It pins the
user namespace it was mounted in, so every iteration permanently eats
one of the caller's user namespace charges.

So let's just do the sane thing. SB_I_NOEXEC makes open_exec() fail on
the instance's own files and s_stack_depth makes overlayfs reject the
layer before it ever takes a clone. That also covers the ecryptfs and
fuse passthrough variants. What 'F' promises is unchanged.

The stable tag is narrower than the Fixes tags on purpose. Before
sandboxed mounts this needed global root against the single instance
everyone shares, and the change doesn't apply to those trees anyway.

Note that SB_I_NODEV is implicitly raised for userns mounts but raise it
explicitly here as well.
Published: 2026-08-15
Score: 5.5 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability arises when a binfmt_misc entry registered with the flag 'F' keeps its interpreter file open for the life of the superblock, leading to a resource leak that matches the definition of CWE-911. This persistent pinning of the interpreter holds the superblock, which in turn pins the mount namespace, so the file is never closed. Based on the description, it is inferred that an attacker can trigger the bug by creating such an entry, which typically requires local privileged access to register a binfmt_misc entry, and that the effect is a denial of service caused by exhausting mount namespace and inode table resources.

Affected Systems

Linux kernel versions prior to the patch, across all vendor distributions that include binfmt_misc and allow registration of an interpreter with the 'F' flag, are affected. The issue is present in any environment where the interpreter lives on a mount that keeps that superblock alive, such as user namespaces or overlayfs layers. All users of such kernel variants where binfmt_misc is enabled can potentially be impacted.

Risk and Exploitability

The risk is moderate with a CVSS score of 5.5, but the EPSS score is reported as less than 1% and the vulnerability is not listed in the CISA KEV catalog, indicating that active exploitation is unlikely. However, since the attack vector is inferred to be local and the privilege required to create a binfmt_misc entry is typically root or equivalent, the severity remains significant if the environment allows privileged local users to register such entries. Therefore, the vulnerability can lead to a denial of service by continuously consuming mount namespace and inode resources, potentially bringing the system to an unresponsive state.

Generated by OpenCVE AI on August 21, 2026 at 23:27 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Update the Linux kernel to a version that includes the patch removing the 'F' entry susceptibility to self‑pinning.
  • Configure binfmt_misc entries with the noexec flag to prevent executables from opening their interpreter during registration, thereby mitigating resource leakage.
  • Avoid using overlayfs layers that reference the problematic binfmt_misc instance until the kernel fix is applied.
  • Restart affected services or reboot the system to clear lingering pinned references if an immediate kernel update is not possible.

Generated by OpenCVE AI on August 21, 2026 at 23:27 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Debian DSA Debian DSA DSA-6466-1 linux security update
History

Fri, 21 Aug 2026 21:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-400

Fri, 21 Aug 2026 12:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-911
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Moderate


Sat, 15 Aug 2026 14:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-400

Sat, 15 Aug 2026 12:45:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: binfmt_misc: don't let an 'F' entry pin its own instance An entry registered with 'F' opens its interpreter at registration time and holds that file until the entry is freed. Any entry nobody removes by hand only gets closed once the binfmt_misc superblock is shut down. If the interpreter lives on a mount that keeps that superblock alive the two pin each other: binfmt_misc sb -> inode -> entry -> interp_file -> vfsmount -> binfmt_misc sb TL;DR the file is never closed. Once the mount namespace is gone there is nothing left to unregister through either. There are two ways to trigger this bug: - Point the interpreter at the instance itself. Its files are regular files owned by the mounter and both bm_get_inode() and simple_fill_super() leave i_op at empty_iops. So notify_change() falls back to simple_setattr() and chmod +x works. We never set SB_I_NOEXEC and so open_exec() accepts it. - Use the instance as an overlayfs lower layer. The overlay superblock holds a clone_private_mount() of every layer until it is destroyed and that clone is in no namespace. So umount_tree() never reaches it. That's a DoS. And it isn't only the superblock that leaks. It pins the user namespace it was mounted in, so every iteration permanently eats one of the caller's user namespace charges. So let's just do the sane thing. SB_I_NOEXEC makes open_exec() fail on the instance's own files and s_stack_depth makes overlayfs reject the layer before it ever takes a clone. That also covers the ecryptfs and fuse passthrough variants. What 'F' promises is unchanged. The stable tag is narrower than the Fixes tags on purpose. Before sandboxed mounts this needed global root against the single instance everyone shares, and the change doesn't apply to those trees anyway. Note that SB_I_NODEV is implicitly raised for userns mounts but raise it explicitly here as well.
Title binfmt_misc: don't let an 'F' entry pin its own instance
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-08-19T06:52:35.407Z

Reserved: 2026-08-15T05:44:03.904Z

Link: CVE-2026-74484

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-15T13:17:53.270

Modified: 2026-08-19T07:16:55.913

Link: CVE-2026-74484

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-08-15T00:00:00Z

Links: CVE-2026-74484 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-08-21T23:30:17Z

Weaknesses
  • CWE-911

    Improper Update of Reference Count