binfmt_misc: restore write access when removing an entry
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 948b701a607f123df92ed29084413e5dd8cda2ed · < fdc1d702bf3001586221fa07e598e876a0a854c5| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s binfmt_misc subsystem fails to restore write access to an interpreter when an entry registered with MISC_FMT_OPEN_FILE is removed. A local actor able to register and remove such an entry can leave writes to the interpreter failing with ETXTBSY until its inode is evicted from the cache. No user interaction is described.
Engineers running Linux kernels with binfmt_misc should check whether their kernel includes the fix; affected versions are not specified.