focal/linux: 5.4.0-190.210 -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: d68191af651f1c9f
  route-entry: 2
comments:
  abi-testing: 1
delta:
  promote-to-proposed: [lrm, lrs, main, meta, signed, lrg, generate]
  promote-to-updates: [lrm, lrs, 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-13026
packages:
  generate: linux-generate
  lrg: linux-restricted-generate
  lrm: linux-restricted-modules
  lrs: linux-restricted-signatures
  main: linux
  meta: linux-meta
  signed: linux-signed
phase: Complete
phase-changed: Thursday, 25. July 2024 00:27 UTC
reason: {}
synthetic:
  :promote-to-as-proposed: Invalid
trackers:
  bionic/linux-hwe-5.4: bug 2072107
  focal/linux-aws: bug 2072063
  focal/linux-azure: bug 2072066
  focal/linux-bluefield: bug 2072067
  focal/linux-ein: bug 2072082
  focal/linux-fips: bug 2072083
  focal/linux-gcp: bug 2072086
  focal/linux-gkeop: bug 2072087
  focal/linux-havana: bug 2072090
  focal/linux-ibm: bug 2072092
  focal/linux-iot: bug 2072097
  focal/linux-kvm: bug 2072098
  focal/linux-nuremberg: bug 2072101
  focal/linux-oracle: bug 2072103
  focal/linux-raspi: bug 2072074
  focal/linux-uc20-efi: bug 2072105
  focal/linux-xilinx-zynqmp: bug 2072106
variant: debs
versions:
  lrm: 5.4.0-190.210
  main: 5.4.0-190.210
  meta: 5.4.0.190.188
  signed: 5.4.0-190.210
~~:
  announce:
    swm-transition-crankable: 2024-07-04 20:15:51.465050
  clamps:
    new-review: d68191af651f1c9f
    promote-to-proposed: d68191af651f1c9f
    self: 5.4.0-190.210
    sru-review: d68191af651f1c9f
  tracker:
    last-message: '2024-07-24 20:14:31.218036+00:00'

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

amd64/generic canonical-certs.pem unchanged
amd64/generic canonical-revoked-certs.pem unchanged
amd64/generic fwinfo unchanged
amd64/generic modules unchanged
amd64/generic retpoline unchanged
amd64/lowlatency canonical-certs.pem unchanged
amd64/lowlatency canonical-revoked-certs.pem unchanged
amd64/lowlatency fwinfo unchanged
amd64/lowlatency modules unchanged
amd64/lowlatency retpoline unchanged
arm64/generic canonical-certs.pem unchanged
arm64/generic canonical-revoked-certs.pem unchanged
arm64/generic fwinfo unchanged
arm64/generic modules unchanged
arm64/generic retpoline unchanged
armhf/generic canonical-certs.pem unchanged
armhf/generic canonical-revoked-certs.pem unchanged
armhf/generic fwinfo unchanged
armhf/generic modules differs
  @@ -5251,6 +5251,7 @@
   team_mode_roundrobin
   tee
   tef6862
  +tegra-aconnect (ok)
   tegra-bpmp-thermal
   tegra-drm
   tegra-gmi
  @@ -5259,6 +5260,7 @@
   tegra-vde
   tegra186-cpufreq
   tegra20-devfreq
  +tegra210-adma (ok)
   tegra30-devfreq
   tegra_cec
   tegra_nand
armhf/generic retpoline unchanged
armhf/generic-lpae canonical-certs.pem unchanged
armhf/generic-lpae canonical-revoked-certs.pem unchanged
armhf/generic-lpae fwinfo unchanged
armhf/generic-lpae modules unchanged
armhf/generic-lpae retpoline unchanged
ppc64el/generic canonical-certs.pem unchanged
ppc64el/generic canonical-revoked-certs.pem unchanged
ppc64el/generic fwinfo unchanged
ppc64el/generic modules unchanged
ppc64el/generic retpoline unchanged
s390x/generic canonical-certs.pem unchanged
s390x/generic canonical-revoked-certs.pem unchanged
s390x/generic fwinfo unchanged
s390x/generic modules unchanged
s390x/generic retpoline unchanged

[Manuel Diewald (diewald)]

No new regressions found. Metal instance 'exotic-skunk' locked by another user and hence unable to deploy, 'wright-kernel' has been blocked by another job for over a week. Furthermore, we observed this issue on instance 'blanka':
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2072972
The issue can be reproduced with older kernel versions and is hence no regression, technically.

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux - 5.4.0-190.210

---------------
linux (5.4.0-190.210) focal; urgency=medium

  * 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

 -- Manuel Diewald <email address hidden> Fri, 05 Jul 2024 17:04:36 +0200

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

All tasks have been completed and the bug is being closed