Comment 1 for bug 1973951

This bug was fixed in the package linux-azure-5.4 - 5.4.0-1080.83~18.04.2

---------------
linux-azure-5.4 (5.4.0-1080.83~18.04.2) bionic; urgency=medium

  * bionic/linux-azure-5.4: 5.4.0-1080.83~18.04.2 -proposed tracker
    (LP: #1973951)

  * Miscellaneous Ubuntu changes
    - [Config] azure-5.4: Bionic gcc cannot support CONFIG_STACKPROTECTOR

linux-azure-5.4 (5.4.0-1080.83~18.04.1) bionic; urgency=medium

  * bionic/linux-azure-5.4: 5.4.0-1080.83~18.04.1 -proposed tracker
    (LP: #1973951)

  [ Ubuntu: 5.4.0-1080.83 ]

  * focal/linux-azure: 5.4.0-1080.83 -proposed tracker (LP: #1973952)
  * focal/linux: 5.4.0-113.127 -proposed tracker (LP: #1973980)
  * CVE-2022-29581
    - net/sched: cls_u32: fix netns refcount changes in u32_change()
  * CVE-2022-1116
    - io_uring: fix fs->users overflow
  * ext4: limit length to bitmap_maxbytes (LP: #1972281)
    - ext4: limit length to bitmap_maxbytes - blocksize in punch_hole
  * 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

 -- Tim Gardner <email address hidden> Thu, 19 May 2022 12:30:51 -0600