References to Advisories, Solutions, and Tools

By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to nvd@nist.gov.

Change History

https://git.kernel.org/stable/c/10c02aad111df02088d1a81792a709f6a7eca6cc

https://git.kernel.org/stable/c/3ab1c40a1e915e350d9181a4603af393141970cc

https://git.kernel.org/stable/c/3d16cebf01127f459dcfeb79ed77bd68b124c228

In the Linux kernel, the following vulnerability has been resolved:

KVM: arm64: Fix circular locking dependency

The rule inside kvm enforces that the vcpu->mutex is taken *inside*
kvm->lock. The rule is violated by the pkvm_create_hyp_vm() which acquires
the kvm->lock while already holding the vcpu->mutex lock from
kvm_vcpu_ioctl(). Avoid the circular locking dependency altogether by
protecting the hyp vm handle with the config_lock, much like we already
do for other forms of VM-scoped data.

kernel.org https://git.kernel.org/stable/c/10c02aad111df02088d1a81792a709f6a7eca6cc [No types assigned]

kernel.org https://git.kernel.org/stable/c/3ab1c40a1e915e350d9181a4603af393141970cc [No types assigned]

kernel.org https://git.kernel.org/stable/c/3d16cebf01127f459dcfeb79ed77bd68b124c228 [No types assigned]