Hi Loïc, You're welcome.
Yes, I understand that glibc is a critical piece and we need to do the upgrade carefully. With my customer, we tested with several ubuntu versions: ubuntu 14.04: glibc 2.19: OK ubuntu 16.04: glibc 2.23: OK ubuntu 18.04: glibc 2.27: KO ubuntu 18.10: glibc 2.28: OK Only the LTS 18.04 is affected. The patch I'm looking for has been backported [1] by Glibc upstream project (for good reason) and they are certainly more competent than me to complete the SRU process. Maybe other patches related to libio can be necessary [2] and there are some patches related to CVE. I only tested up to the last Debian glibc 2.27 version packaged [3]. [1] https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=3bb748257405e94e13de76573a4e9da1cfd961d0 [2] https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=0262507918cfad7223bf81b8f162b7adc7a2af01 [3] https://salsa.debian.org/glibc-team/glibc/commit/0c8d271ac59dc2e4ee6bd509d59049080bd87f76 Best regards, Romain -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851263 Title: Ubuntu 18.04.3 LTS bump Glibc 2.27 to the latest stable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1851263/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
