focal/linux: 5.4.0-151.168 -proposed tracker

[Roxana Nicolescu]

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: 0d9a42437a03bc1a
  route-entry: 1
delta:
  promote-to-proposed: [lrm, lrs, main, meta, signed, lrg, generate]
flag:
  boot-testing-requested: true
  bugs-spammed: true
  proposed-announcement-sent: true
  proposed-testing-requested: true
issue: KSRU-7434
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: Ready for Testing
phase-changed: Wednesday, 07. June 2023 20:57 UTC
reason:
  certification-testing: Ongoing -s testing in progress
  kernel-signoff: Stalled -s waiting for signoff
synthetic:
  :promote-to-as-proposed: Fix Released
trackers:
  bionic/linux-hwe-5.4: bug 2019374
  focal/linux-aws: bug 2019346
  focal/linux-azure: bug 2019349
  focal/linux-bluefield: bug 2019350
  focal/linux-fips: bug 2019351
  focal/linux-gcp: bug 2019354
  focal/linux-gke: bug 2019355
  focal/linux-gkeop: bug 2019356
  focal/linux-ibm: bug 2019358
  focal/linux-iot: bug 2019361
  focal/linux-kvm: bug 2019362
  focal/linux-nv-dgx: bug 2019363
  focal/linux-oracle: bug 2019365
  focal/linux-raspi: bug 2019369
  focal/linux-uc20-efi: bug 2019371
  focal/linux-xilinx-zynqmp: bug 2019372
variant: debs
versions:
  lrm: 5.4.0-151.168
  main: 5.4.0-151.168
  meta: 5.4.0.151.148
  signed: 5.4.0-151.168
~~:
  clamps:
    new-review: 0d9a42437a03bc1a
    promote-to-proposed: 0d9a42437a03bc1a
    self: 5.4.0-151.168
    sru-review: 0d9a42437a03bc1a

[Stefan Bader (smb)]

I would call it good. For GCP there is one instance type which usually gives trouble (failing the warnings check) and for bare metal one amd64 is good and the other has deployment problems which sounds like MaaS issues.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Marcin Janowski (janowski-m)]

I would like to ask if anyone knows with why the patch has not been released yet?

[Luke Nowakowski-Krijger (lukenow)]

Hi @janowski-m , Which patch are you referring to specifically? Do you have a bug report for the patch you're looking for? This is a generic bug tracker for tracking the kernel release.

[Marcin Janowski (janowski-m)]

Thanks for reploy, i'm waiting for patch on CVE-2023-32233, i cannot use mitigations.

[Thadeu Lima de Souza Cascardo (cascardo)]

You can install 5.4.0-150 from ppa:canonical-kernel-team/proposed2. That version has the fix for CVE-2023-32233 and other vulnerabilities.

[Launchpad Janitor (janitor)]

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

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

  * focal/linux: 5.4.0-152.169 -proposed tracker (LP: #2023070)

  * Focal update: v5.4.236 upstream stable release (LP: #2020390)
    - wifi: cfg80211: Partial revert "wifi: cfg80211: Fix use after free for wext"

  * Packaging resync (LP: #1786013)
    - [Packaging] resync git-ubuntu-log
    - [Packaging] resync getabis

linux (5.4.0-151.168) focal; urgency=medium

  * focal/linux: 5.4.0-151.168 -proposed tracker (LP: #2019375)

  * Packaging resync (LP: #1786013)
    - [Packaging] update helper scripts
    - debian/dkms-versions -- update from kernel-versions (main/2023.05.15)

  * CVE-2023-32233
    - netfilter: nf_tables: deactivate anonymous set from preparation phase

  * CVE-2023-2612
    - SAUCE: shiftfs: prevent lock unbalance in shiftfs_create_object()

  * CVE-2023-31436
    - net: sched: sch_qfq: prevent slab-out-of-bounds in qfq_activate_agg

  * CVE-2023-1380
    - wifi: brcmfmac: slab-out-of-bounds read in brcmf_get_assoc_ies()

  * Focal update: Focal update: v5.4.235 upstream stable release (LP: #2017706)
    - HID: asus: Remove check for same LED brightness on set
    - HID: asus: use spinlock to protect concurrent accesses
    - HID: asus: use spinlock to safely schedule workers
    - ARM: OMAP2+: Fix memory leak in realtime_counter_init()
    - arm64: dts: qcom: qcs404: use symbol names for PCIe resets
    - ARM: zynq: Fix refcount leak in zynq_early_slcr_init
    - arm64: dts: meson-gx: Fix Ethernet MAC address unit name
    - arm64: dts: meson-g12a: Fix internal Ethernet PHY unit name
    - arm64: dts: meson-gx: Fix the SCPI DVFS node name and unit address
    - arm64: dts: meson: remove CPU opps below 1GHz for G12A boards
    - ARM: OMAP1: call platform_device_put() in error case in
      omap1_dm_timer_init()
    - ARM: dts: exynos: correct wr-active property in Exynos3250 Rinato
    - ARM: imx: Call ida_simple_remove() for ida_simple_get
    - arm64: dts: amlogic: meson-gx: fix SCPI clock dvfs node name
    - arm64: dts: amlogic: meson-axg: fix SCPI clock dvfs node name
    - arm64: dts: amlogic: meson-gx: add missing SCPI sensors compatible
    - arm64: dts: amlogic: meson-gx: add missing unit address to rng node name
    - arm64: dts: amlogic: meson-gxl: add missing unit address to eth-phy-mux node
      name
    - arm64: dts: amlogic: meson-gxl-s905d-phicomm-n1: fix led node name
    - ARM: dts: imx7s: correct iomuxc gpr mux controller cells
    - arm64: dts: mediatek: mt7622: Add missing pwm-cells to pwm node
    - Revert "scsi: core: run queue if SCSI device queue isn't ready and queue is
      idle"
    - block: Limit number of items taken from the I/O scheduler in one go
    - blk-mq: remove stale comment for blk_mq_sched_mark_restart_hctx
    - blk-mq: wait on correct sbitmap_queue in blk_mq_mark_tag_wait
    - blk-mq: correct stale comment of .get_budget
    - s390/dasd: Prepare for additional path event handling
    - s390/dasd: Fix potential memleak in dasd_eckd_init()
    - sched/deadline,rt: Remove unused parameter from pick_next_[rt|dl]_entity()
    - sched/rt: pick_next_rt_entity(): che...