{"api_version":"1","generated_at":"2026-08-15T15:12:02+00:00","cve":"CVE-2026-74487","urls":{"html":"https://cve.report/CVE-2026-74487","api":"https://cve.report/api/cve/CVE-2026-74487.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-74487","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-74487"},"summary":{"title":"binfmt_misc: restore write access when removing an entry","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nbinfmt_misc: restore write access when removing an entry\n\nRegistering an entry with the MISC_FMT_OPEN_FILE flag opens the\ninterpreter via open_exec() which denies write access to it for as\nlong as the entry exists. Removing the entry closes the interpreter\nfile via filp_close() but never restores write access, leaving the\ninode's i_writecount permanently negative. Opening the interpreter\nfor writing keeps failing with ETXTBSY long after the entry is gone\nuntil the inode is evicted from the inode cache.\n\nCommit 90f601b497d7 (\"binfmt_misc: restore write access before\nclosing files opened by open_exec()\") fixed the same imbalance in the\nerror path of bm_register_write() but the actual removal path has\nbeen leaking the write denial since the introduction of the flag.\n\nRestore write access in put_binfmt_handler() before closing the\ninterpreter file.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-08-15 13:17:53","updated_at":"2026-08-15 13:17:53"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/db1856ea9196cf6e015d12199a34c0b9313c7bfa","name":"https://git.kernel.org/stable/c/db1856ea9196cf6e015d12199a34c0b9313c7bfa","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/fdc1d702bf3001586221fa07e598e876a0a854c5","name":"https://git.kernel.org/stable/c/fdc1d702bf3001586221fa07e598e876a0a854c5","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/3b522487a3a9162b1b519eefde7998d103e3e07b","name":"https://git.kernel.org/stable/c/3b522487a3a9162b1b519eefde7998d103e3e07b","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-74487","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74487","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 948b701a607f123df92ed29084413e5dd8cda2ed fdc1d702bf3001586221fa07e598e876a0a854c5 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 948b701a607f123df92ed29084413e5dd8cda2ed 3b522487a3a9162b1b519eefde7998d103e3e07b git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 948b701a607f123df92ed29084413e5dd8cda2ed db1856ea9196cf6e015d12199a34c0b9313c7bfa git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 4.8","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 4.8 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.44 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1.8 7.1.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2-rc6 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["fs/binfmt_misc.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"fdc1d702bf3001586221fa07e598e876a0a854c5","status":"affected","version":"948b701a607f123df92ed29084413e5dd8cda2ed","versionType":"git"},{"lessThan":"3b522487a3a9162b1b519eefde7998d103e3e07b","status":"affected","version":"948b701a607f123df92ed29084413e5dd8cda2ed","versionType":"git"},{"lessThan":"db1856ea9196cf6e015d12199a34c0b9313c7bfa","status":"affected","version":"948b701a607f123df92ed29084413e5dd8cda2ed","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["fs/binfmt_misc.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"4.8"},{"lessThan":"4.8","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.44","versionType":"semver"},{"lessThanOrEqual":"7.1.*","status":"unaffected","version":"7.1.8","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.2-rc6","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.44","versionStartIncluding":"4.8","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1.8","versionStartIncluding":"4.8","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2-rc6","versionStartIncluding":"4.8","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nbinfmt_misc: restore write access when removing an entry\n\nRegistering an entry with the MISC_FMT_OPEN_FILE flag opens the\ninterpreter via open_exec() which denies write access to it for as\nlong as the entry exists. Removing the entry closes the interpreter\nfile via filp_close() but never restores write access, leaving the\ninode's i_writecount permanently negative. Opening the interpreter\nfor writing keeps failing with ETXTBSY long after the entry is gone\nuntil the inode is evicted from the inode cache.\n\nCommit 90f601b497d7 (\"binfmt_misc: restore write access before\nclosing files opened by open_exec()\") fixed the same imbalance in the\nerror path of bm_register_write() but the actual removal path has\nbeen leaking the write denial since the introduction of the flag.\n\nRestore write access in put_binfmt_handler() before closing the\ninterpreter file."}],"providerMetadata":{"dateUpdated":"2026-08-15T12:27:18.236Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/fdc1d702bf3001586221fa07e598e876a0a854c5"},{"url":"https://git.kernel.org/stable/c/3b522487a3a9162b1b519eefde7998d103e3e07b"},{"url":"https://git.kernel.org/stable/c/db1856ea9196cf6e015d12199a34c0b9313c7bfa"}],"title":"binfmt_misc: restore write access when removing an entry","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-74487","datePublished":"2026-08-15T12:27:18.236Z","dateReserved":"2026-08-15T05:44:03.905Z","dateUpdated":"2026-08-15T12:27:18.236Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-08-15 13:17:53","lastModifiedDate":"2026-08-15 13:17:53","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"74487","Ordinal":"1","Title":"binfmt_misc: restore write access when removing an entry","CVE":"CVE-2026-74487","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"74487","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nbinfmt_misc: restore write access when removing an entry\n\nRegistering an entry with the MISC_FMT_OPEN_FILE flag opens the\ninterpreter via open_exec() which denies write access to it for as\nlong as the entry exists. Removing the entry closes the interpreter\nfile via filp_close() but never restores write access, leaving the\ninode's i_writecount permanently negative. Opening the interpreter\nfor writing keeps failing with ETXTBSY long after the entry is gone\nuntil the inode is evicted from the inode cache.\n\nCommit 90f601b497d7 (\"binfmt_misc: restore write access before\nclosing files opened by open_exec()\") fixed the same imbalance in the\nerror path of bm_register_write() but the actual removal path has\nbeen leaking the write denial since the introduction of the flag.\n\nRestore write access in put_binfmt_handler() before closing the\ninterpreter file.","Type":"Description","Title":"binfmt_misc: restore write access when removing an entry"}]}}}