This bug was fixed in the package linux - 5.15.0-33.34
---------------
linux (5.15.0-33.34) jammy; urgency=medium
* 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 protected]> Wed, 18 May 2022 15:11:00
+0200
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1972281
Title:
ext4: limit length to bitmap_maxbytes
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Trusty:
In Progress
Status in linux source package in Xenial:
In Progress
Status in linux source package in Bionic:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in linux source package in Impish:
Fix Released
Status in linux source package in Jammy:
Fix Released
Bug description:
[Impact]
Abusing ext4_fallocate() (as a normal user) triggers a BUG()/kernel panic.
[Fix]
Apply this upstream fix:
commit 2da376228a2427501feb9d15815a45dbdbdd753e
Author: Tadeusz Struk <[email protected]>
Date: Thu Mar 31 13:05:15 2022 -0700
ext4: limit length to bitmap_maxbytes - blocksize in punch_hole
[Test]
The reporter has provided a working reproducer.
[Where problems could occur]
Upstream fix already slated for @stable inclusion.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972281/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
