This isn't related to kernels 5.4 or above as Debian Bullseye (5.10
kernel) is giving me no issues on
- ibm thinkpad r50p (pentium m, 1gb ram, amd/ati mobility firegl t2;
rv350/m10 gl)
I expect the same on t42p as well (I just haven't got to testing that
yet).
In support I was just telling peopl
Public bug reported:
On the mainline kernel server, all folders for kernels v5.10.37 to
v5.10.45 contain packages for kernel v5.11.0.
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.10.37/
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: build kernel mainli
** Description changed:
[Impact]
Test case cfs_bandwidth01 in LTP sched test suite is a reproducer
of a CFS unthrottle_cfs_rq() issue (fe61468b2cbc2b sched/fair: Fix
enqueue_task_fair warning).
This test triggers a warning on our 4.15 kernel:
- LTP: starting cfs_bandwidth01 (cfs_band
Seems previous findings - hirsute/azure and groovy/oracle might not be
correct as the "Test wakeup tracer" passes.
--
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/1873054
Title:
Test Wake
@rbalint @ddstreed any update on this issue?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1919177
Title:
Azure: issues with accelerated networking on Hirsute
Status in cloud-ini
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-450 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubunt
A couple of other behaviours I have observed now that may be useful for
figuring this one out:
1. When this monitor (Benq EX2780Q) goes to standby, it stops showing
signs of life on the signal line. This manifests as it disappearing
completely from the system, including the sound output and the di
https://lists.ubuntu.com/archives/kernel-team/2021-June/121571.html
--
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/1931325
Title:
cfs_bandwidth01 in sched from ubuntu_ltp_stable failed o
You have been subscribed to a public bug:
lagg display
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-55-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
BootLog:
You have been subscribed to a public bug:
My dual display setup sometimes switches to a mirror display mode (from
joined display) when waking up from sleep.
This could be totally unrelated but I have two graphic cards, and both
screens are connected to the same one (Hdmi and display port).
Probl
Thanks for the bug report. Your kernel log is showing a couple of
different problems that would explain poor performance:
[ 1432.047693] pcieport :00:1c.4: AER: Corrected error received:
:00:1c.4
[ 1432.047705] pcieport :00:1c.4: AER: PCIe Bus Error: severity=Corrected,
type=Physical
Usually bugs like this happen when the system detects different monitor
capabilities, so it thinks it has a different monitor setup and reverts
to a default arrangement.
Please try running:
xrandr
before and after sleeping, and then compare the results.
** Summary changed:
- Display mode aft
** Changed in: ubuntu-kernel-tests
Assignee: Sean Feole (sfeole) => Krzysztof Kozlowski (krzk)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1783881
Title:
ltp-syscalls: msgs
** Also affects: alsa-lib (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-lib in Ubuntu.
https://bugs.launchpad.net/bugs/1921452
Title:
[SRU] alsa-lib: conf: USB - add "Cm
> similar to bug #1907886 if upstream decided to include it in the
noinst set they might have a reason?
In bug 1907886 that consideration sounds like it was overridden by the
statement: "fedora is including it in their binary though, we could
probably do the same for Ubuntu".
As for this bug, 'bt
** Changed in: alsa-lib (Ubuntu Bionic)
Status: New => In Progress
** Changed in: alsa-lib (Ubuntu Bionic)
Importance: Undecided => Critical
** Changed in: alsa-lib (Ubuntu Bionic)
Assignee: (unassigned) => Hui Wang (hui.wang)
--
You received this bug notification because you are
** Attachment added: "bluez_5.59.orig.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1933078/+attachment/5506232/+files/bluez_5.59.orig.tar.xz
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.
Subscribe the sponsor team again, since our oem project needs this fix
to be landed to bionic too.
This is the debdiff for bionic, please help review and upload
thx.
** Patch added: "alsa-lib_1.1.3-5ubuntu0.6.debdiff"
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1921452/+attachme
** Attachment added: "bluez_5.59-0ubuntu1.debian.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1933078/+attachment/5506233/+files/bluez_5.59-0ubuntu1.debian.tar.xz
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in
This test can pass with the disco branch, so out of curiosity I ran a
bisect against kvm-unit-test and this test case seem to be the cause:
8726f9771911d6749dbd36ab2fc70f0f25e2b1a9 is the first bad commit
commit 8726f9771911d6749dbd36ab2fc70f0f25e2b1a9
Author: Jacob Xu
Date: Wed Apr 21 16:12:57
update debdiff of groovy.
** Patch added: "bluez_5.55-0ubuntu1.3~1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1933221/+attachment/5506235/+files/bluez_5.55-0ubuntu1.3~1.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subs
Public bug reported:
[Impact]
* On/off of Bluetooth in gnome-control-center will not work properly.
* Devices are not refreshed in the list anymore.
* The passed struct will depend on the length of the submitted read() and the
kernel version.
[Test Plan]
* Open gnome-control-center and
Sent patch to upstream (LTP):
https://lists.linux.it/pipermail/ltp/2021-June/023346.html
** Changed in: ubuntu-kernel-tests
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https
upload debdiff of hirsute
** Patch added: "bluez_5.56-0ubuntu4.2~1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1933221/+attachment/5506236/+files/bluez_5.56-0ubuntu4.2~1.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subs
https://gitlab.com/kvm-unit-tests/kvm-unit-
tests/-/commit/2805ff600e44936ce4d2c024f3ae81078c59658d
Note that even with this test removed, we might need to investigate if
we need to run this for older kernels.
--
You received this bug notification because you are a member of Kernel
Packages, whi
Needed a bit of tweaking to get this benchmarked. Had to enable zstd in
kmod package and also apply a hack to the kernel package building. (See
attachment).
So, the installed compressed kernel modules are 27.1 MB compared to the
uncompressed 99.1 MB. The compressed extra modules are 103 MB compare
I like smaller install size.
In many cases we boot without initrd by default (gcp, azure, aws, kvm).
Does it then make sense to enable this for the cloud kernels?
I ponder, if i can hack initramfs-tools to append compressed kernel modules as
an uncompressed cpio archive to the initramfs, instead
Attached is the diff of the kernel to build zstd modules. This is a hack
for the moment just to get benchmarks.
** Patch added: "diff to enable ZSTD compressed kernel modules"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932329/+attachment/5506241/+files/zstd-kernel-config.diff
--
Y
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Note that the download size is much larger. Doesn't that impact on the
amount of data that users download (which is quite large considering the
number of kernel updates we do)?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubunt
Note also the boot speed is not much different, so the I doubt we see
any noticeable boot performance wins on cloud images.
--
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/1932329
Title:
This bug is awaiting verification that the 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 still exists, change
the tag 'verificati
This bug is awaiting verification that the 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 still exists, change
the tag 'verificati
This bug is awaiting verification that the 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 still exists, change
the tag 'verificati
This bug is awaiting verification that the 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 still exists, change
the tag 'verificati
This bug is awaiting verification that the 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 still exists, change
the tag 'verificati
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-450 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubunt
Confirmed I had to jump through these hoops on a ThinkPad X1 Carbon 9th
Generation, with a Razer Core attached. Using 21.04.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu.
https://bugs.launchpad.net/
** Tags added: patch
--
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/1932329
Title:
Benchmark if we can compress kernel modules
Status in linux package in Ubuntu:
In Progress
Bug desc
** Tags added: hirsute
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu.
https://bugs.launchpad.net/bugs/1881701
Title:
NVIDIA cards should have set AllowExternalGpus in
/usr/share/X11/xorg.conf.d/
** Description changed:
+ [Impact]
+
Backport Linux kernel 5.11 SGX native support to new Azure Ubuntu 20.04
releases.
+ [Fix]
+
+ Update linux-base to add a UDEV rule to set group permissions on the SGX
device.
+ Add an environment variable to default to out-of-proc attestation.
+
+ [T
Ok, so the issue there was triggered by kernel changes, you can read the
details in the commit message of the GNOME fix
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/d2200632
The fix is in gnome-settings-daemon 3.38.2 in impish, bluez also
requires a similar fix which is being SRU
Are there any more informations under which specific configuration (like
modules, kernel parameters etc.)
https://ubuntu.com/certified/202104-28912 has been tested?
As described in the kernel bugtracker, the behaviour seems to flip from
time to time - sometimes already tested kernels do not work e
Thank you for clarification. Yes, system looks stable. The only thing
that bothers is that these messages are visible for a moment during
power off/suspend.
Please close this ticket
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** Changed in: bluez (Ubuntu)
Status: New => Fix Committed
** Changed in: bluez (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1933221
Tit
Do you need 20.10? I don't think we have kernels that trigger the issue
on that serie and I don't think it's worth the effort since it's non-LTS
and not-current-stable?
Upload to hirsute and focal now with the bug reference added to the
changelog as required by the SRU process
We will handle impi
I change bios configuration of motherboard, No freeze during last 30
days.
On Thu, Apr 8, 2021, 10:50 PM Daniel van Vugt <1919...@bugs.launchpad.net>
wrote:
> I don't see anything related in the logs, but a full system freeze could
> be another hardware problem. Not sure what to do next...
>
> **
I am also seeing this on a the AMD Ryzen desktop system Dell OptiPlex
5055 with Linux 5.13-rc7.
[0.00] DMI: Dell Inc. OptiPlex 5055 Ryzen CPU/0P03DX, BIOS 1.1.25
05/03/2021
[…]
[ 12.810715] wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control
method not found
[ 1
Public bug reported:
Hotplugging of CPUs does not work on Azure instances. See lp:1836166 for
cpuhotplug tests.
$ sudo ./runltp -f controllers -s cpuset_hotplug
cpuset_hotplug 1 TINFO: CPUs are numbered continuously starting at 0 (0-3)
cpuset_hotplug 1 TINFO: Nodes are numbered continuously star
Found also on: focal/5.4.0-1047.49-azure (Standard_F32s_v2)
focal/5.8.0-1033.35~20.04.1, focal/5.8.0-1034.36~20.04.1-azure
** Changed in: ubuntu-kernel-tests
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed t
Sent patch to upstream (LTP):
https://lists.linux.it/pipermail/ltp/2021-June/023368.html
--
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/1933247
Title:
cpuset_hotplug from controllers in
You have been subscribed to a public bug:
Hi,
Another issue with Qualcomm Atheros QCA6174 (very similar to
https://bugs.launchpad.net/ubuntu/+bug/1827879), this time using Mint
20.1/Ubuntu 20.04: when suspending laptop, firmware often (80%) crashes
(see kernel log at bottom). It prevents the comp
** Package changed: ubuntu => linux (Ubuntu)
--
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/1933201
Title:
ath10k_pci QCA6174 firmware crash on suspend
Status in linux package in Ubuntu
My problem has been gone for some time, but now it occurs again.
I'm sending prevboot.txt like you said above
sri, 2. lip 2021. u 18:16 Merima Fajić napisao
je:
> Im sorry, neglect earlier message please, I forgot to reboot
>
> On Wed, Jun 2, 2021, 13:36 Merima Fajić wrote:
>
>> last night I p
I've tested this on an older X220 with the air vents taped up while
running stress-ng and glxgears for 1 hour:
stress-ng --cpu 1 --matrix 4 --iomix 1 --cache 1 --icache 1
--thermalstat 1 --vmstat 10 -t 1h -v
I enabled the full debug logging and was able to observe thermald
throttling the CPU and
This bug was fixed in the package linux - 5.4.0-77.86
---
linux (5.4.0-77.86) focal; urgency=medium
* UAF on CAN J1939 j1939_can_recv (LP: #1932209)
- SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu
* UAF on CAN BCM bcm_rx_handler (LP: #1931855)
- SAU
This bug was fixed in the package linux - 5.8.0-59.66
---
linux (5.8.0-59.66) groovy; urgency=medium
* UAF on CAN J1939 j1939_can_recv (LP: #1932209)
- SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu
* UAF on CAN BCM bcm_rx_handler (LP: #1931855)
- SA
This bug was fixed in the package linux - 5.11.0-22.23
---
linux (5.11.0-22.23) hirsute; urgency=medium
* UAF on CAN J1939 j1939_can_recv (LP: #1932209)
- SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu
* UAF on CAN BCM bcm_rx_handler (LP: #1931855)
-
This bug was fixed in the package linux - 5.11.0-22.23
---
linux (5.11.0-22.23) hirsute; urgency=medium
* UAF on CAN J1939 j1939_can_recv (LP: #1932209)
- SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu
* UAF on CAN BCM bcm_rx_handler (LP: #1931855)
-
This bug was fixed in the package linux - 5.4.0-77.86
---
linux (5.4.0-77.86) focal; urgency=medium
* UAF on CAN J1939 j1939_can_recv (LP: #1932209)
- SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu
* UAF on CAN BCM bcm_rx_handler (LP: #1931855)
- SAU
This bug was fixed in the package linux - 5.4.0-77.86
---
linux (5.4.0-77.86) focal; urgency=medium
* UAF on CAN J1939 j1939_can_recv (LP: #1932209)
- SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu
* UAF on CAN BCM bcm_rx_handler (LP: #1931855)
- SAU
This bug was fixed in the package linux-oracle - 5.11.0-1010.10
---
linux-oracle (5.11.0-1010.10) hirsute; urgency=medium
[ Ubuntu: 5.11.0-22.23 ]
* UAF on CAN J1939 j1939_can_recv (LP: #1932209)
- SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu
* UAF o
This bug was fixed in the package linux-gcp - 5.11.0-1011.12
---
linux-gcp (5.11.0-1011.12) hirsute; urgency=medium
[ Ubuntu: 5.11.0-22.23 ]
* UAF on CAN J1939 j1939_can_recv (LP: #1932209)
- SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu
* UAF on CAN
This bug was fixed in the package linux - 5.11.0-22.23
---
linux (5.11.0-22.23) hirsute; urgency=medium
* UAF on CAN J1939 j1939_can_recv (LP: #1932209)
- SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu
* UAF on CAN BCM bcm_rx_handler (LP: #1931855)
-
This bug was fixed in the package linux - 5.11.0-22.23
---
linux (5.11.0-22.23) hirsute; urgency=medium
* UAF on CAN J1939 j1939_can_recv (LP: #1932209)
- SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu
* UAF on CAN BCM bcm_rx_handler (LP: #1931855)
-
This bug was fixed in the package linux - 5.4.0-77.86
---
linux (5.4.0-77.86) focal; urgency=medium
* UAF on CAN J1939 j1939_can_recv (LP: #1932209)
- SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu
* UAF on CAN BCM bcm_rx_handler (LP: #1931855)
- SAU
This bug was fixed in the package linux - 5.11.0-22.23
---
linux (5.11.0-22.23) hirsute; urgency=medium
* UAF on CAN J1939 j1939_can_recv (LP: #1932209)
- SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu
* UAF on CAN BCM bcm_rx_handler (LP: #1931855)
-
This bug was fixed in the package linux - 5.11.0-22.23
---
linux (5.11.0-22.23) hirsute; urgency=medium
* UAF on CAN J1939 j1939_can_recv (LP: #1932209)
- SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu
* UAF on CAN BCM bcm_rx_handler (LP: #1931855)
-
This bug was fixed in the package linux - 5.8.0-59.66
---
linux (5.8.0-59.66) groovy; urgency=medium
* UAF on CAN J1939 j1939_can_recv (LP: #1932209)
- SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu
* UAF on CAN BCM bcm_rx_handler (LP: #1931855)
- SA
This bug was fixed in the package linux - 5.4.0-77.86
---
linux (5.4.0-77.86) focal; urgency=medium
* UAF on CAN J1939 j1939_can_recv (LP: #1932209)
- SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu
* UAF on CAN BCM bcm_rx_handler (LP: #1931855)
- SAU
This bug was fixed in the package linux - 5.11.0-22.23
---
linux (5.11.0-22.23) hirsute; urgency=medium
* UAF on CAN J1939 j1939_can_recv (LP: #1932209)
- SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu
* UAF on CAN BCM bcm_rx_handler (LP: #1931855)
-
This bug was fixed in the package linux - 5.11.0-22.23
---
linux (5.11.0-22.23) hirsute; urgency=medium
* UAF on CAN J1939 j1939_can_recv (LP: #1932209)
- SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu
* UAF on CAN BCM bcm_rx_handler (LP: #1931855)
-
This bug was fixed in the package linux - 5.11.0-22.23
---
linux (5.11.0-22.23) hirsute; urgency=medium
* UAF on CAN J1939 j1939_can_recv (LP: #1932209)
- SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu
* UAF on CAN BCM bcm_rx_handler (LP: #1931855)
-
This bug was fixed in the package linux - 5.8.0-59.66
---
linux (5.8.0-59.66) groovy; urgency=medium
* UAF on CAN J1939 j1939_can_recv (LP: #1932209)
- SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu
* UAF on CAN BCM bcm_rx_handler (LP: #1931855)
- SA
This bug was fixed in the package linux - 5.8.0-59.66
---
linux (5.8.0-59.66) groovy; urgency=medium
* UAF on CAN J1939 j1939_can_recv (LP: #1932209)
- SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu
* UAF on CAN BCM bcm_rx_handler (LP: #1931855)
- SA
This bug was fixed in the package linux - 5.11.0-22.23
---
linux (5.11.0-22.23) hirsute; urgency=medium
* UAF on CAN J1939 j1939_can_recv (LP: #1932209)
- SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu
* UAF on CAN BCM bcm_rx_handler (LP: #1931855)
-
This bug was fixed in the package linux-raspi - 5.11.0-1012.13
---
linux-raspi (5.11.0-1012.13) hirsute; urgency=medium
[ Ubuntu: 5.11.0-22.23 ]
* UAF on CAN J1939 j1939_can_recv (LP: #1932209)
- SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu
* UAF on
This bug was fixed in the package linux - 5.4.0-77.86
---
linux (5.4.0-77.86) focal; urgency=medium
* UAF on CAN J1939 j1939_can_recv (LP: #1932209)
- SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu
* UAF on CAN BCM bcm_rx_handler (LP: #1931855)
- SAU
This bug was fixed in the package linux - 5.8.0-59.66
---
linux (5.8.0-59.66) groovy; urgency=medium
* UAF on CAN J1939 j1939_can_recv (LP: #1932209)
- SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu
* UAF on CAN BCM bcm_rx_handler (LP: #1931855)
- SA
This bug was fixed in the package linux - 5.11.0-22.23
---
linux (5.11.0-22.23) hirsute; urgency=medium
* UAF on CAN J1939 j1939_can_recv (LP: #1932209)
- SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu
* UAF on CAN BCM bcm_rx_handler (LP: #1931855)
-
This bug was fixed in the package linux - 5.11.0-22.23
---
linux (5.11.0-22.23) hirsute; urgency=medium
* UAF on CAN J1939 j1939_can_recv (LP: #1932209)
- SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu
* UAF on CAN BCM bcm_rx_handler (LP: #1931855)
-
This bug was fixed in the package linux - 5.8.0-59.66
---
linux (5.8.0-59.66) groovy; urgency=medium
* UAF on CAN J1939 j1939_can_recv (LP: #1932209)
- SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu
* UAF on CAN BCM bcm_rx_handler (LP: #1931855)
- SA
This bug was fixed in the package linux-raspi - 5.11.0-1012.13
---
linux-raspi (5.11.0-1012.13) hirsute; urgency=medium
[ Ubuntu: 5.11.0-22.23 ]
* UAF on CAN J1939 j1939_can_recv (LP: #1932209)
- SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu
* UAF on
This bug was fixed in the package linux - 5.11.0-22.23
---
linux (5.11.0-22.23) hirsute; urgency=medium
* UAF on CAN J1939 j1939_can_recv (LP: #1932209)
- SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu
* UAF on CAN BCM bcm_rx_handler (LP: #1931855)
-
This bug was fixed in the package linux - 5.4.0-77.86
---
linux (5.4.0-77.86) focal; urgency=medium
* UAF on CAN J1939 j1939_can_recv (LP: #1932209)
- SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu
* UAF on CAN BCM bcm_rx_handler (LP: #1931855)
- SAU
This bug was fixed in the package linux - 5.4.0-77.86
---
linux (5.4.0-77.86) focal; urgency=medium
* UAF on CAN J1939 j1939_can_recv (LP: #1932209)
- SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu
* UAF on CAN BCM bcm_rx_handler (LP: #1931855)
- SAU
This bug was fixed in the package linux - 5.11.0-22.23
---
linux (5.11.0-22.23) hirsute; urgency=medium
* UAF on CAN J1939 j1939_can_recv (LP: #1932209)
- SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu
* UAF on CAN BCM bcm_rx_handler (LP: #1931855)
-
This bug was fixed in the package linux - 5.11.0-22.23
---
linux (5.11.0-22.23) hirsute; urgency=medium
* UAF on CAN J1939 j1939_can_recv (LP: #1932209)
- SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu
* UAF on CAN BCM bcm_rx_handler (LP: #1931855)
-
This bug was fixed in the package linux-oracle - 5.8.0-1033.34
---
linux-oracle (5.8.0-1033.34) groovy; urgency=medium
[ Ubuntu: 5.8.0-59.66 ]
* UAF on CAN J1939 j1939_can_recv (LP: #1932209)
- SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu
* UAF on CA
This bug was fixed in the package linux - 5.8.0-59.66
---
linux (5.8.0-59.66) groovy; urgency=medium
* UAF on CAN J1939 j1939_can_recv (LP: #1932209)
- SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu
* UAF on CAN BCM bcm_rx_handler (LP: #1931855)
- SA
This bug was fixed in the package linux - 5.4.0-77.86
---
linux (5.4.0-77.86) focal; urgency=medium
* UAF on CAN J1939 j1939_can_recv (LP: #1932209)
- SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu
* UAF on CAN BCM bcm_rx_handler (LP: #1931855)
- SAU
This bug was fixed in the package linux - 5.11.0-22.23
---
linux (5.11.0-22.23) hirsute; urgency=medium
* UAF on CAN J1939 j1939_can_recv (LP: #1932209)
- SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu
* UAF on CAN BCM bcm_rx_handler (LP: #1931855)
-
This bug was fixed in the package linux - 5.8.0-59.66
---
linux (5.8.0-59.66) groovy; urgency=medium
* UAF on CAN J1939 j1939_can_recv (LP: #1932209)
- SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu
* UAF on CAN BCM bcm_rx_handler (LP: #1931855)
- SA
This bug was fixed in the package linux - 5.4.0-77.86
---
linux (5.4.0-77.86) focal; urgency=medium
* UAF on CAN J1939 j1939_can_recv (LP: #1932209)
- SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu
* UAF on CAN BCM bcm_rx_handler (LP: #1931855)
- SAU
This bug was fixed in the package linux - 5.4.0-77.86
---
linux (5.4.0-77.86) focal; urgency=medium
* UAF on CAN J1939 j1939_can_recv (LP: #1932209)
- SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu
* UAF on CAN BCM bcm_rx_handler (LP: #1931855)
- SAU
This bug was fixed in the package linux - 5.8.0-59.66
---
linux (5.8.0-59.66) groovy; urgency=medium
* UAF on CAN J1939 j1939_can_recv (LP: #1932209)
- SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu
* UAF on CAN BCM bcm_rx_handler (LP: #1931855)
- SA
This bug was fixed in the package linux - 5.4.0-77.86
---
linux (5.4.0-77.86) focal; urgency=medium
* UAF on CAN J1939 j1939_can_recv (LP: #1932209)
- SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu
* UAF on CAN BCM bcm_rx_handler (LP: #1931855)
- SAU
This bug was fixed in the package linux - 5.11.0-22.23
---
linux (5.11.0-22.23) hirsute; urgency=medium
* UAF on CAN J1939 j1939_can_recv (LP: #1932209)
- SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu
* UAF on CAN BCM bcm_rx_handler (LP: #1931855)
-
This bug was fixed in the package linux-meta-gcp-5.8 -
5.8.0.1035.37~20.04.9
---
linux-meta-gcp-5.8 (5.8.0.1035.37~20.04.9) focal; urgency=medium
* Bump ABI 5.8.0-1035.37~20.04
* Cloud kernels meta don't provide kernel-testing--*--modules-extra--preferred
(LP: #1931576)
-
1 - 100 of 214 matches
Mail list logo
