This bug was fixed in the package linux-riscv - 5.8.0-22.24
---------------
linux-riscv (5.8.0-22.24) groovy; urgency=medium
[ Ubuntu: 5.8.0-50.56 ]
* overlayfs calls vfs_setxattr without cap_convert_nscap
- vfs: move cap_convert_nscap() call into vfs_setxattr()
* CVE-2021-3492
- SAUCE: shiftfs: free allocated memory in shiftfs_btrfs_ioctl_fd_replace()
error paths
- SAUCE: shiftfs: handle copy_to_user() return values correctly
* CVE-2021-29154
- SAUCE: bpf, x86: Validate computation of branch displacements for x86-64
- SAUCE: bpf, x86: Validate computation of branch displacements for x86-32
-- Kelsey Skunberg <kelsey.skunb...@canonical.com> Mon, 12 Apr 2021
15:36:17 -0600
** Changed in: linux-riscv (Ubuntu Groovy)
Status: Fix Committed => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-29154
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3492
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv in Ubuntu.
https://bugs.launchpad.net/bugs/1917433
Title:
riscv: revert SiFive Unleashed CPUFreq
Status in linux-riscv package in Ubuntu:
Fix Released
Status in linux-riscv source package in Groovy:
Fix Released
Bug description:
== SRU Justifcation Groovy/RISCV ==
The SiFive Unleashed board with the current Ubuntu cpufreq default
config can hang on boot with CPU freq enabled with the latest device
tree settings. It is known that the cpufreq can be problematic so the
recommended way forward is to currently revert the cpufreq enablement
commit
commit 3949df6ecdca04339bc8a3925c2ba7f881cf82b1
Author: David Abdurachmanov <david.abdurachma...@sifive.com>
Date: Tue Jan 28 02:55:56 2020 -0800
SiFive Unleashed CPUFreq
== The fix(es) ==
Revert commit "SiFive Unleashed CPUFreq"
== Test Case ==
Boot with the latest DT. It should now boot. Boot without the latest
DT, it should also boot.
== Where problems could occur ==
1. Users expecting CPU freq scaling now don't have this working
option. This is deemed to be acceptable as without the fix their
systems are likely to be unbootable with the updated DT.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1917433/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
