CyberRota Analysis
AI-GeneratedThe vulnerability affects the Linux kernel's handling of interpreter files in the binfmt_misc subsystem, where improper management of write access can lead to inconsistent states during execution. Specifically, the issue arises from a failure to properly synchronize write permissions between the clone of the interpreter and the original file, potentially leading to unwritable interpreter files and execution failures. System administrators and developers using Linux kernel versions that utilize binfmt_misc should prioritize addressing this vulnerability to ensure reliable execution of binary formats and prevent unexpected behavior in their applications.
Original NVD Description
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.