focal/linux-gke: 5.4.0-1072.77 -proposed tracker

Bug #1973961 reported by Stefan Bader
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Kernel SRU Workflow
Fix Committed
Medium
Unassigned
Automated-testing
Fix Released
Medium
Canonical Kernel Team
Boot-testing
Fix Released
Medium
Unassigned
Certification-testing
Invalid
Medium
Unassigned
New-review
Fix Released
Undecided
Unassigned
Prepare-package
Fix Released
Medium
Khaled El Mously
Prepare-package-meta
Fix Released
Medium
Khaled El Mously
Prepare-package-signed
Fix Released
Medium
Khaled El Mously
Promote-signing-to-proposed
Invalid
Medium
Unassigned
Promote-to-proposed
Fix Released
Medium
Ubuntu Stable Release Updates Team
Promote-to-security
Fix Released
Medium
Andy Whitcroft
Promote-to-updates
Fix Released
Medium
Andy Whitcroft
Regression-testing
Invalid
Medium
Canonical Kernel Team
Security-signoff
Fix Released
Medium
Steve Beattie
Sru-review
Fix Released
Medium
Andy Whitcroft
Verification-testing
Fix Released
Medium
Canonical Kernel Team
linux-gke (Ubuntu)
Focal
Fix Released
Medium
Unassigned

Bug Description

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
bugs-spammed: true
built:
  from: 826580dcbb911dc2
  route-entry: 1
delta:
  promote-to-proposed: [main, signed, meta]
  promote-to-security: []
  promote-to-updates: [signed, main, meta]
issue: KSRU-2190
kernel-stable-master-bug: 1973980
packages:
  main: linux-gke
  meta: linux-meta-gke
  signed: linux-signed-gke
phase: Complete
phase-changed: Thursday, 26. May 2022 09:17 UTC
proposed-announcement-sent: true
reason: {}
synthetic:
  :promote-to-as-proposed: Fix Released
trackers:
  bionic/linux-gke-5.4: bug 1973960
variant: debs
versions:
  main: 5.4.0-1072.77
  meta: 5.4.0.1072.81
  signed: 5.4.0-1072.77
~~:
  clamps:
    new-review: 826580dcbb911dc2
    promote-to-proposed: 826580dcbb911dc2
    self: 5.4.0-1072.77
    sru-review: 826580dcbb911dc2

CVE References

Stefan Bader (smb)
tags: added: kernel-release-tracking-bug-live
description: updated
tags: added: kernel-sru-cycle-2022.04.18-9
description: updated
tags: added: kernel-sru-derivative-of-1973980
Changed in kernel-sru-workflow:
status: New → Confirmed
importance: Undecided → Medium
Changed in linux-gke (Ubuntu Focal):
importance: Undecided → Medium
Changed in kernel-sru-workflow:
status: Confirmed → Triaged
description: updated
Changed in kernel-sru-workflow:
status: Triaged → In Progress
tags: added: kernel-jira-issue-ksru-2190
description: updated
description: updated
summary: - focal/linux-gke: <version to be filled> -proposed tracker
+ focal/linux-gke: 5.4.0-1072.77 -proposed tracker
description: updated
description: updated
Andy Whitcroft (apw)
tags: added: kernel-signing-bot
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
tags: added: boot-testing-passed
description: updated
tags: added: automated-testing-passed
description: updated
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux-gke - 5.4.0-1072.77

---------------
linux-gke (5.4.0-1072.77) focal; urgency=medium

  * focal/linux-gke: 5.4.0-1072.77 -proposed tracker (LP: #1973961)

  [ Ubuntu: 5.4.0-113.127 ]

  * 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

 -- Khalid Elmously <email address hidden> Thu, 19 May 2022 03:15:21 -0400

Changed in linux-gke (Ubuntu Focal):
status: New → Fix Released
description: updated
description: updated
description: updated
description: updated
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Workflow done!

All tasks have been completed and the bug is being closed

Changed in kernel-sru-workflow:
status: In Progress → Fix Committed
description: updated
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers