jammy/linux-intel-iotg: 5.15.0-1061.67 -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: 5a8395e85953729c
  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-13005
kernel-stable-master-bug: 2072059
packages:
  generate: linux-generate-intel-iotg
  lrg: linux-restricted-generate-intel-iotg
  lrm: linux-restricted-modules-intel-iotg
  lrs: linux-restricted-signatures-intel-iotg
  main: linux-intel-iotg
  meta: linux-meta-intel-iotg
  signed: linux-signed-intel-iotg
phase: Complete
phase-changed: Thursday, 25. July 2024 00:24 UTC
reason: {}
synthetic:
  :promote-to-as-proposed: Invalid
trackers:
  focal/linux-intel-iotg-5.15: bug 2072043
  jammy/linux-uc22-intel-iotg: bug 2072039
variant: debs
versions:
  lrm: 5.15.0-1061.67
  main: 5.15.0-1061.67
  meta: 5.15.0.1061.61
  signed: 5.15.0-1061.67
~~:
  announce:
    swm-transition-crankable: 2024-07-11 10:50:22.631578
  clamps:
    new-review: 5a8395e85953729c
    promote-to-proposed: 5a8395e85953729c
    self: 5.15.0-1061.67
    sru-review: 5a8395e85953729c
  tracker:
    last-message: '2024-07-24 20:22:22.690100+00:00'

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

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

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux-intel-iotg - 5.15.0-1061.67

---------------
linux-intel-iotg (5.15.0-1061.67) jammy; urgency=medium

  * jammy/linux-intel-iotg: 5.15.0-1061.67 -proposed tracker (LP: #2072044)

  [ 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"

 -- Thibault Ferrante <email address hidden> Fri, 12 Jul 2024 10:38:58 +0200

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

All tasks have been completed and the bug is being closed