This bug was fixed in the package bash - 5.2.21-2ubuntu4
---
bash (5.2.21-2ubuntu4) noble; urgency=medium
* No-change rebuild for CVE-2024-3094
-- Steve Langasek Sun, 31 Mar 2024
08:41:03 +
** Changed in: bash (Ubuntu)
Status: New => Fix Released
** CVE added:
I added an sssd task due to the workaround we had to add to it in
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2058576 (we don't
install faketime). Should faketime be fixed, then we can revert that
change in sssd.
** Also affects: sssd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: faketime (Ubuntu)
Milestone: None => ubuntu-24.04-beta
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
https://bugs.launchpad.net/bugs/2059078
Title:
proposed-migration for faketime
What now remains to be done is to heavily patch faketime to, when on
armhf:
1/ use the proper symbols from glibc (e.g. __clock_gettime64 instead of
__clock_gettime)
2/ expose those symbols instead of the legacy 32-bit ones.
--
You received this bug notification because you are a member of
Oh, hang on. The bash build has apparently been uploaded just a day
after the t64 gcc, which means gcc was presumably still building when
the bash build started:
gcc-13 armhf 13.2.0-13ubuntu1 (from the bash build logs)
A bash rebuild should "fix" this somewhat. Well, at least a little bit.
**
5 matches
Mail list logo