focal/linux-gcp-5.13: 5.13.0-1027.32~20.04.1 -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 --
boot-testing-requested: true
built:
  from: 0e5c02e8dc3b7015
  route-entry: 1
delta:
  promote-to-proposed: [main, lrs, meta, signed, lrm, lrg]
  promote-to-security: []
  promote-to-updates: [meta, signed, lrs, main, lrm]
issue: KSRU-2241
kernel-stable-master-bug: 1973933
packages:
  lrg: linux-restricted-generate-gcp-5.13
  lrm: linux-restricted-modules-gcp-5.13
  lrs: linux-restricted-signatures-gcp-5.13
  main: linux-gcp-5.13
  meta: linux-meta-gcp-5.13
  signed: linux-signed-gcp-5.13
phase: Complete
phase-changed: Monday, 30. May 2022 21:26 UTC
proposed-announcement-sent: true
reason: {}
synthetic:
  :promote-to-as-proposed: Fix Released
variant: debs
versions:
  lrm: 5.13.0-1027.32~20.04.1
  main: 5.13.0-1027.32~20.04.1
  meta: 5.13.0.1027.32~20.04.1
  signed: 5.13.0-1027.32~20.04.1
~~:
  clamps:
    new-review: 0e5c02e8dc3b7015
    promote-to-proposed: 0e5c02e8dc3b7015
    self: 5.13.0-1027.32~20.04.1
    sru-review: 0e5c02e8dc3b7015

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux-gcp-5.13 - 5.13.0-1027.32~20.04.1

---------------
linux-gcp-5.13 (5.13.0-1027.32~20.04.1) focal; urgency=medium

  * focal/linux-gcp-5.13: 5.13.0-1027.32~20.04.1 -proposed tracker
    (LP: #1973932)

  * Packaging resync (LP: #1786013)
    - [Packaging] update variants

  [ Ubuntu: 5.13.0-1027.32 ]

  * impish/linux-gcp: 5.13.0-1027.32 -proposed tracker (LP: #1973933)
  * impish/linux: 5.13.0-44.49 -proposed tracker (LP: #1973941)
  * CVE-2022-29581
    - net/sched: cls_u32: fix netns refcount changes in u32_change()
  * Unprivileged users may use PTRACE_SEIZE to set PTRACE_O_SUSPEND_SECCOMP
    option (LP: #1972740)
    - ptrace: Check PTRACE_O_SUSPEND_SECCOMP permission on PTRACE_SEIZE
  * ext4: limit length to bitmap_maxbytes (LP: #1972281)
    - ext4: limit length to bitmap_maxbytes - blocksize in punch_hole

 -- Joseph Salisbury <email address hidden> Wed, 25 May 2022 19:11:47 -0400

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

All tasks have been completed and the bug is being closed