CVE-2026-74486binfmt_misc: use exe_file_deny_write_access() for the interpreter clone
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- Not yet scored
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Aug 23, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from 5b432413f7bbbc8b935138490a57be05c1921684 before c65eb018c12179b5e2c7afe1f0956298576fecec; from bb4715098d8e340bbbdd3a874b31f89867c8067e before 2bd860b7e752a51185960143cab9fec7bf32c84e; from c152be5adc0975c75cc4f50891c9072d52d60b47 before eea4b7c7711b1e425272d23352af157f45f4c3e3; from bf5ed2ef5cdb7b47ce606e3d48ea6eb803b31503 before 2fdf8b07bee5ef99ec77773a6be05fbb8ee5cdb9; from 483217fd6f7ccd98b3ed2531a54f75ed144b4499 before f1e7ea3c8e070f19771cdaef55bbeda1359ad490; 0357ef03c94ef835bd44a0658b8edb672a9dbf51 builds before 255a758697da87a205e072e0cfc35897b8f743b1; from 0357ef03c94ef835bd44a0658b8edb672a9dbf51 before f0edbaf487e4653a680a7abb91c1df94cb7886aa; from 0357ef03c94ef835bd44a0658b8edb672a9dbf51 before fa5990ca8fd917003e526036bcc50413edb9722c | CNA record |
References
- https://git.kernel.org/stable/c/c65eb018c12179b5e2c7afe1f0956298576fecec
- https://git.kernel.org/stable/c/2bd860b7e752a51185960143cab9fec7bf32c84e
- https://git.kernel.org/stable/c/eea4b7c7711b1e425272d23352af157f45f4c3e3
- https://git.kernel.org/stable/c/2fdf8b07bee5ef99ec77773a6be05fbb8ee5cdb9
- https://git.kernel.org/stable/c/f1e7ea3c8e070f19771cdaef55bbeda1359ad490
- https://git.kernel.org/stable/c/255a758697da87a205e072e0cfc35897b8f743b1
- https://git.kernel.org/stable/c/f0edbaf487e4653a680a7abb91c1df94cb7886aa
- https://git.kernel.org/stable/c/fa5990ca8fd917003e526036bcc50413edb9722c
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.