This bug is awaiting verification that the linux-mtk/5.15.0-1030.34
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy-
linux-mtk'. If the pro
This bug is awaiting verification that the linux-nvidia/5.15.0-1011.11
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-
bluefield/5.15.0-1010.12 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy' to 'verification-
done-jammy'. If the problem still ex
This bug is awaiting verification that the linux-
gkeop-5.15/5.15.0-1005.7~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal' to
'verification-done-focal'. If the problem s
This bug was fixed in the package linux - 5.15.0-50.56
---
linux (5.15.0-50.56) jammy; urgency=medium
* jammy/linux: 5.15.0-50.56 -proposed tracker (LP: #1990148)
* CVE-2022-3176
- io_uring: refactor poll update
- io_uring: move common poll bits
- io_uring: kill poll
I ran the original reproducer on a VM that was running
linux/5.15.0-50.56 and linux/linux/5.15.0-46.49. On the former the
problem did not reproduce, but on the latter it did. Marking this as
verified via testing and setting 'verification-done-jammy'.
** Tags added: verification-done-jammy
--
Y
This bug is awaiting verification that the linux/5.15.0-50.56 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-jammy' to 'verification-done-jammy'. If the problem
still exists, change t
@Stefan thanks for explaining how the process works. I appreciate your
willingness to take this patch ahead of its arrival in the stable pull
for the Jammy train. One of your updates mentioned TBD on a test. I
have a reproducer in the original cover letter to Steven here, if it
helps:
https://l
@Krister, no the affected series is related to where the primarily
affected kernel version sits. For 5.15 kernels this is 22.04/Jammy. On
AWS the custom kernels used, roll. So it is a 5.15 based kernel. 5.4
would be the native Focal kernel. But that is not affected. So this
overall is not tracked a
Should this also get nominated as affecting Focal? I hit this on the
5.15 kernel that was attached to linux-aws for Focal.
--
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/1987232
Title:
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: Confirmed
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
Status: Ne
The fix has also been added to the Stable queue for 5.15 and 5.19 as of
this morning:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-
queue.git/tree/queue-5.19/tracing-perf-fix-double-put-of-trace-event-
when-init-fails.patch
https://git.kernel.org/pub/scm/linux/kernel/git/stable/s
apport information
** Tags added: apport-collected focal uec-images
** Description changed:
I have systems that are regularly hitting a WARN in
trace_event_dyn_put_ref.
The exact message is:
WARNING: CPU: 1 PID: 30309 at kernel/trace/trace_dynevent.c:46
+trace_event_dyn_put_ref+0
13 matches
Mail list logo
