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.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Linux Linux
Default version status: unaffected
732f25a2895a8c1c54fb56544f0b1e23770ef4d7 to < ce54802fe6bb78eb0feffc66fed6a45d41ffc3abaffected732f25a2895a8c1c54fb56544f0b1e23770ef4d7 to < 4eaff1728d0e69b95933412241bbccf4f797dba8affected732f25a2895a8c1c54fb56544f0b1e23770ef4d7 to < 01f784fc9d0ab2a6dac45ee443620e517cb2a19baffected
Linux Linux
Default version status: affected
6.16affected0 to < 6.16unaffected6.18.22 to ≤ 6.18.*unaffected6.19.12 to ≤ 6.19.*unaffected7.0 to ≤ *unaffected