{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-74484 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-74484 is a denial of service vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-74484 and fix it if it is affected.\n\nWhat it is: CVE-2026-74484 is a denial of service vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-74484 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-74484/ (Markdown: https://insights.sbomify.com/CVE-2026-74484/index.md)","id":"CVE-2026-74484","markdown":"https://insights.sbomify.com/CVE-2026-74484/index.md","name":"CVE-2026-74484","record":{"aliases":["BELL-CVE-2026-74484","DEBIAN-CVE-2026-74484","GHSA-649r-6xhp-rm3w","UBUNTU-CVE-2026-74484"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A local attacker can cause a denial of service and resource leak in the Linux kernel by registering a binfmt_misc entry that pins its own instance.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nbinfmt_misc: don't let an 'F' entry pin its own instance\n\nAn entry registered with 'F' opens its interpreter at registration time\nand holds that file until the entry is freed. Any entry nobody removes\nby hand only gets closed once the binfmt_misc superblock is shut down.\nIf the interpreter lives on a mount that keeps that superblock alive the\ntwo pin each other:\n\n    binfmt_misc sb -\u003e inode -\u003e entry -\u003e interp_file -\u003e vfsmount -\u003e binfmt_misc sb\n\nTL;DR the file is never closed. Once the mount namespace is gone there\nis nothing left to unregister through either.\n\nThere are two ways to trigger this bug:\n\n- Point the interpreter at the instance itself. Its files are regular\n  files owned by the mounter and both bm_get_inode() and\n  simple_fill_super() leave i_op at empty_iops. So notify_change() falls\n  back to simple_setattr() and chmod +x works. We never set SB_I_NOEXEC\n  and so open_exec() accepts it.\n\n- Use the instance as an overlayfs lower layer. The overlay superblock\n  holds a clone_private_mount() of every layer until it is destroyed and\n  that clone is in no namespace. So umount_tree() never reaches it.\n\nThat's a DoS. And it isn't only the superblock that leaks. It pins the\nuser namespace it was mounted in, so every iteration permanently eats\none of the caller's user namespace charges.\n\nSo let's just do the sane thing. SB_I_NOEXEC makes open_exec() fail on\nthe instance's own files and s_stack_depth makes overlayfs reject the\nlayer before it ever takes a clone. That also covers the ecryptfs and\nfuse passthrough variants. What 'F' promises is unchanged.\n\nThe stable tag is narrower than the Fixes tags on purpose. Before\nsandboxed mounts this needed global root against the single instance\neveryone shares, and the change doesn't apply to those trees anyway.\n\nNote that SB_I_NODEV is implicitly raised for userns mounts but raise it\nexplicitly here as well.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"binfmt_misc: don't let an 'F' entry pin its own instance","id":"CVE-2026-74484","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"binfmt_misc: reject a flag character as the field delimiter","id":"CVE-2026-74485"},"packages":[],"prev":{"headline":"binfmt_misc: don't leak the user namespace when the mount fails","id":"CVE-2026-74483"},"products":["Linux"],"published":"2026-08-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-08-19","vendors":["Linux"]},"summary":"A local attacker can cause a denial of service and resource leak in the Linux kernel by registering a binfmt_misc entry that pins its own instance.","url":"https://insights.sbomify.com/CVE-2026-74484/"}