This bug is awaiting verification that the linux-
nvidia-6.5/6.5.0-1014.14 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-nvidia-6.5' to
** Changed in: linux-oem-6.1 (Ubuntu Lunar)
Status: New => Invalid
** Changed in: linux-oem-6.1 (Ubuntu Mantic)
Status: New => Invalid
** Changed in: linux-oem-6.1 (Ubuntu Jammy)
Status: New => Won't Fix
--
You received this bug notification because you are a member of
This bug is awaiting verification that the linux-
hwe-6.5/6.5.0-25.25~22.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-jammy-linux-
hwe-6.5' to
This bug is awaiting verification that the linux-azure/6.5.0-1016.16
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-mantic-linux-azure' to 'verification-done-
mantic-linux-azure'. If
This bug is awaiting verification that the linux-aws/6.5.0-1015.15
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-mantic-linux-aws' to 'verification-done-mantic-
linux-aws'. If the
I have confirmed that with the 6.5.0-25.25 kernel in mantic-proposed,
shared libraries for 32bit binaries are loaded with some randoness;
specifically, we are back to 7 bits of randomness with this kernel
update:
$ cat /proc/version_signature
Ubuntu 6.5.0-25.25-generic 6.5.13
$ for ((i = 0 ; i <
This bug is awaiting verification that the linux/6.5.0-25.25 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-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still
** Changed in: linux (Ubuntu Mantic)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/1983357
Title:
test_021_aslr_dapper_libs from
Lunar is EOL
** Changed in: linux (Ubuntu Lunar)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/1983357
Title:
test_021_aslr_dapper_libs
This bug was fixed in the package linux - 6.6.0-14.14
---
linux (6.6.0-14.14) noble; urgency=medium
* noble/linux: 6.6.0-14.14 -proposed tracker (LP: #2045243)
* Noble update: v6.6.3 upstream stable release (LP: #2045244)
- locking/ww_mutex/test: Fix potential workqueue
Hey, Steve, we have applied this on linux-unstable, and will let it sit
there for a bit before we try this on mantic and lunar. I took the
opportunity and raised all values to the max, including the non-compat
ones. That should recover some of the bits we lost due to this PMD
alignment.
**
Thanks for investigating this, Cascardo. I agree that option 3 is likely
the best path forward, either via changing our kernel config defaults or
adjusting the sysctl defaults via the procps package. For reference the
adjustable sysctl setting is vm.mmap_rnd_compat_bits.
--
You received this bug
aslr32 libs regressed because of upstream commit 1854bc6e2420
("mm/readahead: Align file mappings for non-DAX").
Some filesystems mmap will try to align the address by the size and when
glibc loaded maps the ELF file, a randomized address will be chosen but
then aligned to the PMD size (21 bits
13 matches
Mail list logo
