CVE-2026-74486: binfmt_misc: use exe_file_deny_write_access() for the interpreter clone
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Fixed version: Linux Linux 255a758697da87a205e072e0cfc35897b8f743b1, 2bd860b7e752a51185960143cab9fec7bf32c84e, 2fdf8b07bee5ef99ec77773a6be05fbb8ee5cdb9.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 255a758697da87a205e072e0cfc35897b8f743b1, 2bd860b7e752a51185960143cab9fec7bf32c84e, 2fdf8b07bee5ef99ec77773a6be05fbb8ee5cdb9 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 15, 2026
- Updated
- Aug 23, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.14affected
- 5b432413f7bbbc8b935138490a57be05c1921684 and later · before c65eb018c12179b5e2c7afe1f0956298576fececaffected · git
- bb4715098d8e340bbbdd3a874b31f89867c8067e and later · before 2bd860b7e752a51185960143cab9fec7bf32c84eaffected · git
- c152be5adc0975c75cc4f50891c9072d52d60b47 and later · before eea4b7c7711b1e425272d23352af157f45f4c3e3affected · git
- bf5ed2ef5cdb7b47ce606e3d48ea6eb803b31503 and later · before 2fdf8b07bee5ef99ec77773a6be05fbb8ee5cdb9affected · git
- 483217fd6f7ccd98b3ed2531a54f75ed144b4499 and later · before f1e7ea3c8e070f19771cdaef55bbeda1359ad490affected · git
- 0357ef03c94ef835bd44a0658b8edb672a9dbf51 and later · before 255a758697da87a205e072e0cfc35897b8f743b1affected · git
- 0357ef03c94ef835bd44a0658b8edb672a9dbf51 and later · before f0edbaf487e4653a680a7abb91c1df94cb7886aaaffected · git
- 0357ef03c94ef835bd44a0658b8edb672a9dbf51 and later · before fa5990ca8fd917003e526036bcc50413edb9722caffected · git
- before 6.14not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:14 | linux | before 7.1.8-1 | 7.1.8-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-74483Aug 15, 2026 · binfmt_misc: don't leak the user namespace when the mount fails0Monitor
- ← EarlierCVE-2026-74484Aug 15, 2026 · binfmt_misc: don't let an 'F' entry pin its own instance0Monitor
- Later →CVE-2026-74487Aug 15, 2026 · binfmt_misc: restore write access when removing an entry0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 255a758697da87a205e072e0cfc35897b8f743b1 | Vendor (CNA) |
| Linux Linux | 2bd860b7e752a51185960143cab9fec7bf32c84e | Vendor (CNA) |
| Linux Linux | 2fdf8b07bee5ef99ec77773a6be05fbb8ee5cdb9 | Vendor (CNA) |
| Linux Linux | c65eb018c12179b5e2c7afe1f0956298576fecec | Vendor (CNA) |
| Linux Linux | eea4b7c7711b1e425272d23352af157f45f4c3e3 | Vendor (CNA) |
| Linux Linux | f0edbaf487e4653a680a7abb91c1df94cb7886aa | Vendor (CNA) |
| Linux Linux | f1e7ea3c8e070f19771cdaef55bbeda1359ad490 | Vendor (CNA) |
| Linux Linux | fa5990ca8fd917003e526036bcc50413edb9722c | Vendor (CNA) |
| debian:linux | 7.1.8-1 · Debian:14 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0854 · Aug 19, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/2bd860b7e752a51185960143cab9fec7bf32c84e
- git.kernel.org/stable/c/2fdf8b07bee5ef99ec77773a6be05fbb8ee5cdb9
- git.kernel.org/stable/c/c65eb018c12179b5e2c7afe1f0956298576fecec
- git.kernel.org/stable/c/eea4b7c7711b1e425272d23352af157f45f4c3e3
- git.kernel.org/stable/c/f0edbaf487e4653a680a7abb91c1df94cb7886aa
- git.kernel.org/stable/c/f1e7ea3c8e070f19771cdaef55bbeda1359ad490
- git.kernel.org/stable/c/fa5990ca8fd917003e526036bcc50413edb9722c
Vendor advisories and official records. Exploit/PoC links are deliberately left out.