We have several production systems that have upgraded to this via unattended-upgrades. Only on one did we notice the conflict when we installed some backup things that pulled in libc6-dev (via build-essential for a python lib dependency).
You'll have to make up your own mind, but looking at the changelog https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1914044/comments/14 downgrading doesn't seem like much of a problem. If you don't need to install libc6-dev you can just wait for 2.31-0ubuntu9.4 I guess (but then it would be unlikely you're reading this ... so ... :)
For anyone else finding this and wondering what the implications are; from what I could find:
It seems that 2.31-0ubuntu9.3 was released for https:/ /bugs.launchpad .net/ubuntu/ +source/ glibc/+ bug/1914044 but as noted in https:/ /bugs.launchpad .net/ubuntu/ +source/ glibc/+ bug/1914044/ comments/ 18 "This fix proved to be too intrusive to be released via focal-updates." hence it was pulled.
We have several production systems that have upgraded to this via unattended- upgrades. Only on one did we notice the conflict when we installed some backup things that pulled in libc6-dev (via build-essential for a python lib dependency).
You'll have to make up your own mind, but looking at the changelog https:/ /bugs.launchpad .net/ubuntu/ +source/ glibc/+ bug/1914044/ comments/ 14 downgrading doesn't seem like much of a problem. If you don't need to install libc6-dev you can just wait for 2.31-0ubuntu9.4 I guess (but then it would be unlikely you're reading this ... so ... :)