{"api_version":"1","generated_at":"2026-08-22T06:26:42+00:00","cve":"CVE-2026-74486","urls":{"html":"https://cve.report/CVE-2026-74486","api":"https://cve.report/api/cve/CVE-2026-74486.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-74486","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-74486"},"summary":{"title":"binfmt_misc: use exe_file_deny_write_access() for the interpreter clone","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nbinfmt_misc: use exe_file_deny_write_access() for the interpreter clone\n\nFor MISC_FMT_OPEN_FILE entries load_misc_binary() clones the\nregistered interpreter file and denies write access to the clone via\nplain deny_write_access(). The clone is installed as\nbprm->interpreter and later released by the exec machinery through\nexe_file_allow_write_access() which skips the i_writecount increment\nfor files with FMODE_FSNOTIFY_HSM set.\n\nThe deny and allow side can therefore come to different conclusions\nwhen pre-content watches are in play: if a pre-content watch is added\nto the interpreter after registration every subsequent exec through\nthat entry takes a write denial on the clone that is never paired\nwith a write allowance, driving the interpreter inode's i_writecount\nfurther down with each exec and leaving the interpreter unwritable\neven after the entry and all its users are gone.\n\nTake the write denial via exe_file_deny_write_access() so both sides\nof the pairing base their decision on the same file mode, and\npropagate failure instead of silently ignoring it: an interpreter\nthat is concurrently open for writing now fails the exec with\nETXTBSY, exactly like an interpreter freshly opened via open_exec()\nwould.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-08-15 13:17:53","updated_at":"2026-08-17 06:19:44"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/fa5990ca8fd917003e526036bcc50413edb9722c","name":"https://git.kernel.org/stable/c/fa5990ca8fd917003e526036bcc50413edb9722c","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/f0edbaf487e4653a680a7abb91c1df94cb7886aa","name":"https://git.kernel.org/stable/c/f0edbaf487e4653a680a7abb91c1df94cb7886aa","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/255a758697da87a205e072e0cfc35897b8f743b1","name":"https://git.kernel.org/stable/c/255a758697da87a205e072e0cfc35897b8f743b1","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-74486","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74486","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 0357ef03c94ef835bd44a0658b8edb672a9dbf51 255a758697da87a205e072e0cfc35897b8f743b1 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 0357ef03c94ef835bd44a0658b8edb672a9dbf51 f0edbaf487e4653a680a7abb91c1df94cb7886aa git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 0357ef03c94ef835bd44a0658b8edb672a9dbf51 fa5990ca8fd917003e526036bcc50413edb9722c git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.14","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.14 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 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"74486","cve":"CVE-2026-74486","epss":"0.001660000","percentile":"0.063180000","score_date":"2026-08-17","updated_at":"2026-08-18 00:11:46"},"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":"255a758697da87a205e072e0cfc35897b8f743b1","status":"affected","version":"0357ef03c94ef835bd44a0658b8edb672a9dbf51","versionType":"git"},{"lessThan":"f0edbaf487e4653a680a7abb91c1df94cb7886aa","status":"affected","version":"0357ef03c94ef835bd44a0658b8edb672a9dbf51","versionType":"git"},{"lessThan":"fa5990ca8fd917003e526036bcc50413edb9722c","status":"affected","version":"0357ef03c94ef835bd44a0658b8edb672a9dbf51","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":"6.14"},{"lessThan":"6.14","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","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.44","versionStartIncluding":"6.14","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1.8","versionStartIncluding":"6.14","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2","versionStartIncluding":"6.14","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nbinfmt_misc: use exe_file_deny_write_access() for the interpreter clone\n\nFor MISC_FMT_OPEN_FILE entries load_misc_binary() clones the\nregistered interpreter file and denies write access to the clone via\nplain deny_write_access(). The clone is installed as\nbprm->interpreter and later released by the exec machinery through\nexe_file_allow_write_access() which skips the i_writecount increment\nfor files with FMODE_FSNOTIFY_HSM set.\n\nThe deny and allow side can therefore come to different conclusions\nwhen pre-content watches are in play: if a pre-content watch is added\nto the interpreter after registration every subsequent exec through\nthat entry takes a write denial on the clone that is never paired\nwith a write allowance, driving the interpreter inode's i_writecount\nfurther down with each exec and leaving the interpreter unwritable\neven after the entry and all its users are gone.\n\nTake the write denial via exe_file_deny_write_access() so both sides\nof the pairing base their decision on the same file mode, and\npropagate failure instead of silently ignoring it: an interpreter\nthat is concurrently open for writing now fails the exec with\nETXTBSY, exactly like an interpreter freshly opened via open_exec()\nwould."}],"providerMetadata":{"dateUpdated":"2026-08-17T05:20:19.915Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/255a758697da87a205e072e0cfc35897b8f743b1"},{"url":"https://git.kernel.org/stable/c/f0edbaf487e4653a680a7abb91c1df94cb7886aa"},{"url":"https://git.kernel.org/stable/c/fa5990ca8fd917003e526036bcc50413edb9722c"}],"title":"binfmt_misc: use exe_file_deny_write_access() for the interpreter clone","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-74486","datePublished":"2026-08-15T12:27:17.609Z","dateReserved":"2026-08-15T05:44:03.905Z","dateUpdated":"2026-08-17T05:20:19.915Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-08-15 13:17:53","lastModifiedDate":"2026-08-17 06:19:44","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"74486","Ordinal":"1","Title":"binfmt_misc: use exe_file_deny_write_access() for the interprete","CVE":"CVE-2026-74486","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"74486","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nbinfmt_misc: use exe_file_deny_write_access() for the interpreter clone\n\nFor MISC_FMT_OPEN_FILE entries load_misc_binary() clones the\nregistered interpreter file and denies write access to the clone via\nplain deny_write_access(). The clone is installed as\nbprm->interpreter and later released by the exec machinery through\nexe_file_allow_write_access() which skips the i_writecount increment\nfor files with FMODE_FSNOTIFY_HSM set.\n\nThe deny and allow side can therefore come to different conclusions\nwhen pre-content watches are in play: if a pre-content watch is added\nto the interpreter after registration every subsequent exec through\nthat entry takes a write denial on the clone that is never paired\nwith a write allowance, driving the interpreter inode's i_writecount\nfurther down with each exec and leaving the interpreter unwritable\neven after the entry and all its users are gone.\n\nTake the write denial via exe_file_deny_write_access() so both sides\nof the pairing base their decision on the same file mode, and\npropagate failure instead of silently ignoring it: an interpreter\nthat is concurrently open for writing now fails the exec with\nETXTBSY, exactly like an interpreter freshly opened via open_exec()\nwould.","Type":"Description","Title":"binfmt_misc: use exe_file_deny_write_access() for the interprete"}]}}}