CVE-2026-74487

binfmt_misc: restore write access when removing an entry

N/A
Published: August 15, 2026 at 12:27 PM UTC
Updated: August 23, 2026 at 01:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: binfmt_misc: restore write access when removing an entry Registering an entry with the MISC_FMT_OPEN_FILE flag opens the interpreter via open_exec() which denies write access to it for as long as the entry exists. Removing the entry closes the interpreter file via filp_close() but never restores write access, leaving the inode's i_writecount permanently negative. Opening the interpreter for writing keeps failing with ETXTBSY long after the entry is gone until the inode is evicted from the inode cache. Commit 90f601b497d7 ("binfmt_misc: restore write access before closing files opened by open_exec()") fixed the same imbalance in the error path of bm_register_write() but the actual removal path has been leaking the write denial since the introduction of the flag. Restore write access in put_binfmt_handler() before closing the interpreter file.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.8 ≤ v < 5.10.2664.8 ≤ v < 5.15.2174.8 ≤ v < 6.1.1844.8 ≤ v < 6.12.1054.8 ≤ v < 6.18.444.8 ≤ v < 6.6.1534.8 ≤ v < 7.1.84.8 ≤ v < 7.24.8948b701a607f123df92ed29084413e5dd8cda2ed
Vendor states this is fixed in 13efc628fdf641d901bdba07caa1c558e1bed046 (fixed)
Vendor states this is fixed in 3b522487a3a9162b1b519eefde7998d103e3e07b (fixed)
Vendor states this is fixed in 7873f987213695e3564c8c259e6db283e4739472 (fixed)
Vendor states this is fixed in a50296cca2a1db9d8d21051e7d50f0cf3a4b7ec8 (fixed)
Vendor states this is fixed in db1856ea9196cf6e015d12199a34c0b9313c7bfa (fixed)
Vendor states this is fixed in dd9ba32169e73a3c3ba595cf1de1f4c69ceafb3c (fixed)
Vendor states this is fixed in f1cf67f6be0babc73afa4ee0e27bdedffeeeb095 (fixed)
Vendor states this is fixed in fdc1d702bf3001586221fa07e598e876a0a854c5 (fixed)
Vendor states this is fixed in 4.8 (unaffected)
Vendor states this is fixed in 5.10.266 (unaffected)
Vendor states this is fixed in 5.15.217 (unaffected)
Vendor states this is fixed in 6.1.184 (unaffected)
Vendor states this is fixed in 6.12.105 (unaffected)
Vendor states this is fixed in 6.18.44 (unaffected)
Vendor states this is fixed in 6.6.153 (unaffected)
Vendor states this is fixed in 7.1.8 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card