CVE-2020-25741 QEMU: fdc: null pointer dereference during r/w data transfer A null pointer dereference issue was found in the Floppy disk emulator of QEMU. It could occur while transferring data via fdctrl_read_data(), fdctrl_write_data() routines, if current drive has a null block pointer. A guest may use this flaw to crash the QEMU process on the host resulting in DoS scenario. References: ----------- -> https://lists.nongnu.org/archive/html/qemu-devel/2020-09/msg07779.html -> https://ruhr-uni-bochum.sciebo.de/s/NNWP2GfwzYKeKwE?path=%2Ffdc_nullptr1 === 2. CVE-2020-25742 QEMU: scsi: lsi: null pointer dereference during memory move A null pointer dereference issue was found in the LSI53C895A SCSI Host Bus Adapter emulator of QEMU. It could occur while processing 'Memory Move' instructions to move data between dma memory and i/o address space via lsi_memcpy(). A guest user/process may use this flaw to crash the QEMU process resulting in DoS scenario. References: ----------- -> https://lists.nongnu.org/archive/html/qemu-devel/2020-09/msg05294.html -> https://ruhr-uni-bochum.sciebo.de/s/NNWP2GfwzYKeKwE?path=%2Flsi_nullptr1 === 3. CVE-2020-25743 QEMU: ide: null pointer dereference while cancelling i/o operation A null pointer dereference issue was found in the IDE disk emulator of QEMU. It could occur while cancelling an i/o operation via ide_cancel_dma_sync() routine, if a block drive pointer is null. A guest may use this flaw to crash the QEMU process on the host resulting in DoS scenario. References: ----------- -> https://lists.nongnu.org/archive/html/qemu-devel/2020-09/msg01568.html -> https://ruhr-uni-bochum.sciebo.de/s/NNWP2GfwzYKeKwE?path=%2Fide_nullptr1b * These issues were reported by Sergej Schumilo, Cornelius Aschermann, Simon Wrner of Ruhr-University Bochum. Other Links: https://www.suse.com/security/cve/CVE-2020-25741/ https://www.suse.com/security/cve/CVE-2020-25743/ Reproducible: Always
We will wait when correct fix lands upstream.
(In reply to Sergei Trofimovich from comment #1) > We will wait when correct fix lands upstream. thank you for answer, I changed the whiteboard
QEMU 5.2 is out, does it have the fixes?
(In reply to Joakim Tjernlund from comment #3) > QEMU 5.2 is out, does it have the fixes? QEMU is one of the worst upstreams I've seen for tracking patches. That said, I don't see the subjects of those emails in any QEMU master commits.
These patches have not been applied upstream.
Package list is empty or all packages have requested keywords.
Still seems unfixed
(In reply to filip ambroz from comment #0) > CVE-2020-25741 QEMU: fdc: null pointer dereference during r/w data transfer > > A null pointer dereference issue was found in the Floppy disk emulator of > QEMU. It could occur while transferring data via fdctrl_read_data(), > fdctrl_write_data() routines, if current drive has a null block pointer. A > guest may use this flaw to crash the QEMU process on the host resulting in > DoS scenario. > > > References: > ----------- > -> https://lists.nongnu.org/archive/html/qemu-devel/2020-09/msg07779.html > -> https://ruhr-uni-bochum.sciebo.de/s/NNWP2GfwzYKeKwE?path=%2Ffdc_nullptr1 > === > > 2. CVE-2020-25742 QEMU: scsi: lsi: null pointer dereference during memory > move > > A null pointer dereference issue was found in the LSI53C895A SCSI Host Bus > Adapter emulator of QEMU. It could occur while processing 'Memory Move' > instructions to move data between dma memory and i/o address space via > lsi_memcpy(). A guest user/process may use this flaw to crash the QEMU > process resulting in DoS scenario. > > > References: > ----------- > -> https://lists.nongnu.org/archive/html/qemu-devel/2020-09/msg05294.html > -> https://ruhr-uni-bochum.sciebo.de/s/NNWP2GfwzYKeKwE?path=%2Flsi_nullptr1 > === > > > 3. CVE-2020-25743 QEMU: ide: null pointer dereference while cancelling i/o > operation > > A null pointer dereference issue was found in the IDE disk emulator of QEMU. > It could occur while cancelling an i/o operation via ide_cancel_dma_sync() > routine, if a block drive pointer is null. A guest may use this flaw to > crash the QEMU process on the host resulting in DoS scenario. > > > References: > ----------- > -> https://lists.nongnu.org/archive/html/qemu-devel/2020-09/msg01568.html > -> > https://ruhr-uni-bochum.sciebo.de/s/NNWP2GfwzYKeKwE?path=%2Fide_nullptr1b > > > * These issues were reported by Sergej Schumilo, Cornelius Aschermann, Simon > Wrner of Ruhr-University Bochum. > > Other Links: > https://www.suse.com/security/cve/CVE-2020-25741/ > https://www.suse.com/security/cve/CVE-2020-25743/ > https://scratchgeometrydash.com > Reproducible: Always These vulnerabilities were reported by security researchers from Ruhr-University Bochum and highlight potential risks associated with null pointer dereferences in critical parts of QEMU's emulation stack. It's recommended to update QEMU to the latest version available to mitigate these vulnerabilities.
