CVE-2026-74486

published 15 Aug 2026 · updated 8 Nov 2026

binfmt_misc: use exe_file_deny_write_access() for the interpreter clone

5.0MediumEPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel eea4b7c7711b1e425272d23352af157f45f4c3e3, Kernel 2bd860b7e752a51185960143cab9fec7bf32c84e, Kernel 2fdf8b07bee5ef99ec77773a6be05fbb8ee5cdb9 and 7 more.

In the Linux kernel, the following vulnerability has been resolved: binfmt_misc: use exe_file_deny_write_access() for the interpreter clone For MISC_FMT_OPEN_FILE entries load_misc_binary() clones the registered interpreter file and denies write access to the clone via plain deny_write_access(). The clone is installed as bprm->interpreter and later released by the exec machinery through exe_file_allow_write_access() which skips the i_writecount increment for files with FMODE_FSNOTIFY_HSM set. The deny and allow side can therefore come to different conclusions when pre-content watches are in play: if a pre-content watch is added to the interpreter after registration every subsequent exec through that entry takes a write denial on the clone that is never paired with a write allowance, driving the interpreter inode's i_writecount further down with each exec and leaving the interpreter unwritable even after the entry and all its users are gone. Take the write denial via exe_file_deny_write_access() so both sides of the pairing base their decision on the same file mode, and propagate failure instead of silently ignoring it: an interpreter that is concurrently open for writing now fails the exec with ETXTBSY, exactly like an interpreter freshly opened via open_exec() would.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=c152be5adc0975c75cc4f50891c9072d52d60b47 <eea4b7c7711b1e425272d23352af157f45f4c3e3, >=bb4715098d8e340bbbdd3a874b31f89867c8067e <2bd860b7e752a51185960143cab9fec7bf32c84e, >=bf5ed2ef5cdb7b47ce606e3d48ea6eb803b31503 <2fdf8b07bee5ef99ec77773a6be05fbb8ee5cdb9, =6.14, >=0357ef03c94ef835bd44a0658b8edb672a9dbf51 <255a758697da87a205e072e0cfc35897b8f743b1, >=0357ef03c94ef835bd44a0658b8edb672a9dbf51 <f0edbaf487e4653a680a7abb91c1df94cb7886aa, >=0357ef03c94ef835bd44a0658b8edb672a9dbf51 <fa5990ca8fd917003e526036bcc50413edb9722c, >=483217fd6f7ccd98b3ed2531a54f75ed144b4499 <f1e7ea3c8e070f19771cdaef55bbeda1359ad490, >=5b432413f7bbbc8b935138490a57be05c1921684 <c65eb018c12179b5e2c7afe1f0956298576fececeea4b7c7711b1e425272d23352af157f45f4c3e3, 2bd860b7e752a51185960143cab9fec7bf32c84e, 2fdf8b07bee5ef99ec77773a6be05fbb8ee5cdb9, 255a758697da87a205e072e0cfc35897b8f743b1, f0edbaf487e4653a680a7abb91c1df94cb7886aa, fa5990ca8fd917003e526036bcc50413edb9722c, f1e7ea3c8e070f19771cdaef55bbeda1359ad490, c65eb018c12179b5e2c7afe1f0956298576fecec
linux-kernel: Kernel>=6.19.0 <7.1.8, >=6.14.0 <6.18.447.1.8, 6.18.44

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-74486 severity on Zeptric[![CVE-2026-74486](https://zeptric.io/badge/cve/CVE-2026-74486.svg)](https://zeptric.io/cve/CVE-2026-74486)