USN-5073-2: Linux kernel (GCP) vulnerabilities<\/p>\n
Maxim Levitsky and Paolo Bonzini discovered that the KVM hypervisor
\nimplementation for AMD processors in the Linux kernel allowed a guest VM to
\ndisable restrictions on VMLOAD\/VMSAVE in a nested guest. An attacker in a
\nguest VM could use this to read or write portions of the host’s physical
\nmemory. (CVE-2021-3656)<\/p>\n
Maxim Levitsky discovered that the KVM hypervisor implementation for AMD
\nprocessors in the Linux kernel did not properly prevent a guest VM from
\nenabling AVIC in nested guest VMs. An attacker in a guest VM could use this
\nto write to portions of the host’s physical memory. (CVE-2021-3653)<\/p>\n
Norbert Slusarek discovered that the CAN broadcast manger (bcm) protocol
\nimplementation in the Linux kernel did not properly initialize memory in
\nsome situations. A local attacker could use this to expose sensitive
\ninformation (kernel memory). (CVE-2021-34693)<\/p>\n
Murray McAllister discovered that the joystick device interface in the
\nLinux kernel did not properly validate data passed via an ioctl(). A local
\nattacker could use this to cause a denial of service (system crash) or
\npossibly execute arbitrary code on systems with a joystick device
\nregistered. (CVE-2021-3612)<\/p>\n
It was discovered that the Virtio console implementation in the Linux USN-5073-2: Linux kernel (GCP) vulnerabilities Maxim Levitsky and Paolo Bonzini discovered that the KVM hypervisor implementation for AMD processors in the Linux kernel allowed a guest VM to disable restrictions on VMLOAD\/VMSAVE in a nested guest. An attacker in a guest VM could use this to read or write portions of the host’s physical memory. (CVE-2021-3656) Maxim Levitsky discovered that the KVM hypervisor implementation for AMD processors in the Linux kernel did not properly prevent a guest VM from enabling AVIC in nested guest VMs. An attacker in a guest VM could use this to write to portions of the host’s physical memory. (CVE-2021-3653) Norbert Slusarek discovered that the CAN broadcast manger (bcm) protocol implementation in the Linux kernel did not properly initialize memory in some situations. A local attacker could use this to expose sensitive information (kernel memory). (CVE-2021-34693) [ more… ]<\/a><\/p>\n<\/div>","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[586],"tags":[587],"class_list":["post-43315","post","type-post","status-publish","format-standard","hentry","category-ubuntu-usn","tag-ubuntu-usn"],"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/jirak.net\/wp\/wp-json\/wp\/v2\/posts\/43315","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/jirak.net\/wp\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/jirak.net\/wp\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/jirak.net\/wp\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/jirak.net\/wp\/wp-json\/wp\/v2\/comments?post=43315"}],"version-history":[{"count":1,"href":"https:\/\/jirak.net\/wp\/wp-json\/wp\/v2\/posts\/43315\/revisions"}],"predecessor-version":[{"id":43316,"href":"https:\/\/jirak.net\/wp\/wp-json\/wp\/v2\/posts\/43315\/revisions\/43316"}],"wp:attachment":[{"href":"https:\/\/jirak.net\/wp\/wp-json\/wp\/v2\/media?parent=43315"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/jirak.net\/wp\/wp-json\/wp\/v2\/categories?post=43315"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/jirak.net\/wp\/wp-json\/wp\/v2\/tags?post=43315"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\nkernel did not properly validate input lengths in some situations. A local
\nattacker could possibly use this to cause a denial of service (system
\ncrash). (CVE-2021-38160)
\nSource: USN-5073-2: Linux kernel (GCP) vulnerabilities<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"