CVE-2022-50081: KVM: Unconditionally get a ref to /dev/kvm module when creating a VM
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ubuntu/linux-aws-5.15to a version that resolves this vulnerability.Fixed in 5.15.0-1023.27~20.04.1 - Upgrade
Upgrade
ubuntu/linux-azure-5.15to a version that resolves this vulnerability.Fixed in 5.15.0-1023.29~20.04.1 - Upgrade
Upgrade
ubuntu/linux-gcp-5.15to a version that resolves this vulnerability.Fixed in 5.15.0-1022.29~20.04.1 - Upgrade
Upgrade
ubuntu/linux-hwe-5.15to a version that resolves this vulnerability.Fixed in 5.15.0-53.59~20.04.1 - Upgrade
Upgrade
ubuntu/linux-intel-iotg-5.15to a version that resolves this vulnerability.Fixed in 5.15.0-1018.23~20.04.1 - Upgrade
Upgrade
ubuntu/linux-lowlatency-hwe-5.15to a version that resolves this vulnerability.Fixed in 5.15.0-53.59~20.04.1 - Upgrade
Upgrade
ubuntu/linux-oracle-5.15to a version that resolves this vulnerability.Fixed in 5.15.0-1022.28~20.04.1 - Upgrade
Upgrade
ubuntu/linux-riscv-5.15to a version that resolves this vulnerability.Fixed in 5.15.0-1023.27~20.04.1 - Compensating control
Do not use `rmmod --force` on the KVM module while VMs may be running.
Event History
Frequently Asked Questions
What is the severity of CVE-2022-50081?
CVE-2022-50081 has been rejected or withdrawn, thus it does not have an assigned severity level.
What does it mean that CVE-2022-50081 has been rejected?
The rejection of CVE-2022-50081 indicates that it was not considered valid for public disclosure of a security vulnerability.
Is there a fix available for CVE-2022-50081?
Since CVE-2022-50081 has been rejected, there are no fixes or patches necessary for it.
Which software is affected by CVE-2022-50081?
CVE-2022-50081 was associated with the Linux kernel, but since it's rejected, no specific version is implicated.
How should I respond to the findings regarding CVE-2022-50081?
As CVE-2022-50081 has been withdrawn, there is no need for any response or mitigation related to this identifier.