USN-5692-1: Linux kernel vulnerabilities
19 October 2022
Several security issues were fixed in the Linux kernel.
Releases
Packages
- linux - Linux kernel
- linux-aws - Linux kernel for Amazon Web Services (AWS) systems
- linux-aws-5.15 - Linux kernel for Amazon Web Services (AWS) systems
- linux-azure - Linux kernel for Microsoft Azure Cloud systems
- linux-azure-5.15 - Linux kernel for Microsoft Azure cloud systems
- linux-gcp - Linux kernel for Google Cloud Platform (GCP) systems
- linux-gcp-5.15 - Linux kernel for Google Cloud Platform (GCP) systems
- linux-gke - Linux kernel for Google Container Engine (GKE) systems
- linux-gke-5.15 - Linux kernel for Google Container Engine (GKE) systems
- linux-gkeop - Linux kernel for Google Container Engine (GKE) systems
- linux-hwe-5.15 - Linux hardware enablement (HWE) kernel
- linux-ibm - Linux kernel for IBM cloud systems
- linux-kvm - Linux kernel for cloud environments
- linux-lowlatency - Linux low latency kernel
- linux-lowlatency-hwe-5.15 - Linux low latency kernel
- linux-oem-5.14 - Linux kernel for OEM systems
- linux-oracle - Linux kernel for Oracle Cloud systems
- linux-raspi - Linux kernel for Raspberry Pi systems
Details
David Bouman and Billy Jheng Bing Jhong discovered that a race condition
existed in the io_uring subsystem in the Linux kernel, leading to a use-
after-free vulnerability. A local attacker could use this to cause a denial
of service (system crash) or possibly execute arbitrary code.
(CVE-2022-2602)
Sönke Huster discovered that an integer overflow vulnerability existed in
the WiFi driver stack in the Linux kernel, leading to a buffer overflow. A
physically proximate attacker could use this to cause a denial of service
(system crash) or possibly execute arbitrary code. (CVE-2022-41674)
Sönke Huster discovered that a use-after-free vulnerability existed in the
WiFi driver stack in the Linux kernel. A physically proximate attacker
could use this to cause a denial of service (system crash) or possibly
execute arbitrary code. (CVE-2022-42719)
Sönke Huster discovered that the WiFi driver stack in the Linux kernel did
not properly perform reference counting in some situations, leading to a
use-after-free vulnerability. A physically proximate attacker could use
this to cause a denial of service (system crash) or possibly execute
arbitrary code. (CVE-2022-42720)
Sönke Huster discovered that the WiFi driver stack in the Linux kernel did
not properly handle BSSID/SSID lists in some situations. A physically
proximate attacker could use this to cause a denial of service (infinite
loop). (CVE-2022-42721)
Sönke Huster discovered that the WiFi driver stack in the Linux kernel
contained a NULL pointer dereference vulnerability in certain situations. A
physically proximate attacker could use this to cause a denial of service
(system crash). (CVE-2022-42722)
Update instructions
The problem can be corrected by updating your system to the following package versions:
Ubuntu 22.04
-
linux-image-5.15.0-52-generic-64k
-
5.15.0-52.58
-
linux-image-gkeop
-
5.15.0.1007.8
-
linux-image-virtual
-
5.15.0.52.52
-
linux-image-aws
-
5.15.0.1022.22
-
linux-image-lowlatency-64k-hwe-22.04
-
5.15.0.52.47
-
linux-image-azure
-
5.15.0.1022.21
-
linux-image-5.15.0-1019-gke
-
5.15.0-1019.23
-
linux-image-5.15.0-52-generic-lpae
-
5.15.0-52.58
-
linux-image-generic-64k-hwe-22.04
-
5.15.0.52.52
-
linux-image-kvm
-
5.15.0.1020.18
-
linux-image-lowlatency
-
5.15.0.52.47
-
linux-image-5.15.0-1020-kvm
-
5.15.0-1020.24
-
linux-image-generic-64k
-
5.15.0.52.52
-
linux-image-gke-5.15
-
5.15.0.1019.20
-
linux-image-5.15.0-1022-azure
-
5.15.0-1022.27
-
linux-image-5.15.0-1021-oracle
-
5.15.0-1021.27
-
linux-image-gcp
-
5.15.0.1021.18
-
linux-image-gkeop-5.15
-
5.15.0.1007.8
-
linux-image-generic-lpae-hwe-22.04
-
5.15.0.52.52
-
linux-image-generic-lpae
-
5.15.0.52.52
-
linux-image-5.15.0-1022-aws
-
5.15.0-1022.26
-
linux-image-5.15.0-52-lowlatency
-
5.15.0-52.58
-
linux-image-5.15.0-1017-raspi
-
5.15.0-1017.19
-
linux-image-ibm
-
5.15.0.1017.15
-
linux-image-5.15.0-52-lowlatency-64k
-
5.15.0-52.58
-
linux-image-aws-lts-22.04
-
5.15.0.1022.22
-
linux-image-gke
-
5.15.0.1019.20
-
linux-image-oracle
-
5.15.0.1021.18
-
linux-image-lowlatency-hwe-22.04
-
5.15.0.52.47
-
linux-image-raspi
-
5.15.0.1017.16
-
linux-image-generic
-
5.15.0.52.52
-
linux-image-azure-lts-22.04
-
5.15.0.1022.21
-
linux-image-5.15.0-1021-gcp
-
5.15.0-1021.28
-
linux-image-5.15.0-52-generic
-
5.15.0-52.58
-
linux-image-5.15.0-1017-ibm
-
5.15.0-1017.20
-
linux-image-lowlatency-64k
-
5.15.0.52.47
-
linux-image-generic-hwe-22.04
-
5.15.0.52.52
-
linux-image-5.15.0-1007-gkeop
-
5.15.0-1007.10
-
linux-image-raspi-nolpae
-
5.15.0.1017.16
-
linux-image-5.15.0-1017-raspi-nolpae
-
5.15.0-1017.19
-
linux-image-virtual-hwe-22.04
-
5.15.0.52.52
Ubuntu 20.04
-
linux-image-5.15.0-52-generic-64k
-
5.15.0-52.58~20.04.1
-
linux-image-5.15.0-52-lowlatency
-
5.15.0-52.58~20.04.1
-
linux-image-oem-20.04b
-
5.14.0.1054.52
-
linux-image-virtual-hwe-20.04
-
5.15.0.52.58~20.04.20
-
linux-image-aws
-
5.15.0.1022.26~20.04.14
-
linux-image-oem-20.04d
-
5.14.0.1054.52
-
linux-image-gke-5.15
-
5.15.0.1019.23~20.04.1
-
linux-image-5.15.0-1022-azure
-
5.15.0-1022.27~20.04.1
-
linux-image-lowlatency-hwe-20.04
-
5.15.0.52.58~20.04.18
-
linux-image-5.15.0-52-lowlatency-64k
-
5.15.0-52.58~20.04.1
-
linux-image-oem-20.04c
-
5.14.0.1054.52
-
linux-image-5.14.0-1054-oem
-
5.14.0-1054.61
-
linux-image-generic-hwe-20.04
-
5.15.0.52.58~20.04.20
-
linux-image-azure
-
5.15.0.1022.27~20.04.15
-
linux-image-oem-20.04
-
5.14.0.1054.52
-
linux-image-lowlatency-64k-hwe-20.04
-
5.15.0.52.58~20.04.18
-
linux-image-gcp
-
5.15.0.1021.28~20.04.1
-
linux-image-5.15.0-1019-gke
-
5.15.0-1019.23~20.04.1
-
linux-image-5.15.0-52-generic-lpae
-
5.15.0-52.58~20.04.1
-
linux-image-5.15.0-1021-gcp
-
5.15.0-1021.28~20.04.1
-
linux-image-generic-lpae-hwe-20.04
-
5.15.0.52.58~20.04.20
-
linux-image-5.15.0-52-generic
-
5.15.0-52.58~20.04.1
-
linux-image-generic-64k-hwe-20.04
-
5.15.0.52.58~20.04.20
-
linux-image-5.15.0-1022-aws
-
5.15.0-1022.26~20.04.1
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.