CVE-2020-11669

Description

An issue was discovered in the Linux kernel before 5.2 on the powerpc platform. arch/powerpc/kernel/idle_book3s.S does not have save/restore functionality for PNV_POWERSAVE_AMR, PNV_POWERSAVE_UAMOR, and PNV_POWERSAVE_AMOR, aka CID-53a712bae5dd.

5.5

CVSS

Severity: Medium

CVSS 3.1 •

CVSS 2.0 •

EPSS 0.02%

Vendor Advisory redhat.com Vendor Advisory opensuse.org Vendor Advisory ubuntu.com Vendor Advisory ubuntu.com Vendor Advisory kernel.org Vendor Advisory kernel.org Vendor Advisory github.com

Affected: n/a n/a

References

Link	Tags
https://access.redhat.com/errata/RHSA-2019:3517	third party advisory vendor advisory
https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.2	release notes vendor advisory
https://lists.ozlabs.org/pipermail/linuxppc-dev/2020-April/208663.html	mailing list third party advisory patch
https://lists.ozlabs.org/pipermail/linuxppc-dev/2020-April/208660.html	mailing list third party advisory patch
https://lists.ozlabs.org/pipermail/linuxppc-dev/2020-April/208661.html	mailing list third party advisory patch
https://github.com/torvalds/linux/commit/53a712bae5dd919521a58d7bad773b949358add0	patch vendor advisory
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=53a712bae5dd919521a58d7bad773b949358add0	patch vendor advisory
http://lists.opensuse.org/opensuse-security-announce/2020-04/msg00035.html	mailing list third party advisory patch vendor advisory
https://security.netapp.com/advisory/ntap-20200430-0001/	mailing list third party advisory patch
https://usn.ubuntu.com/4368-1/	vendor advisory
https://usn.ubuntu.com/4363-1/	vendor advisory

Frequently Asked Questions

What is the severity of CVE-2020-11669?: CVE-2020-11669 has been scored as a medium severity vulnerability.
How to fix CVE-2020-11669?: To fix CVE-2020-11669, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2020-11669 being actively exploited in the wild?: As for now, there are no information to confirm that CVE-2020-11669 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.