CVE-2026-74486None▾ SunlitIn 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 de…
▾ Sunlit zone — Low / medium · no exploitation signal
impact 2.8 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake.
Exploit-prediction probability, daily snapshots since Nov 6.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
Last analysed / modified upstream
0.2%
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.
Linux >= 5b432413f7bbbc8b935138490a57be05c1921684 < c65eb018c12179b5e2c7afe1f0956298576fececLinux >= bb4715098d8e340bbbdd3a874b31f89867c8067e < 2bd860b7e752a51185960143cab9fec7bf32c84eLinux >= c152be5adc0975c75cc4f50891c9072d52d60b47 < eea4b7c7711b1e425272d23352af157f45f4c3e3Linux >= bf5ed2ef5cdb7b47ce606e3d48ea6eb803b31503 < 2fdf8b07bee5ef99ec77773a6be05fbb8ee5cdb9Linux >= 483217fd6f7ccd98b3ed2531a54f75ed144b4499 < f1e7ea3c8e070f19771cdaef55bbeda1359ad490Linux >= 0357ef03c94ef835bd44a0658b8edb672a9dbf51 < 255a758697da87a205e072e0cfc35897b8f743b1Linux >= 0357ef03c94ef835bd44a0658b8edb672a9dbf51 < f0edbaf487e4653a680a7abb91c1df94cb7886aaLinux >= 0357ef03c94ef835bd44a0658b8edb672a9dbf51 < fa5990ca8fd917003e526036bcc50413edb9722cLinux 6.14Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-99284Nonenet: skbuff: propagate shared-frag marker in skb_zerocopy()
CVE-2026-99283Nonenetfilter: conntrack: tcp: use UNACK timeout for non-closing RST packets
CVE-2026-99272Nonesmb: client: validate the data area in SMB2_read()
CVE-2026-99271NoneALSA: line6: Clear prev_fbuf on capture buffer release
CVE-2026-99273Noneksmbd: reserve space for the UTF-16 terminator in stream info
CVE-2026-99275Nonesmb: client: reject short SESSION_SETUP responses