CVE-2026-74487: Linux kernel · binfmt_misc: restore write access when removing an entry
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in fdc1d702bf3001586221fa07e598e876a0a854c5 : update Linux kernel when convenient.
Data as of 6 Nov 2026, 17:56 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-06.
- Patch
- Available – fixed in fdc1d702bf3001586221fa07e598e876a0a854c5, f1cf67f6be0babc73afa4ee0e27bdedffeeeb095, dd9ba32169e73a3c3ba595cf1de1f4c69ceafb3c +5
Exploitation evidence
Disclosed: evidence found.
CVE published 15 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix is available and has been applied in the Linux kernel source as indicated by the listed fixed commit versions. Users and administrators should update their Linux kernel to a version including these fixes to resolve the write access denial issue. No additional mitigation steps are indicated.
Description
A vulnerability in the Linux kernel's binfmt_misc subsystem caused write access to an interpreter file to remain denied after removing an entry, due to an imbalance in write access accounting. This resulted in the inode's write count being permanently negative, preventing the interpreter from being opened for writing until the inode was evicted from the cache. The issue was fixed by restoring write access before closing the interpreter file during entry removal.
References
- git.kernel.org/stable/c/7873f987213695e3564c8c259e6db283e4739472 (opens in a new tab)
- git.kernel.org/stable/c/13efc628fdf641d901bdba07caa1c558e1bed046 (opens in a new tab)
- git.kernel.org/stable/c/f1cf67f6be0babc73afa4ee0e27bdedffeeeb095 (opens in a new tab)
- git.kernel.org/stable/c/dd9ba32169e73a3c3ba595cf1de1f4c69ceafb3c (opens in a new tab)
- git.kernel.org/stable/c/a50296cca2a1db9d8d21051e7d50f0cf3a4b7ec8 (opens in a new tab)
- git.kernel.org/stable/c/fdc1d702bf3001586221fa07e598e876a0a854c5 (opens in a new tab)
- git.kernel.org/stable/c/3b522487a3a9162b1b519eefde7998d103e3e07b (opens in a new tab)
- git.kernel.org/stable/c/db1856ea9196cf6e015d12199a34c0b9313c7bfa (opens in a new tab)