CVE-2026-74486 — binfmt_misc: use exe_file_deny_write_access() for the interpreter clone
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 5b432413f7bbbc8b935138490a57be05c1921684 and < c65eb018c12179b5e2c7afe1f0956298576fecec≥ bb4715098d8e340bbbdd3a874b31f89867c8067e and < 2bd860b7e752a51185960143cab9fec7bf32c84e≥ c152be5adc0975c75cc4f50891c9072d52d60b47 and < eea4b7c7711b1e425272d23352af157f45f4c3e3≥ bf5ed2ef5cdb7b47ce606e3d48ea6eb803b31503 and < 2fdf8b07bee5ef99ec77773a6be05fbb8ee5cdb9≥ 483217fd6f7ccd98b3ed2531a54f75ed144b4499 and < f1e7ea3c8e070f19771cdaef55bbeda1359ad490≥ 0357ef03c94ef835bd44a0658b8edb672a9dbf51 and < 255a758697da87a205e072e0cfc35897b8f743b1≥ 0357ef03c94ef835bd44a0658b8edb672a9dbf51 and < f0edbaf487e4653a680a7abb91c1df94cb7886aa≥ 0357ef03c94ef835bd44a0658b8edb672a9dbf51 and < fa5990ca8fd917003e526036bcc50413edb9722c and 1 moreversion 6.14 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 29, 2026 · 14 reading(s) · max 0.18%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/eea4b7c7711b1e425272d23352af157f45f4c3e3
- git.kernel.org/stable/c/2fdf8b07bee5ef99ec77773a6be05fbb8ee5cdb9
- git.kernel.org/stable/c/f0edbaf487e4653a680a7abb91c1df94cb7886aa
- git.kernel.org/stable/c/255a758697da87a205e072e0cfc35897b8f743b1
- git.kernel.org/stable/c/2bd860b7e752a51185960143cab9fec7bf32c84e
- git.kernel.org/stable/c/c65eb018c12179b5e2c7afe1f0956298576fecec
- git.kernel.org/stable/c/fa5990ca8fd917003e526036bcc50413edb9722c
- git.kernel.org/stable/c/f1e7ea3c8e070f19771cdaef55bbeda1359ad490
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-99216 Drivers: hv: Don't reset VMBus connection state on error/exit paths 2d
- Unknown CVE-2026-99215 power: supply: core: prevent unregistering a power supply while a callback runs 2d
- Unknown CVE-2026-99207 scsi: target: Disable interrupts while holding delayed_cmd_lock 2d
- Unknown CVE-2026-99208 drm/xe/oa: Zero OA buffer at allocation 2d
- Unknown CVE-2026-99209 drm/xe: skip eviction of a BO with no resource 2d
- Unknown CVE-2026-99210 accel/rocket: clear rdev on device init failure 2d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-74486 is "binfmt_misc: use exe_file_deny_write_access() for the interpreter clone", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.18% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.