focal/linux-gkeop: 5.4.0-1096.100 -proposed tracker

[Stefan Bader]

This bug will contain status and test results related to a kernel source (or snap) as stated in the title.

For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

-- swm properties --
built:
  from: faf906eaf7628663
  route-entry: 2
comments:
  abi-testing: 1
delta:
  promote-to-proposed: [main, meta, signed, generate]
  promote-to-updates: [main, meta, signed]
flag:
  boot-testing-requested: true
  bugs-spammed: true
  proposed-announcement-sent: true
  proposed-testing-requested: true
  stream-from-cycle: true
issue: KSRU-13053
kernel-stable-master-bug: 2072108
packages:
  generate: linux-generate-gkeop
  main: linux-gkeop
  meta: linux-meta-gkeop
  signed: linux-signed-gkeop
phase: Complete
phase-changed: Thursday, 25. July 2024 00:26 UTC
reason: {}
synthetic:
  :promote-to-as-proposed: Invalid
variant: debs
versions:
  main: 5.4.0-1096.100
  meta: 5.4.0.1096.94
  signed: 5.4.0-1096.100
~~:
  announce:
    swm-transition-crankable: 2024-07-15 16:22:15.370339
  clamps:
    new-review: faf906eaf7628663
    promote-to-proposed: faf906eaf7628663
    self: 5.4.0-1096.100
    sru-review: faf906eaf7628663
  tracker:
    last-message: '2024-07-24 20:16:50.930903+00:00'

[Ubuntu Kernel Ancillary Bot (ubuntu-kernel-ancillary-bot)]

amd64/gkeop canonical-certs.pem unchanged
amd64/gkeop canonical-revoked-certs.pem unchanged
amd64/gkeop fwinfo unchanged
amd64/gkeop modules unchanged
amd64/gkeop retpoline unchanged

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux-gkeop - 5.4.0-1096.100

---------------
linux-gkeop (5.4.0-1096.100) focal; urgency=medium

  * focal/linux-gkeop: 5.4.0-1096.100 -proposed tracker (LP: #2072087)

  [ Ubuntu: 5.4.0-190.210 ]

  * focal/linux: 5.4.0-190.210 -proposed tracker (LP: #2072108)
  * CVE-2024-36016
    - tty: n_gsm: fix possible out-of-bounds in gsm0_receive()
  * CVE-2022-48655
    - firmware: arm_scmi: Harden accesses to the reset domains
  * CVE-2024-26907
    - RDMA/mlx5: Fix fortify source warning while accessing Eth segment
  * CVE-2024-26585
    - tls: fix race between tx work scheduling and socket close
  * CVE-2024-26584
    - net: tls: handle backlogging of crypto requests
  * CVE-2024-26583
    - net/tls: Replace TLS_RX_SYNC_RUNNING with RCU
    - net/tls: Fix use-after-free after the TLS device goes down and up
    - tls: splice_read: fix record type check
    - tls splice: remove inappropriate flags checking for MSG_PEEK
    - tls: splice_read: fix accessing pre-processed records
    - tls: Fix context leak on tls_device_down
    - net/tls: Check for errors in tls_device_init
    - net/tls: Remove the context from the list in tls_device_down
    - net/tls: pass context to tls_device_decrypted()
    - net/tls: Perform immediate device ctx cleanup when possible
    - net/tls: Multi-threaded calls to TX tls_dev_del
    - net: tls: avoid discarding data on record close
    - tls: rx: don't store the record type in socket context
    - tls: rx: don't store the decryption status in socket context
    - tls: rx: don't issue wake ups when data is decrypted
    - tls: rx: refactor decrypt_skb_update()
    - tls: hw: rx: use return value of tls_device_decrypted() to carry status
    - tls: rx: drop unnecessary arguments from tls_setup_from_iter()
    - tls: rx: don't report text length from the bowels of decrypt
    - tls: rx: wrap decryption arguments in a structure
    - tls: rx: factor out writing ContentType to cmsg
    - tls: rx: don't track the async count
    - tls: rx: assume crypto always calls our callback
    - tls: rx: use async as an in-out argument
    - tls: decrement decrypt_pending if no async completion will be called
    - net: tls: fix async vs NIC crypto offload
    - tls: rx: simplify async wait
    - tls: extract context alloc/initialization out of tls_set_sw_offload
    - net: tls: factor out tls_*crypt_async_wait()
    - tls: fix race between async notify and socket close

 -- Jacob Martin <email address hidden> Mon, 15 Jul 2024 13:54:26 -0500

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

All tasks have been completed and the bug is being closed