This bug was fixed in the package linux - 4.15.0-147.151
---
linux (4.15.0-147.151) bionic; urgency=medium
* CVE-2021-3444
- bpf: Fix truncation handling for mod32 dst reg wrt zero
* CVE-2021-3600
- SAUCE: bpf: Do not use ax register in interpreter on div/mod
- bpf:
This bug was fixed in the package linux-azure - 5.8.0-1036.38
---
linux-azure (5.8.0-1036.38) 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 CAN
This bug was fixed in the package linux-raspi - 5.4.0-1038.41
---
linux-raspi (5.4.0-1038.41) focal; urgency=medium
[ Ubuntu: 5.4.0-77.86 ]
* 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-azure - 5.4.0-1051.53
---
linux-azure (5.4.0-1051.53) focal; urgency=medium
[ Ubuntu: 5.4.0-77.86 ]
* 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-azure - 5.11.0-1009.9
---
linux-azure (5.11.0-1009.9) 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)
-
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)
-
This bug was fixed in the package linux-azure - 5.8.0-1036.38
---
linux-azure (5.8.0-1036.38) 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 CAN
This bug was fixed in the package linux-meta-azure - 5.4.0.1051.49
---
linux-meta-azure (5.4.0.1051.49) focal; urgency=medium
* Bump ABI 5.4.0-1051
-- Stefan Bader Thu, 17 Jun 2021 19:43:45
+0200
** Changed in: linux-meta-azure-5.8 (Ubuntu Focal)
Status: Fix Committed
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
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)
-
This bug was fixed in the package linux-meta-azure-5.8 -
5.8.0.1036.38~20.04.8
---
linux-meta-azure-5.8 (5.8.0.1036.38~20.04.8) focal; urgency=medium
* Bump ABI 5.8.0-1036.38~20.04
* Cloud kernels meta don't provide kernel-testing--*--modules-extra--preferred
(LP: #1931576)
This bug was fixed in the package linux-hwe-5.8 - 5.8.0-59.66~20.04.1
---
linux-hwe-5.8 (5.8.0-59.66~20.04.1) focal; 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
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-aws - 5.11.0-1011.11
---
linux-aws (5.11.0-1011.11) 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.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)
-
This bug was fixed in the package linux - 4.15.0-147.151
---
linux (4.15.0-147.151) bionic; urgency=medium
* CVE-2021-3444
- bpf: Fix truncation handling for mod32 dst reg wrt zero
* CVE-2021-3600
- SAUCE: bpf: Do not use ax register in interpreter on div/mod
- bpf:
This bug was fixed in the package linux-raspi - 5.4.0-1038.41
---
linux-raspi (5.4.0-1038.41) focal; urgency=medium
[ Ubuntu: 5.4.0-77.86 ]
* 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.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)
-
This bug was fixed in the package linux-azure-5.8 -
5.8.0-1036.38~20.04.1
---
linux-azure-5.8 (5.8.0-1036.38~20.04.1) focal; urgency=medium
[ Ubuntu: 5.8.0-1036.38 ]
* UAF on CAN J1939 j1939_can_recv (LP: #1932209)
- SAUCE: can: j1939: delay release of j1939_priv after
This bug was fixed in the package linux - 4.15.0-147.151
---
linux (4.15.0-147.151) bionic; urgency=medium
* CVE-2021-3444
- bpf: Fix truncation handling for mod32 dst reg wrt zero
* CVE-2021-3600
- SAUCE: bpf: Do not use ax register in interpreter on div/mod
- bpf:
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)
-
This bug was fixed in the package linux-aws - 5.8.0-1038.40
---
linux-aws (5.8.0-1038.40) 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 CAN BCM
This bug was fixed in the package linux-azure - 5.4.0-1051.53
---
linux-azure (5.4.0-1051.53) focal; urgency=medium
[ Ubuntu: 5.4.0-77.86 ]
* 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 - 4.15.0-147.151
---
linux (4.15.0-147.151) bionic; urgency=medium
* CVE-2021-3444
- bpf: Fix truncation handling for mod32 dst reg wrt zero
* CVE-2021-3600
- SAUCE: bpf: Do not use ax register in interpreter on div/mod
- bpf:
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)
-
I just want to say that after 2 years I remembered I had an SSD with
different brand tham Samsung, a Kingston one. I installed it on my razer
and it worked perfectly for days, I did several SSD stress tests and no
errors.
The error is defintely with Samsung AND linux. And it's not a faulty SSD
** Changed in: ubuntu-certification
Status: New => Invalid
--
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/1845418
Title:
Wifi is Slow
Status in Ubuntu-Certification:
Invalid
Unclear what changed but I haven't been able to reproduce this issue in
a week or so. My computer is now running:
5.11.0-18-generic
When I reported the bug it was using:
5.11.0-17-generic
--
You received this bug notification because you are a member of Kernel
Packages, which is
You seem to be right : the hdmi monitor seems to be reset... This didn't happen
a few weeks ago (maybe 21.04 update).
Here is the output of xrandr :
###
Initial xrandr result, when no problem is present (except that the hdmi monitor
refresh rate should be 144Hz but is detected at 120, maybe this
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)
-
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)
-
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)
-
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)
-
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)
-
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)
-
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
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)
-
The x1e.xlarge and m3.large AWS instances report 0-14 as possible CPUs
(/sys/devices/system/cpu/possible) even though they have 4 or 2 CPUs
respectively. This should be fixed with LTP commit 14797491f1cc
("cpuset_hotplug_test.sh: Fix bug for obtaining task_cpus value in
root/generic_cpu_hotplut
@fmalfoy it was fixed with the 06-04 round of sru updates.
Does the new linux-base from proposed not resolve the reported
regressions for you?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-base in Ubuntu.
The verification of the Stable Release Update for crash has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
This bug was fixed in the package crash - 7.2.8-1ubuntu1.20.10.2
---
crash (7.2.8-1ubuntu1.20.10.2) groovy; urgency=medium
* Fix FTBFS (LP: #1931435):
- d/p/0004-Fix-for-an-ARM64-gcc-10-compilation-error.-Without-t.patch
crash (7.2.8-1ubuntu1.20.10.1) groovy; urgency=medium
This bug was fixed in the package crash - 7.2.8-1ubuntu1.20.10.2
---
crash (7.2.8-1ubuntu1.20.10.2) groovy; urgency=medium
* Fix FTBFS (LP: #1931435):
- d/p/0004-Fix-for-an-ARM64-gcc-10-compilation-error.-Without-t.patch
crash (7.2.8-1ubuntu1.20.10.1) groovy; urgency=medium
This bug was fixed in the package crash - 7.2.8-1ubuntu0.18.04.2
---
crash (7.2.8-1ubuntu0.18.04.2) bionic; urgency=medium
* Fix cannot determine VA_BITS_ACTUAL (LP: #1919275):
- d/p/0003-arm64-Change-tcr_el1_t1sz-variable-name-to-TCR_EL1_T.patch
-- Ioanna Alifieraki Wed,
The verification of the Stable Release Update for crash has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
This bug was fixed in the package crash - 7.2.8-1ubuntu1.20.04.1
---
crash (7.2.8-1ubuntu1.20.04.1) focal; urgency=medium
* Fix cannot determine VA_BITS_ACTUAL (LP: #1919275):
- d/p/0003-arm64-Change-tcr_el1_t1sz-variable-name-to-TCR_EL1_T.patch
-- Ioanna Alifieraki Thu, 15
** Summary changed:
- placeholder bug
+ UAF on CAN J1939 j1939_can_recv
** Description changed:
- Another bug.
+ [Impact]
+ j1939_can_recv may run concurrently to can_rx_unregister on
j1939_netdev_stop, which will, then, free the priv struct that is used by
j1939_can_recv, leading to a system
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
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/1931546
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)
-
This bug was fixed in the package linux-meta-aws - 5.4.0.1051.53
---
linux-meta-aws (5.4.0.1051.53) focal; urgency=medium
* Bump ABI 5.4.0-1051
-- Stefan Bader Thu, 17 Jun 2021 19:24:12
+0200
** Changed in: linux-meta-aws (Ubuntu Focal)
Status: Fix Committed => Fix
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)
-
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)
-
Public bug reported:
Can't turn on the bluetooth on 21.04. Using bluetoothctl these are the
returns:
```
bluetoothctl
Agent registered
[CHG] Controller 60:14:B3:AC:14:C8 Pairable: yes
[bluetooth]# connect 60:14:B3:AC:14:C8
Device 60:14:B3:AC:14:C8 not available
[bluetooth]# scan on
Failed to
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either
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)
-
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)
-
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)
-
** Changed in: linux (Ubuntu Groovy)
Status: New => In Progress
** Changed in: linux (Ubuntu Groovy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Groovy)
Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)
** Changed in: linux (Ubuntu)
Status: Confirmed
I should mention that bluetooth was working on 20.04 and 20.10 but after
upgrade to 21.04 it doesn't work anymore.
--
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/1933259
Title:
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)
-
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)
-
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)
-
** Description changed:
-
- SRU Justification
-
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by
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)
-
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)
This bug was fixed in the package linux-meta-gcp - 5.4.0.1046.55
---
linux-meta-gcp (5.4.0.1046.55) focal; urgency=medium
* Bump ABI 5.4.0-1046
* Cloud kernels meta don't provide kernel-testing--*--modules-extra--preferred
(LP: #1931576)
- [Packaging] Fix provides for
Testing:
1. install -proposed thermald
2. stop thermald:
sudo systemctl stop thermald
3. capture stdout + stderr output using script command, run thermald
manually to capture logging:
script
sudo thermald --no-daemon --loglevel=debug --ignore-cpuid-check
4. run stress-ng in another terminal
** Summary changed:
- placeholder bug
+ UAF on CAN BCM bcm_rx_handler
** Description changed:
- This reports a bug.
+ [Impact]
+ bcm_rx_handler may run concurrently to can_rx_unregister on bcm_release,
which will, then, free the bcm_op that is used by bcm_rx_handler, leading to a
system
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-aws - 5.4.0-1051.53
---
linux-aws (5.4.0-1051.53) focal; urgency=medium
[ Ubuntu: 5.4.0-77.86 ]
* UAF on CAN J1939 j1939_can_recv (LP: #1932209)
- SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu
* UAF on CAN BCM
This bug was fixed in the package linux - 4.15.0-147.151
---
linux (4.15.0-147.151) bionic; urgency=medium
* CVE-2021-3444
- bpf: Fix truncation handling for mod32 dst reg wrt zero
* CVE-2021-3600
- SAUCE: bpf: Do not use ax register in interpreter on div/mod
- bpf:
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)
-
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu Cosmic)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
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/1836167
Title:
cpuhotplug03 in cpuhotplug from ubuntu_ltp failed on some
Followup: the patch "linux/bits.h: fix compilation error with GENMASK" has been
omitted
(reference https://bugs.launchpad.net/bugs/1932585)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
Tracing this back, I found the current Ubuntu 5.11 kernel has incorrect
offsets for some platforms (TGL-H and ADL). I created an upstream bug at
https://gitlab.freedesktop.org/drm/intel/-/issues/3662 and was directed
to a commit, 5d0c938ec9cc, that ought to fix this issue.
Can you please try to Hibernate your laptop to disk, then start it again
and test the LAN connection? On my Fujitsu S7311 with I219-LM with
Ubuntu kernel 5.10.0-18-generic hibernating running OS to disk and then
turning it on makes LAN working as expected without any error (no
special kernel
** Attachment added: "bluez_5.59-0ubuntu1.debian.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1933078/+attachment/5506368/+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
*** This bug is a duplicate of bug 1926062 ***
https://bugs.launchpad.net/bugs/1926062
** This bug has been marked a duplicate of bug 1926062
[hirsute/impish] Can't turn bluetooth on again after turning it off
--
You received this bug notification because you are a member of Kernel
Hello koba, or anyone else affected,
Accepted linux-firmware into hirsute-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.197.2 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** 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/1933274
Title:
TGL-H skl_dram_get_dimm_info crashes with "Missing case (val ==
65535)"
Status in linux package in
** Description changed:
+ [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]
+
+ *
@Georgi, would you please try the last drm-tip(amd64)?
https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1922334
On hold again since there's also a fix for bug 1926062 coming.
--
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/1933078
Title:
BlueZ 5.59 release
Status in bluez package in Ubuntu:
In
*** This bug is a duplicate of bug 1926062 ***
https://bugs.launchpad.net/bugs/1926062
** This bug has been marked a duplicate of bug 1926062
[hirsute/impish] Can't turn bluetooth on again after turning it off
--
You received this bug notification because you are a member of Kernel
Hi @Daniel,
Yes, it has not been upstreamed yet. Linux-bluetooth does not reply the thread,
maybe I'll have a try to send mail to them.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
1 - 100 of 205 matches
Mail list logo