focal/linux-azure-5.15: 5.15.0-1029.36~20.04.1 -proposed tracker

[Tim Gardner]

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: 44f801ce1f5375ee
  route-entry: 2
delta:
  promote-to-proposed: [lrm, main, signed, lrs, meta, lrg]
  promote-to-security: []
  promote-to-updates: [lrs, lrm, signed, main, meta]
flag:
  boot-testing-requested: true
  bugs-respammed: true
  proposed-announcement-sent: true
  proposed-testing-requested: true
  stream-from-cycle: true
issue: KSRU-5839
kernel-stable-master-bug: 1998845
packages:
  lrg: linux-restricted-generate-azure-5.15
  lrm: linux-restricted-modules-azure-5.15
  lrs: linux-restricted-signatures-azure-5.15
  main: linux-azure-5.15
  meta: linux-meta-azure-5.15
  signed: linux-signed-azure-5.15
phase: Complete
phase-changed: Tuesday, 13. December 2022 13:46 UTC
reason: {}
synthetic:
  :promote-to-as-proposed: Invalid
trackers:
  focal/linux-azure-fde-5.15: bug 1998945
variant: debs
versions:
  lrm: 5.15.0-1029.36~20.04.1
  main: 5.15.0-1029.36~20.04.1
  meta: 5.15.0.1029.36~20.04.19
  signed: 5.15.0-1029.36~20.04.1
~~:
  clamps:
    new-review: 44f801ce1f5375ee
    promote-to-proposed: 44f801ce1f5375ee
    self: 5.15.0-1029.36~20.04.1
    sru-review: 44f801ce1f5375ee

[Launchpad Janitor (janitor)]

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

[Tim Gardner (timg-tpi)]

ADT: No regressions

[Tim Gardner (timg-tpi)]

RT: No regressions. Ignoring some transient network access failures.

[Tim Gardner (timg-tpi)]

This was a bug fix upload and does not involve security patches. Marking Invalid on Thadeu Cascardo's advice.

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux-azure-5.15 - 5.15.0-1029.36~20.04.1

---------------
linux-azure-5.15 (5.15.0-1029.36~20.04.1) focal; urgency=medium

  * focal/linux-azure-5.15: 5.15.0-1029.36~20.04.1 -proposed tracker
    (LP: #1998946)

  [ Ubuntu: 5.15.0-1029.36 ]

  * jammy/linux-azure: 5.15.0-1029.36 -proposed tracker (LP: #1998845)
  * Azure: Jammy fio test hangs, swiotlb buffers exhausted (LP: #1998838)
    - SAUCE: scsi: storvsc: Fix swiotlb bounce buffer leak in confidential VM

  [ Ubuntu: 5.15.0-1027.33 ]

  * jammy/linux-azure: 5.15.0-1027.33 -proposed tracker (LP: #1997044)
  * jammy/linux: 5.15.0-56.62 -proposed tracker (LP: #1997079)
  * CVE-2022-3566
    - tcp: Fix data races around icsk->icsk_af_ops.
  * CVE-2022-3567
    - ipv6: annotate some data-races around sk->sk_prot
    - ipv6: Fix data races around sk->sk_prot.
  * CVE-2022-3621
    - nilfs2: fix NULL pointer dereference at nilfs_bmap_lookup_at_level()
  * CVE-2022-3564
    - Bluetooth: L2CAP: Fix use-after-free caused by l2cap_reassemble_sdu
  * CVE-2022-3524
    - tcp/udp: Fix memory leak in ipv6_renew_options().
  * CVE-2022-3565
    - mISDN: fix use-after-free bugs in l1oip timer handlers
  * CVE-2022-3594
    - r8152: Rate limit overflow messages
  * CVE-2022-43945
    - SUNRPC: Fix svcxdr_init_decode's end-of-buffer calculation
    - SUNRPC: Fix svcxdr_init_encode's buflen calculation
    - NFSD: Protect against send buffer overflow in NFSv2 READDIR
    - NFSD: Protect against send buffer overflow in NFSv3 READDIR
    - NFSD: Protect against send buffer overflow in NFSv2 READ
    - NFSD: Protect against send buffer overflow in NFSv3 READ
    - NFSD: Remove "inline" directives on op_rsize_bop helpers
    - NFSD: Cap rsize_bop result based on send buffer size
  * CVE-2022-42703
    - mm/rmap: Fix anon_vma->degree ambiguity leading to double-reuse
  * 5.15.0-53-generic no longer boots (LP: #1996740)
    - drm/amd/display: Add helper for blanking all dp displays

  [ Ubuntu: 5.15.0-1024.30 ]

  * jammy/linux-azure: 5.15.0-1024.30 -proposed tracker (LP: #1996817)
  * Azure: Jammy fio test causes panic (LP: #1996806)
    - scsi: storvsc: Fix unsigned comparison to zero

 -- Tim Gardner <email address hidden> Tue, 06 Dec 2022 09:42:46 -0700

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

All tasks have been completed and the bug is being closed