Your submission was sent successfully! Close

Thank you for contacting us. A member of our team will be in touch shortly. Close

You have successfully unsubscribed! Close

Thank you for signing up for our newsletter!
In these regular emails you will find the latest updates about Ubuntu and upcoming events where you can meet our team.Close

LSN-0106-1: Kernel Live Patch Security Notice

20 August 2024

Several security issues were fixed in the kernel.

Releases

Software Description

  • aws - Linux kernel for Amazon Web Services (AWS) systems - (>= 4.15.0-1054, >= 4.15.0-1159, >= 4.15.0-1119, >= 5.4.0-1009, >= 5.4.0-1061, >= 5.15.0-1000, >= 6.8.0-1008, >= 4.4.0-1098, >= 4.4.0-1129, >= 4.4.0-1159)
  • aws-5.15 - Linux kernel for Amazon Web Services (AWS) systems - (>= 5.15.0-1000)
  • aws-hwe - Linux kernel for Amazon Web Services (AWS-HWE) systems - (>= 4.15.0-1126)
  • azure - Linux kernel for Microsoft Azure Cloud systems - (>= 5.4.0-1010, >= 5.15.0-1000, >= 6.8.0-1007, >= 4.15.0-1063, >= 4.15.0-1078, >= 4.15.0-1114)
  • azure-4.15 - Linux kernel for Microsoft Azure Cloud systems - (>= 4.15.0-1115, >= 4.15.0-1168)
  • gcp - Linux kernel for Google Cloud Platform (GCP) systems - (>= 5.4.0-1009, >= 5.15.0-1000, >= 6.8.0-1007, >= 4.15.0-1118)
  • gcp-4.15 - Linux kernel for Google Cloud Platform (GCP) systems - (>= 4.15.0-1121, >= 4.15.0-1154)
  • gcp-5.15 - Linux kernel for Google Cloud Platform (GCP) systems - (>= 5.15.0-1000)
  • generic-4.15 - Linux hardware enablement (HWE) kernel - (>= 4.15.0-69, >= 4.15.0-214, >= 4.15.0-69, >= 4.15.0-143, >= 4.15.0-143)
  • generic-4.4 - Linux kernel - (>= 4.4.0-168, >= 4.4.0-168, >= 4.4.0-211, >= 4.4.0-243)
  • generic-5.15 - Linux hardware enablement (HWE) kernel - (>= 5.15.0-0)
  • generic-5.4 - Linux kernel - (>= 5.4.0-26, >= 5.4.0-150, >= 5.4.0-26)
  • gke - Linux kernel for Google Container Engine (GKE) systems - (>= 5.15.0-1000)
  • gkeop - Linux kernel for Google Container Engine (GKE) systems - (>= 5.4.0-1009)
  • ibm - Linux kernel for IBM cloud systems - (>= 5.4.0-1009, >= 5.15.0-1000, >= 6.8.0-1005)
  • ibm-5.15 - Linux kernel for IBM cloud systems - (>= 5.15.0-1000)
  • linux - Linux kernel - (>= 5.15.0-71, >= 5.15.0-24, >= 6.8.0-1)
  • lowlatency-4.15 - Linux hardware enablement (HWE) kernel - (>= 4.15.0-69, >= 4.15.0-214, >= 4.15.0-69, >= 4.15.0-143, >= 4.15.0-143)
  • lowlatency-4.4 - Linux kernel - (>= 4.4.0-168, >= 4.4.0-168, >= 4.4.0-211, >= 4.4.0-243)
  • lowlatency-5.15 - Linux hardware enablement (HWE) kernel - (>= 5.15.0-0)
  • lowlatency-5.4 - Linux kernel - (>= 5.4.0-26, >= 5.4.0-150, >= 5.4.0-26)
  • oracle - Linux kernel for Oracle Cloud systems - (>= 4.15.0-1129, >= 5.4.0-1121, >= 5.15.0-1055)
  • oracle-5.15 - Linux kernel for Oracle Cloud systems - (>= 5.15.0-1055)

Details

In the Linux kernel, the following vulnerability has been
resolved: netfilter: nf_tables: disallow timeout for anonymous sets Never
used from userspace, disallow these parameters.(CVE-2023-52620)

In the Linux kernel, the following vulnerability has been
resolved: tls: fix race between tx work scheduling and socket close
Similarly to previous commit, the submitting thread (recvmsg/sendmsg) may
exit as soon as the async crypto handler calls complete(). Reorder
scheduling the work before calling complete(). This seems more logical in
the first place, as it's the inverse order of what the submitting thread
will do.(CVE-2024-26585)

In the Linux kernel, the following vulnerability has been
resolved: tty: n_gsm: fix possible out-of-bounds in gsm0_receive() Assuming
the following: - side A configures the n_gsm in basic option mode - side B
sends the header of a basic option mode frame with data length 1 - side A
switches to advanced option mode - side B sends 2 data bytes which exceeds
gsm->len Reason: gsm->len is not used in advanced option mode. - side A
switches to basic option mode - side B keeps sending until gsm0_receive()
writes past gsm->buf Reason: Neither gsm->state nor gsm->len have been
reset after reconfiguration. Fix this by changing gsm->count to gsm->len
comparison from equal to less than. Also add upper limit checks against the
constant MAX_MRU in gsm0_receive() and gsm1_receive() to harden against
memory corruption of gsm->len and gsm->mru. All other checks remain as we
still need to limit the data according to the user configuration and actual
payload size.(CVE-2024-36016)

Checking update status

The problem can be corrected in these Livepatch versions:

Kernel type 24.04 22.04 20.04 18.04 16.04 14.04
aws 106.1 106.1 106.1 106.1 106.1
aws-5.15 106.1
aws-hwe 106.1
azure 106.1 106.1 106.1 106.1
azure-4.15 106.1
gcp 106.1 106.1 106.1 106.1
gcp-4.15 106.1
gcp-5.15 106.1
generic-4.15 106.1 106.1
generic-4.4 106.1 106.1
generic-5.15 106.1
generic-5.4 106.1 106.1
gke 106.1
gkeop 106.1
ibm 106.1 106.1 106.1
ibm-5.15 106.1
linux 106.1 106.1
lowlatency-4.15 106.1 106.1
lowlatency-4.4 106.1 106.1
lowlatency-5.15 106.1
lowlatency-5.4 106.1 106.1
oracle 106.1 106.1 106.1
oracle-5.15 106.1

To check your kernel type and Livepatch version, enter this command:

canonical-livepatch status