Lennart pointed out in the upstream pull request that systemd-resolved is respawned after crashing. Therefore, Ubuntu Security considers this security issue to be a low priority. To reduce the risk of regressions in security updates, our general rule is to only perform security updates that fix a medium or higher issue or wait until around five low issues have accumulated. The fix is simple and low risk but there's always inherent risk in building/publishing/installing new binaries. We'll include the fix in a future security update if there are new issues discovered in systemd.
** Changed in: systemd (Ubuntu Xenial) Importance: Undecided => Low ** Changed in: systemd (Ubuntu Yakkety) Importance: Undecided => Low ** Changed in: systemd (Ubuntu Zesty) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1621396 Title: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1621396/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
