CVE-2020-25741: Null Pointer Dereference
First published: Fri Oct 02 2020(Updated: )
fdctrl_write_data in hw/block/fdc.c in QEMU 5.0.0 has a NULL pointer dereference via a NULL block pointer for the current drive.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| QEMU KVM | =5.0.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2020-25741?
CVE-2020-25741 is classified as a high severity vulnerability due to its potential to cause a denial of service through a NULL pointer dereference.
How do I fix CVE-2020-25741?
To fix CVE-2020-25741, upgrade your QEMU installation to version 5.0.1 or later, which addresses this vulnerability.
Which version of QEMU is affected by CVE-2020-25741?
CVE-2020-25741 specifically affects QEMU version 5.0.0.
What is the exploit impact of CVE-2020-25741?
The exploit impact of CVE-2020-25741 is primarily denial of service, as it leads to a crash of the QEMU process.
Is there a workaround for CVE-2020-25741?
As a workaround for CVE-2020-25741, avoid using the features related to the affected block drivers until you can apply the patch.
- agent/references
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/weakness
- agent/author
- agent/remedy
- agent/last-modified-date
- agent/description
- agent/first-publish-date
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/qemu
- canonical/qemu kvm
- version/qemu kvm/5.0.0