USN-6626-1: Linux kernel vulnerabilities
8 February 2024
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-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-gkeop - Linux kernel for Google Container Engine (GKE) systems
- linux-gkeop-5.15 - 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-ibm-5.15 - Linux kernel for IBM cloud systems
- linux-kvm - Linux kernel for cloud environments
- linux-lowlatency-hwe-5.15 - Linux low latency kernel
- linux-nvidia - Linux kernel for NVIDIA systems
- linux-oracle - Linux kernel for Oracle Cloud systems
- linux-oracle-5.15 - Linux kernel for Oracle Cloud systems
Details
Quentin Minster discovered that a race condition existed in the KSMBD
implementation in the Linux kernel when handling sessions operations. A
remote attacker could use this to cause a denial of service (system crash)
or possibly execute arbitrary code. (CVE-2023-32250, CVE-2023-32252,
CVE-2023-32257)
Marek Marczykowski-Górecki discovered that the Xen event channel
infrastructure implementation in the Linux kernel contained a race
condition. An attacker in a guest VM could possibly use this to cause a
denial of service (paravirtualized device unavailability). (CVE-2023-34324)
Zheng Wang discovered a use-after-free in the Renesas Ethernet AVB driver
in the Linux kernel during device removal. A privileged attacker could use
this to cause a denial of service (system crash). (CVE-2023-35827)
Tom Dohrmann discovered that the Secure Encrypted Virtualization (SEV)
implementation for AMD processors in the Linux kernel contained a race
condition when accessing MMIO registers. A local attacker in a SEV guest VM
could possibly use this to cause a denial of service (system crash) or
possibly execute arbitrary code. (CVE-2023-46813)
It was discovered that the Microchip USB Ethernet driver in the Linux
kernel contained a race condition during device removal, leading to a use-
after-free vulnerability. A physically proximate attacker could use this to
cause a denial of service (system crash). (CVE-2023-6039)
It was discovered that the TLS subsystem in the Linux kernel did not
properly perform cryptographic operations in some situations, leading to a
null pointer dereference vulnerability. A local attacker could use this to
cause a denial of service (system crash) or possibly execute arbitrary
code. (CVE-2023-6176)
Xingyuan Mo discovered that the netfilter subsystem in the Linux kernel did
not properly handle dynset expressions passed from userspace, leading to a
null pointer dereference vulnerability. A local attacker could use this to
cause a denial of service (system crash). (CVE-2023-6622)
It was discovered that the TIPC protocol implementation in the Linux kernel
did not properly handle locking during tipc_crypto_key_revoke() operations.
A local attacker could use this to cause a denial of service (kernel
deadlock). (CVE-2024-0641)
Update instructions
The problem can be corrected by updating your system to the following package versions:
Ubuntu 22.04
-
linux-image-5.15.0-1036-gkeop
-
5.15.0-1036.42
-
linux-image-5.15.0-1044-nvidia
-
5.15.0-1044.44
-
linux-image-5.15.0-1044-nvidia-lowlatency
-
5.15.0-1044.44
-
linux-image-5.15.0-1046-ibm
-
5.15.0-1046.49
-
linux-image-5.15.0-1050-gke
-
5.15.0-1050.55
-
linux-image-5.15.0-1050-kvm
-
5.15.0-1050.55
-
linux-image-5.15.0-1051-gcp
-
5.15.0-1051.59
-
linux-image-5.15.0-1051-oracle
-
5.15.0-1051.57
-
linux-image-5.15.0-1053-aws
-
5.15.0-1053.58
-
linux-image-5.15.0-94-generic
-
5.15.0-94.104
-
linux-image-5.15.0-94-generic-64k
-
5.15.0-94.104
-
linux-image-5.15.0-94-generic-lpae
-
5.15.0-94.104
-
linux-image-aws-lts-22.04
-
5.15.0.1053.52
-
linux-image-gcp-lts-22.04
-
5.15.0.1051.47
-
linux-image-generic
-
5.15.0.94.91
-
linux-image-generic-64k
-
5.15.0.94.91
-
linux-image-generic-lpae
-
5.15.0.94.91
-
linux-image-gke
-
5.15.0.1050.49
-
linux-image-gke-5.15
-
5.15.0.1050.49
-
linux-image-gkeop
-
5.15.0.1036.35
-
linux-image-gkeop-5.15
-
5.15.0.1036.35
-
linux-image-ibm
-
5.15.0.1046.42
-
linux-image-kvm
-
5.15.0.1050.46
-
linux-image-nvidia
-
5.15.0.1044.44
-
linux-image-nvidia-lowlatency
-
5.15.0.1044.44
-
linux-image-oracle
-
5.15.0.1051.46
-
linux-image-oracle-lts-22.04
-
5.15.0.1051.46
-
linux-image-virtual
-
5.15.0.94.91
Ubuntu 20.04
-
linux-image-5.15.0-1036-gkeop
-
5.15.0-1036.42~20.04.1
-
linux-image-5.15.0-1046-ibm
-
5.15.0-1046.49~20.04.1
-
linux-image-5.15.0-1051-gcp
-
5.15.0-1051.59~20.04.1
-
linux-image-5.15.0-1051-oracle
-
5.15.0-1051.57~20.04.1
-
linux-image-5.15.0-1053-aws
-
5.15.0-1053.58~20.04.1
-
linux-image-5.15.0-94-generic
-
5.15.0-94.104~20.04.1
-
linux-image-5.15.0-94-generic-64k
-
5.15.0-94.104~20.04.1
-
linux-image-5.15.0-94-generic-lpae
-
5.15.0-94.104~20.04.1
-
linux-image-5.15.0-94-lowlatency
-
5.15.0-94.104~20.04.1
-
linux-image-5.15.0-94-lowlatency-64k
-
5.15.0-94.104~20.04.1
-
linux-image-aws
-
5.15.0.1053.58~20.04.41
-
linux-image-gcp
-
5.15.0.1051.59~20.04.1
-
linux-image-generic-64k-hwe-20.04
-
5.15.0.94.104~20.04.50
-
linux-image-generic-hwe-20.04
-
5.15.0.94.104~20.04.50
-
linux-image-generic-lpae-hwe-20.04
-
5.15.0.94.104~20.04.50
-
linux-image-gkeop-5.15
-
5.15.0.1036.42~20.04.32
-
linux-image-ibm
-
5.15.0.1046.49~20.04.18
-
linux-image-lowlatency-64k-hwe-20.04
-
5.15.0.94.104~20.04.47
-
linux-image-lowlatency-hwe-20.04
-
5.15.0.94.104~20.04.47
-
linux-image-oem-20.04
-
5.15.0.94.104~20.04.50
-
linux-image-oem-20.04b
-
5.15.0.94.104~20.04.50
-
linux-image-oem-20.04c
-
5.15.0.94.104~20.04.50
-
linux-image-oem-20.04d
-
5.15.0.94.104~20.04.50
-
linux-image-oracle
-
5.15.0.1051.57~20.04.1
-
linux-image-virtual-hwe-20.04
-
5.15.0.94.104~20.04.50
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.