Public bug reported:
heppp
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: memtest86+ 6.20-3
ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-27-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Sun
Public bug reported:
Looks like this was a breaking change introduced in 0.2.9 release in Jan
2022, it has since been patched
https://github.com/NilsBrause/waylandpp/releases
Debian article about the bug https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=1006812
Which would be good since
What is the actual fix for this. I have run into this multiple times. Is
there a specific edit that needs to be made to the stanza in netplan?
After reviewing the netplan docs I was unable to find a corresponding
directive for allow-hotplug with /etc/network/interfaces.
$ lsb_release -a
No LSB
Dmitri's (or rather the Redditer's) solution also worked for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971985
Title:
Kernel 5.17.5-76051705 not supported
To manage notifications about
I'm having the same issue (on Pop 22.04 too).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971985
Title:
Kernel 5.17.5-76051705 not supported
To manage notifications about this bug go to:
Hello,
I tried to verify this SRU, but halfway through the process... realized
I was pulling from -updates (current) and not -proposed... and even so,
I could not replicate the bug:
So I guess it's fixed?
Tyler
---
# Boot a clean cloud-init'd 18.04 image:
ubuntu@dev-10-34-138-116
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964802
Title:
[SRU] ceph 15.2.16
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1964802/+subscriptions
** Description changed:
Please see the information at https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=1004671
- This is present in the current dev repos for Jammy, due to the updated
+ This is present in the current dev repos for Jammy, due to the unupdated
Biber package.
It
Public bug reported:
Please see the information at https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=1004671
This is present in the current dev repos for Jammy, due to the updated
Biber package.
It breaks a lot of Latex workflows, including
Found the problem - for some reason the systemctl service getty@tty[1-4] has a
prerequisite of /dev/tty0 existing. If it is not, all the tty[1-4] do not
start. (tty1 fails, the others are not tried)
SEE below - "ConditionPathExists=/dev/tty0 was not met"
systemctl status getty@tty1
○
Just a thought, should we change the name of this report from cgroups to
something "lxc-console only works for console tty0, not tty[1-4]" in
impish?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
to re-create the issue,
1 clean install of impish
# probably need sudo or be root for the following
2 boot into impish and install all updates
3 apt get install "lxc lxcfs lxc-utils lxc-templates lxctl"
4 lxc-create -n test -t ubuntu
5 lxc-start test
6 lxc-console -n test
# the above command FAILS
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1594023
Title:
Poweroff or reboot hangs. Laptop won't shutdown. 16.04
To manage notifications about this bug go to:
other information:-
container installed is from ubuntu template
can start/stop container
lxc-attach works
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947811
Title:
cgroups broken in impish
To
Public bug reported:
fresh install, all updates installed.
install lxc + lxcfs
symptom - can't sudo lxc-console -n lxcmachine (lxc-console works, but no
reponse/tty)
symptom - sudo ls -laF /var/lib/lxcfs
produces:-
---
ls: cannot access
Public bug reported:
If when I resize the gnome-terminal window it becomes too narrow to fit
the entire length of the bash prompt, it prints parts of the prompt to
the above line. It should just wrap the portion of the prompt that
exceeds the window width to the next line, but the characters that
*** This bug is a duplicate of bug 1915056 ***
https://bugs.launchpad.net/bugs/1915056
Public bug reported:
Ubuntu 20.10 Installation ISO was Downloaded 14:50 Feb 12, 2021 - ISO Burned to
DVD RW on 12:35 Feb 13, 2021
- Bug happened at around 90% finished while installing Ubuntu 20.10 from
We have also been bitten by this. Apologies if this does not help solve
the bug, but this issue has been floating for quite awhile and the
following may help future cloud operators...
In our case, we trying to re-IP ALL of our Ceph Mons. As Corey
mentioned, this bug report is for *Cinder
** Changed in: mutter (Ubuntu Bionic)
Assignee: Daniel van Vugt (vanvugt) => Tyler Alexander Driggers (exderia)
** Changed in: mutter (Ubuntu Bionic)
Assignee: Tyler Alexander Driggers (exderia) => (unassigned)
--
You received this bug notification because you are a member of
Ponnuvel, don't the fio tests show significantly better write IOPS and
latency in the optimized case?
== rocksdb%20optimized.txt
...
write: IOPS=1269, BW=5076KiB/s (5198kB/s)(2048MiB/413114msec); 0 zone
...
| 99.00th=[ 180], 99.50th=[ 384], 99.90th=[ 1003], 99.95th=[ 1636],
Good to know it's just rocksdb!
Has Canonical also considered compiling the source code with -DNDEBUG to
align with what appears to be the upstream default set of RelWithDebInfo
flags? The Ceph source code is quasi-judicious about its use of
`ceph_assert`, which is effectively compiled out when
Oof - so I hacked up debian/rules a little so that "RelWithDebInfo" is
used instead of "None" for CMAKE_BUILD_TYPE. I then ^C'd the dpkg-
buildpackage after it started compiling the first few source files and
observed that:
* When doing make V=1 VERBOSE=1 in obj-x86_64-linux-gnu/src/rocksdb
Checked out ceph-15.2.3 source on a up-to-date focal VM.
When running dpkg-buildpackage, CMakeCache.txt gets generated as
expected. However, the generated CMAKE_BUILD_TYPE is "None".
A bit odd, but going a step further, one can grep for CMAKE_C_FLAGS in that
same file and see something to the
Original crashing of mythtv now fixed on ubuntu 20.04 libmysqlclient21
version 8.0.21-0ubuntu0.20.04.3 with mariadb server.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1877504
Title:
Public bug reported:
windows has been booting just fine. Even after the installer fails here.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode
its effecting ubuntu 20.04 if there is a way to fix it please help me
out.
** Project changed: linux => ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1594023
Title:
Poweroff or reboot
** Also affects: linux
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1594023
Title:
Poweroff or reboot hangs. Laptop won't shutdown. 16.04
To manage
Another person affected by this bug chiming in.
My set-up is a Lenovo T440s with UEFI-only booting. Latest BIOS/firmware.
Secure boot is disabled. Grub menu appears fine on Debian itself, but with
Ubuntu I've had this issue since around 19.04, IIRC.
@siepo2
Removing that font is the first time
Never mind, my problem is solved, although there seems to be some
tidying up to be done.
Thanks again,
Kim
On 15/5/20 9:47 pm, Maciej Borzecki wrote:
> Double checked with snap-store from beta channel. The button is there,
> but it seems off.
>
> When I connected the interface, the UI button
Of course there is a button after you do the manual connection, but I
take your point.
Thanks again.
On 15/5/20 8:45 pm, Maciej Borzecki wrote:
> FWIW there should be a button which you can click in the snap-store.
> Sadly there does not seem to be one for the `dvb` interface.
>
> ** Also
Hi,
Yes, it works. Thanks.
I obviously need to do a course on the ins and outs of snap. There
appears to be a lot of stuff to be configured than I'm used to.
Cheers for that,
Kim
On 15/5/20 3:18 am, Maciej Borzecki wrote:
> ```
> [7f9a84000bb0] dtv stream error: cannot access DVR:
I can confirm that the test program above causes segfault with current
libmysqlclient21 but not with previous version, using mariadb as the
server.(sorry, it took me a while to get all the dependencies together
to compile and execute the program.)
--
You received this bug notification because
After the release of Focal, I did a fresh install with mariadb server.
I did a mysqldump backup of the existing mythtv (bionic) mariadb
database and installed mythtv (mythbackend + mythfrontend + plugins) and
configured it to work with the current setup.
This all worked almost perfectly, just
nux (Ubuntu)
Assignee: Tyler Hicks (tyhicks) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855341
Title:
CONFIG_USELIB should be disabled
To manage notifications about this
nux (Ubuntu)
Assignee: Tyler Hicks (tyhicks) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855335
Title:
CONFIG_DEBUG_CREDENTIALS should be enabled
To manage notifications
nux (Ubuntu)
Assignee: Tyler Hicks (tyhicks) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855339
Title:
CONFIG_LEGACY_PTYS should be disabled
To manage notifications about th
** Changed in: linux (Ubuntu)
Status: In Progress => Triaged
** Changed in: linux (Ubuntu)
Assignee: Tyler Hicks (tyhicks) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
nux (Ubuntu)
Assignee: Tyler Hicks (tyhicks) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855338
Title:
CONFIG_IO_STRICT_DEVMEM should be enabled
To manage notifications
nux (Ubuntu)
Assignee: Tyler Hicks (tyhicks) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855336
Title:
CONFIG_DEBUG_SG should be enabled
To manage notifications about this
nux (Ubuntu)
Assignee: Tyler Hicks (tyhicks) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855337
Title:
CONFIG_DEBUG_NOTIFIERS should be enabled
To manage notifications
** Changed in: linux (Ubuntu)
Status: In Progress => Triaged
** Changed in: linux (Ubuntu)
Assignee: Tyler Hicks (tyhicks) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
nux (Ubuntu)
Assignee: Tyler Hicks (tyhicks) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855334
Title:
CONFIG_DEBUG_LIST should be enabled
To manage notifications about this
** Changed in: linux (Ubuntu)
Assignee: Tyler Hicks (tyhicks) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811162
Title:
Turn on CONFIG_REFCOUNT_FULL for non-x86 arc
Scaling issue is effecting me as well:
Ubuntu 20.04 LTS
GeForce RTX 2080 Ti
Dell S2817Q
Samsung U28E590
nvidia-driver-440
Also installed alongside Windows 10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
A snap installation of vlc will not allow vlc to play TV. A repo installation
of vlc works as expected.
When run from command line, get the following messages:-
--snap version--
user@host:~$ /snap/bin/vlc Desktop/vlc_playlist.xspf
VLC media
On 2020-03-02 07:53:18, AceLan Kao wrote:
> Here is the test kernel and the patches I reverted/applied, could
> anyone helps me verify it.
I can confirm that the new kernel does _not_ regress brightness controls
on the machine that caused me to initially open this bug report.
Thanks!
--
You
I enabled the KMS debug messages in the drm module:
$ cat /etc/modprobe.d/drm-debug.conf
options drm debug=0x04
$ sudo update-initramfs -u -k $(uname -r) && sudo reboot
...
Unfortunately, it doesn't look like my device_id is set after the
drm_dp_read_desc() in drm_dp_read_desc:
$ dmesg | grep
Note that the quirks in the debug output from comment #9 are 0x
because I've got still got commit 3269788061d2 ("USUNTU: SAUCE:
drm/i915: Force DPCD backlight mode on Dell Precision 4K sku") reverted
locally.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Tags added: champagne
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861521
Title:
[FOCAL][REGRESSION] Intel Gen 9 brightness cannot be controlled
To manage notifications about this bug go to:
To provide further verification, I built Ubuntu-5.4-5.4.0-14.17 with a
single patch on top that reverts commit 3269788061d2 ("USUNTU: SAUCE:
drm/i915: Force DPCD backlight mode on Dell Precision 4K sku"). My
screen brightness controls are working again and I can undock from my
external monitor
I noticed that upstream v5.4.18 allowed me to adjust my screen
brightness while Ubuntu-5.4-5.4.0-14.17 does not, which indicates an
Ubuntu SAUCE patch as the culprit. I bisected between the two kernels
and this was the result:
$ git bisect good
3269788061d24e316633165608259de1c110b801 is the
Hi Brendan - What you're asking for is very different than the intent
behind this bug report. It'll be best if you open a new bug report.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863234
Title:
Eoan: https://lists.ubuntu.com/archives/kernel-team/2020-February/107613.html
Disco: https://lists.ubuntu.com/archives/kernel-team/2020-February/107616.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
[Impact]
The bpf(2) system call is completely blocked in Disco and Eoan when
Secure Boot is enabled due to overly restrictive Lockdown policies. This
makes it so that all bpf related tools are not usable on those releases.
[Test Case]
Set up test BPF
** Description changed:
+ [Impact]
+
+ The bpf(2) system call is completely blocked in Disco and Eoan when
+ Secure Boot is enabled due to overly restrictive Lockdown policies. This
+ makes it so that all bpf related tools are not usable on those releases.
+
+ [Test Case]
+
+ Set up test BPF
** Changed in: linux (Ubuntu Disco)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu Eoan)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu Disco)
Assignee: (unassigned) => Tyler Hicks (tyhicks)
** Changed in: linux (Ubuntu Eoan)
Hi Quentin - Thanks for the bug report! I do think that relaxing the
eBPF restrictions in Eoan and Disco would be acceptable for Secure Boot
purposes.
** Also affects: linux (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
I've also verified the fix in 5.3.0-41.33-generic.
** Tags removed: verification-needed-eoan
** Tags added: verification-done-eoan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861238
Title:
Root
I've verified the fix in 4.15.0-89.89-generic. The sysrq help message is
printed to the kernel log when trying to lift lockdown with the proof-
of-concept and when trying to lift lockdown with alt+sysrq+x.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
I've verified that the proof-of-concept does not show an information
leak when running 4.15.0-89.89-generic.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Submission to the Ubuntu kernel-team list:
https://lists.ubuntu.com/archives/kernel-team/2020-February/107444.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862840
Title:
[Bionic] i915
** Description changed:
[Impact]
Gregory Herrero reported that the proof-of-concept for CVE-2019-14615
indicates that the information leak is not fixed in the Bionic 4.15
kernel as indicated by USN-4255-1:
https://usn.ubuntu.com/4255-1/
This only affects Ubuntu's 4.15 kernel
I've pushed a set of proposed backports which prevents the information
leak when running the proof-of-concept code:
https://git.launchpad.net/~tyhicks/ubuntu/+source/linux/+git/bionic/log/?h=cves/CVE-2020-8832
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Another Gen 9 GPU that I have is not affected by this bug:
$ glxinfo | grep Device
Device: Mesa DRI Intel(R) HD Graphics 515 (Skylake GT2) (0x191e)
$ cat /proc/version_signature
Ubuntu 5.4.0-12.15-generic 5.4.8
I can increase and decrease the brightness without any issues.
--
You
nute or so to ensure that
# the information leak is not possible.
[Regression Potential]
TODO
** Affects: linux (Ubuntu)
Importance: High
Assignee: Tyler Hicks (tyhicks)
Status: Invalid
** Affects: linux (Ubuntu Bionic)
Importance: High
Assignee: Tyler Hicks (tyhicks)
Proposed fixes have been sent to the kernel-team list.
Focal: https://lists.ubuntu.com/archives/kernel-team/2020-February/107324.html
Eoan: https://lists.ubuntu.com/archives/kernel-team/2020-February/107326.html
Disco: https://lists.ubuntu.com/archives/kernel-team/2020-February/107328.html
(Ubuntu Focal)
Importance: High
Assignee: Tyler Hicks (tyhicks)
Status: In Progress
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Eoan)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Eoan
a lockdown free environment by running 'mokutil --disable-
validation' and rebooting.
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Ty
** Description changed:
+ [Impact]
+
It's possible to turn off kernel lockdown by emulating a USB keyboard
via USB/IP and sending an Alt+SysRq+X key combination through it.
Ubuntu's kernels have USB/IP enabled (CONFIG_USBIP_VHCI_HCD=m and
CONFIG_USBIP_CORE=m) with signed usbip_core
The fix for this bug has been released for a little while now. See the
info here:
https://people.canonical.com/~ubuntu-
security/cve/2019/CVE-2019-14615.html
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
I rebooted into Eoan's 5.3.0-29.31 kernel, with Focal's userspace, and
verified that the screen brightness is still adjustable under that
kernel. Additionally, it is worth noting that I saw the same "hp_wmi:
Unknown event_id" warnings mentioned in comment 2 so they probably don't
have anything to
Public bug reported:
After upgrading from Eoan (5.3.0-29.31) to Focal (5.4.0-12.15), I no
longer have the ability to control the backlight brightness on my HP
EliteBook 840 G5. When pressing the brightness hotkeys, the on-screen
indicator pops up and shows that the brightness setting is being
When the privacy screen functionality is enabled, I see the following
warnings in the logs:
[188829.782403] hp_wmi: Unknown event_id - 20 - 0x46fe
[188834.848948] hp_wmi: Unknown event_id - 20 - 0x3c00
[188835.624987] hp_wmi: Unknown event_id - 20 - 0x4600
The first warning is when I press the
** Information type changed from Private Security to Public Security
** Summary changed:
- Placeholder bug
+ arm64/KVM debug registers vulnerability
** Description changed:
- Placeholder bug report for arm64 KVM issue.
+ [Impact]
+
+ https://www.openwall.com/lists/oss-security/2020/01/30/5
+
FWIW, fatrace works fine for me under the same kernel and fatrace
version:
$ sudo fatrace
...
bash(51938): O /tmp/hi
bash(51938): CW /tmp/hi
...
tyhicks@elm:~$ cat /proc/version_signature
Ubuntu 5.4.0-12.15-generic 5.4.8
$ apt policy fatrace
fatrace:
Installed: 0.13-2
Candidate: 0.13-2
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861238
Title:
Root can lift kernel lockdown via USB/IP
To manage notifications about this
Upstream submission:
https://lore.kernel.org/lkml/20200123091713.12623-1-stefan.ba...@canonical.com/T/#t
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860231
Title:
5.4.0-11 crash on cryptsetup
Fix submitted by smb:
https://lists.ubuntu.com/archives/kernel-team/2020-January/107055.html
** Changed in: linux (Ubuntu)
Assignee: Andrea Righi (arighi) => Stéphane Graber (stgraber)
** Changed in: linux (Ubuntu)
Assignee: Stéphane Graber (stgraber) => Stefan Bader (smb)
--
You
** Description changed:
- An attempt to run cryptsetup open on a newly created LUKS partition on
- Ubuntu Core 20 causes a kernel crash. This happens in 100% of the
- attempts on the snapd Core 20 installation test, but on an image created
- to reproduce this bug it happens only when certain
** Description changed:
An attempt to run cryptsetup open on a newly created LUKS partition on
Ubuntu Core 20 causes a kernel crash. This happens in 100% of the
attempts on the snapd Core 20 installation test, but on an image created
to reproduce this bug it happens only when certain
On 2020-01-19 16:15:58, aaronleung wrote:
> My OS have this bug, i try to install kernel 5.4 in my linuxmint19.3,
> bug, instailing not found samething with from /lib/firmware/i915/ ,again.
> i try to download from
>
** Description changed:
-
+ Legacy BSD PTYs have been replaced by UNIX 98 PTYs a long time ago.
+ Disable legacy BSD PTY support as it is no longer needed.
+
+ This config option is recommended by the Kernel Self Protection
+ Project[1] and a 2019 study performed by Capsule 8 shows that it is
+
** Description changed:
-
+ We should disable CONFIG_USELIB to make the uselib(2) system call
+ unreachable in an effort to reduce the kernel attack surface.
+
+ The system call is only used by very old libc implementations and is
+ unlikely to be used today.
+
+ This config option is
** Description changed:
-
+ We should enable CONFIG_IO_STRICT_DEVMEM to restrict userspace access of
+ active io-memory ranges.
+
+ This could impact kernel debugability. In that case, you may reboot with
+ iomem=relaxed on the kernel commandline to override this setting.
+
+
+ This config
** Description changed:
-
+ We should enable CONFIG_DEBUG_NOTIFIERS to ensure that notifier functions are
present in the core kernel text or module text sections before calling
+ those functions.
+
+ If an invalid function pointer is detected, a warning is issued and the
+ function is not
** Description changed:
-
+ Enable CONFIG_DEBUG_SG to perform sanity checks when performing
+ operations on scatterlists. If a sanity check fails a loud warning is
+ printed to the logs.
+
+ This change may help in detection of an attack that relies on
+ scatterlist manipulation.
**
** Description changed:
-
+ We should enable CONFIG_DEBUG_CREDENTIALS to perform sanity checks, such as
verifying usage counts and proper magic values, when handling cred
+ structs. If a cred sanity check fails a loud warning is printed to the
+ logs.
+
+ The config option raises the bar on
** Description changed:
-
+ We should turn on CONFIG_DEBUG_LIST which does some sanity checking on the
+ surrounding linked list elements when adding or removing an element. If the
sanity check fails, the list manipulation operation is not and a loud warning
is printed to the logs in the form
nce: Undecided => High
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Tyler Hicks (tyhicks)
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-14615
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notifica
This is CVE-2020-7053
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-7053
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1859522
Title:
use-after-free in i915_ppgtt_close
To
** Information type changed from Private Security to Public Security
** Description changed:
[Impact]
Quan Luo and ycq from Codesafe Team of Legendsec at Qi'anxin Group
reported a use-after-free issue in the i915 driver. This issue has been
fixed in the upstream kernel starting in
Hi Neil - I think that's a good idea since we haven't seen any progress
on this private bug report. I'm not sure of the cause here but I think
that we would have received a lot more reports if this was a widespread
issue when using wg-quick (as we have in the past).
** Information type changed
** Description changed:
[Impact]
It was discovered that upstream kernel commit cab15ce604e5 ("arm64:
Introduce execute-only page access permissions"), which introduced
execute-only user mappings, subverted the Privileged Access Never
protections.
The fix is to effectively revert
In Progress
** Changed in: linux (Ubuntu Disco)
Assignee: (unassigned) => Tyler Hicks (tyhicks)
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Tyler Hicks (tyhicks)
** Changed in: linux (Ubuntu Eoan)
Assignee: (unassigned) => Tyler Hicks (tyhicks)
** Chan
*** This bug is a security vulnerability ***
Public security bug reported:
[Impact]
It was discovered that upstream kernel commit cab15ce604e5 ("arm64:
Introduce execute-only page access permissions"), which introduced
execute-only user mappings, subverted the Privileged Access Never
This has been happening for a bit on a work computer that went through
the built in update process to 19.10.
I seem to have gotten some relief by purging the nvidia drivers and
reinstalling. YMMV
1979 sudo apt purge nvidia-prime
1980 cat /var/log/prime-supported.log
1981 cat
This has been happening for a bit on a work computer that went through
the built in update process to 19.10.
I seem to have gotten some relief by purging the nvidia drivers and
reinstalling. YMMV
1979 sudo apt purge nvidia-prime
1980 cat /var/log/prime-supported.log
1981 cat
Public bug reported:
** Affects: linux (Ubuntu)
Importance: Medium
Assignee: Tyler Hicks (tyhicks)
Status: In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855341
Public bug reported:
** Affects: linux (Ubuntu)
Importance: Medium
Assignee: Tyler Hicks (tyhicks)
Status: In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855339
Public bug reported:
** Affects: linux (Ubuntu)
Importance: Medium
Assignee: Tyler Hicks (tyhicks)
Status: In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855342
1 - 100 of 3567 matches
Mail list logo
