The problem can be corrected by updating your system to the following package versions: Ubuntu 20.04 LTS: linux-image-5.15.0-48-generic 5.15.0-48.54~20.04.1 linux-image-5.15.0-48-generic-64k 5.15.0-48.54~20.04.1 linux-image-5.15.0-48-generic-lpae 5.15.0-48.54~20.04.1 linux-image-5.15.0-48-lowlatency 5.15.0-48.54~20.04.1 linux-image-5.15.0-48-lowlatency-64k 5.15.0-48.54~20.04.1 linux-image-generic-64k-hwe-20.04 5.15.0.48.54~20.04.18 linux-image-generic-hwe-20.04 5.15.0.48.54~20.04.18 linux-image-generic-lpae-hwe-20.04 5.15.0.48.54~20.04.18 linux-image-lowlatency-64k-hwe-20.04 5.15.0.48.54~20.04.16 linux-image-lowlatency-hwe-20.04 5.15.0.48.54~20.04.16 linux-image-virtual-hwe-20.04 5.15.0.48.54~20.04.18 After a standard system update you need to reboot your computer to make all the necessary changes. ATTENTION: Due to an unavoidable ABI change the kernel updates have been given a new version number, which requires you to recompile and reinstall all third party kernel modules you might have installed. Unless you manually uninstalled the standard kernel metapackages (e.g. linux-generic, linux-generic-lts-RELEASE, linux-virtual, linux-powerpc), a standard system upgrade will automatically perform this as well.
https://ubuntu.com/security/notices/USN-5623-1
CVE-2021-33061, CVE-2021-33655, CVE-2022-1012, CVE-2022-1729,
CVE-2022-1852, CVE-2022-1943, CVE-2022-1973, CVE-2022-2318,
CVE-2022-2503, CVE-2022-26365, CVE-2022-2873, CVE-2022-2959,
CVE-2022-32296, CVE-2022-33740, CVE-2022-33741, CVE-2022-33742,
CVE-2022-33743, CVE-2022-33744, CVE-2022-34494, CVE-2022-34495,
CVE-2022-36946
https://launchpad.net/ubuntu/+source/linux-hwe-5.15/5.15.0-48.54~20.04.1 https://launchpad.net/ubuntu/+source/linux-lowlatency-hwe-5.15/5.15.0-48.54~20.04.1
Get the latest Linux and open source security news straight to your inbox.