scsi: target: file: Use kzalloc_flex for aio_cmd
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.18.22, 6.19.12
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From 732f25a2895a8c1c54fb56544f0b1e23770ef4d7 · fixed in ce54802fe6bb78eb0feffc66fed6a45d41ffc3ab; From 732f25a2895a8c1c54fb56544f0b1e23770ef4d7 · fixed in 4eaff1728d0e69b95933412241bbccf4f797dba8; From 732f25a2895a8c1c54fb56544f0b1e23770ef4d7 · fixed in 01f784fc9d0ab2a6dac45ee443620e517cb2a19b
- Linux Linux
6.16
- KernelLinux
From 6.16.0 · fixed in 6.18.22; From 6.19.0 · fixed in 6.19.12