jammy/linux-raspi: 5.15.0-1059.62 -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: 30dd3b0d4127fa8c
  route-entry: 2
comments:
  abi-testing: 1
delta:
  promote-to-proposed: [main, meta]
  promote-to-security: []
  promote-to-updates: [main, meta]
flag:
  boot-testing-requested: true
  bugs-spammed: true
  proposed-announcement-sent: true
  proposed-testing-requested: true
  stream-from-cycle: true
issue: KSRU-13018
kernel-stable-master-bug: 2072059
packages:
  main: linux-raspi
  meta: linux-meta-raspi
phase: Complete
phase-changed: Monday, 29. July 2024 20:56 UTC
reason: {}
synthetic:
  :promote-to-as-proposed: Invalid
trackers:
  jammy/linux-raspi/pi-kernel: bug 2072051
variant: debs
versions:
  main: 5.15.0-1059.62
  meta: 5.15.0.1059.57
~~:
  announce:
    swm-transition-crankable: 2024-07-16 11:38:28.317937
  clamps:
    new-review: 30dd3b0d4127fa8c
    promote-to-proposed: 30dd3b0d4127fa8c
    self: 5.15.0-1059.62
    sru-review: 30dd3b0d4127fa8c
  tracker:
    last-message: '2024-07-29 12:01:49.360920+00:00'

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

arm64/raspi canonical-certs.pem unchanged
arm64/raspi canonical-revoked-certs.pem unchanged
arm64/raspi fwinfo unchanged
arm64/raspi modules differs
  @@ -4171,14 +4171,11 @@
   sch5627
   sch5636
   sch56xx-common
  -sch_atm (rejected)
   sch_cake
  -sch_cbq (rejected)
   sch_cbs
   sch_choke
   sch_codel
   sch_drr
  -sch_dsmark (rejected)
   sch_etf
   sch_ets
   sch_fq
arm64/raspi retpoline unchanged
armhf/raspi canonical-certs.pem unchanged
armhf/raspi canonical-revoked-certs.pem unchanged
armhf/raspi fwinfo unchanged
armhf/raspi modules differs
  @@ -4180,14 +4180,11 @@
   sch5627
   sch5636
   sch56xx-common
  -sch_atm (rejected)
   sch_cake
  -sch_cbq (rejected)
   sch_cbs
   sch_choke
   sch_codel
   sch_drr
  -sch_dsmark (rejected)
   sch_etf
   sch_ets
   sch_fq
armhf/raspi retpoline unchanged

[Juerg Haefliger (juergh)]

Missing modules sch_* is OK. From master:

net/sched: Retire CBQ qdisc
UBUNTU: [Config] updateconfigs for NET_SCH_CBQ
net/sched: Retire ATM qdisc
UBUNTU: [Config] updateconfigs for NET_SCH_ATM
net/sched: Retire dsmark qdisc

[Stefan Bader (smb)]

The parent got hinted and there is nothing raspi specific to be verified.

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux-raspi - 5.15.0-1059.62

---------------
linux-raspi (5.15.0-1059.62) jammy; urgency=medium

  * jammy/linux-raspi: 5.15.0-1059.62 -proposed tracker (LP: #2072052)

  [ Ubuntu: 5.15.0-117.127 ]

  * jammy/linux: 5.15.0-117.127 -proposed tracker (LP: #2072059)
  * CVE-2024-27017
    - netfilter: nft_set_pipapo: constify lookup fn args where possible
    - netfilter: nft_set_pipapo: walk over current view on netlink dump
    - netfilter: nf_tables: missing iterator type in lookup walk
  * CVE-2024-26952
    - ksmbd: fix potencial out-of-bounds when buffer offset is invalid
  * CVE-2024-26886
    - Bluetooth: af_bluetooth: Fix deadlock
  * CVE-2023-52752
    - smb: client: fix use-after-free bug in cifs_debug_data_proc_show()
  * CVE-2024-25742
    - x86/sev: Harden #VC instruction emulation somewhat
    - x86/sev: Check for MWAITX and MONITORX opcodes in the #VC handler
  * CVE-2024-36016
    - tty: n_gsm: fix possible out-of-bounds in gsm0_receive()

  [ Ubuntu: 5.15.0-116.126 ]

  * jammy/linux: 5.15.0-116.126 -proposed tracker (LP: #2071603)
  * idxd: NULL pointer dereference reading wq op_config attribute (LP: #2069081)
    - SAUCE: dmaengine: idxd: set is_visible member of idxd_wq_attribute_group
  * AMD GPUs fail with null pointer dereference when IOMMU enabled, leading to
    black screen (LP: #2068738)
    - SAUCE: Revert "drm/amdgpu: init iommu after amdkfd device init"

 -- Juerg Haefliger <email address hidden> Tue, 16 Jul 2024 16:45:45 +0200

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

All tasks have been completed and the bug is being closed