Description
In the Linux kernel, the following vulnerability has been resolved: scsi: target: file: Use kzalloc_flex for aio_cmd The target_core_file doesn't initialize the aio_cmd->iocb for the ki_write_stream. When a write command fd_execute_rw_aio() is executed, we may get a bogus ki_write_stream value, causing unintended write failure status when checking iocb->ki_write_stream > max_write_streams in the block device. Let's just use kzalloc_flex when allocating the aio_cmd and let ki_write_stream=0 to fix this issue.
Product status
732f25a2895a8c1c54fb56544f0b1e23770ef4d7 (git) before ce54802fe6bb78eb0feffc66fed6a45d41ffc3ab
732f25a2895a8c1c54fb56544f0b1e23770ef4d7 (git) before 4eaff1728d0e69b95933412241bbccf4f797dba8
732f25a2895a8c1c54fb56544f0b1e23770ef4d7 (git) before 01f784fc9d0ab2a6dac45ee443620e517cb2a19b
6.16
Any version before 6.16
6.18.22 (semver)
6.19.12 (semver)
7.0 (original_commit_for_fix)
References
git.kernel.org/...c/ce54802fe6bb78eb0feffc66fed6a45d41ffc3ab
git.kernel.org/...c/4eaff1728d0e69b95933412241bbccf4f797dba8
git.kernel.org/...c/01f784fc9d0ab2a6dac45ee443620e517cb2a19b