This bug was fixed in the package linux-lowlatency - 5.15.0-33.34
--------------- linux-lowlatency (5.15.0-33.34) jammy; urgency=medium
* jammy/linux-lowlatency: 5.15.0-33.34 -proposed tracker (LP: #1973907)
[ Ubuntu: 5.15.0-33.34 ]
* jammy/linux: 5.15.0-33.34 -proposed tracker (LP: #1973924) * CVE-2022-29581 - net/sched: cls_u32: fix netns refcount changes in u32_change() * 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
-- Stefan Bader <email address hidden> Wed, 18 May 2022 17:24:45 +0200
This bug was fixed in the package linux-lowlatency - 5.15.0-33.34
---------------
linux-lowlatency (5.15.0-33.34) jammy; urgency=medium
* jammy/linux- lowlatency: 5.15.0-33.34 -proposed tracker (LP: #1973907)
[ Ubuntu: 5.15.0-33.34 ]
* jammy/linux: 5.15.0-33.34 -proposed tracker (LP: #1973924) O_SUSPEND_ SECCOMP O_SUSPEND_ SECCOMP permission on PTRACE_SEIZE
* CVE-2022-29581
- net/sched: cls_u32: fix netns refcount changes in u32_change()
* 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_
option (LP: #1972740)
- ptrace: Check PTRACE_
-- Stefan Bader <email address hidden> Wed, 18 May 2022 17:24:45 +0200