[Bug 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

** No longer affects: systemd (Ubuntu Yakkety) -- 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

[Bug 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

This bug was fixed in the package systemd - 229-4ubuntu19 --- systemd (229-4ubuntu19) xenial; urgency=medium * debian/extra/units/systemd-resolved.service.d/resolvconf.conf: partially revert, by removing ExecStart|StopPost lines, as these are not needed on xenial and

[Bug 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

No crashes visible at https://errors.ubuntu.com/problem/ea90aefe098653f44b46e56d72e2cc05ff980465 ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Ubuntu

[Bug 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

Hello Daniele, or anyone else affected, Accepted systemd into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu19 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Bug 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

LP: #1704677 is reported as a regression in this SRU. Marking verification failed pending resolution. ** Tags removed: verification-done-xenial ** Tags added: verification-failed-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

As per tracker, we have not had any reports of this crash in resolved in 16.04. Thus this fix is mostly advisory / precautionary one for xenial. Marking as verified. There are now even less chances for resolved to crash on systems that use resolved ** Tags removed: verification-needed

[Bug 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

Hello Daniele, or anyone else affected, Accepted systemd into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu18 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Bug 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

** Changed in: systemd (Ubuntu Yakkety) Status: Confirmed => In Progress -- 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

[Bug 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

** Changed in: systemd (Ubuntu Xenial) Milestone: None => ubuntu-16.04.3 -- 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

[Bug 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

This bug was fixed in the package systemd - 232-21ubuntu4 --- systemd (232-21ubuntu4) zesty; urgency=medium * Cherrypick upstream commit to enable system use kernel maximum limit for RLIMIT_NOFILE isntead of hard-coded (low) limit of 65536. (LP: #1686361) *

[Bug 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

** Tags added: verification-done-zesty -- 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

[Bug 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

After checking the tracker, there are no new crashes reported for the proposed version of the package (systemd amd64 232-21ubuntu4) marking as verification done for zesty. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are

[Bug 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

Its worth noting that apport creates an initial .crash file without much information in it, after the user chooses to send the crash to the Error Tracker then some information gathering is performed. This information gathering stage includes adding the version of the package. Looking at the

[Bug 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

There is now one crash report in proposed. I'm not sure if this is because resolved was running, and has not been restarted yet. Or there is still this genuine crash present in the proposed package. _systemctl try-restart systemd-resolved.service || true is called in the postinst, so the

[Bug 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

Hello Daniele, or anyone else affected, Accepted systemd into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/232-21ubuntu4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Bug 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

** Description changed: + [Impact] + + * Null-pointer dereference in resolved, results in resolved crash and + reports on launchpad and errors. + + [Test Case] + + * Unknown steps to reproduce + * Monitor the drop off in crashes on errors.ubuntu.com: +

[Bug 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

Thank you for uploading this stable release update! To ease the SRU review process and later package validation, could you please update the bug description to include the relevant SRU information [1]? Especially the Regression Potential field that's missing here. [1]

[Bug 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

@xnox you previously mentioned that you had some systemd SRUs to prepare. Feel free to include this fix in those SRUs to address the error tracker reports. It just doesn't quite make sense to do a standalone security update of the init daemon for a low priority security issue. This bug is an

[Bug 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

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

[Bug 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2017-9217 -- 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

[Bug 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

** Tags added: apport-request-retrace -- 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

[Bug 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

I've requested a CVE from MITRE for this issue. -- 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

[Bug 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

** Description changed: - This is one of background errors that happens without any active app being involved. + This is one of background errors that happens without any active app being involved. For the records, I had open: Firefox, Slack, Franz and the Terminal + + [Testcase] + Notice

[Bug 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

This bug was fixed in the package systemd - 233-6ubuntu3 --- systemd (233-6ubuntu3) artful; urgency=medium * resolved: fix null pointer dereference crash (LP: #1621396) -- Dimitri John Ledkov Mon, 22 May 2017 09:29:22 +0100 ** Changed in: systemd (Ubuntu)

[Bug 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

** Patch added: "zesty.patch" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1621396/+attachment/4881443/+files/zesty.patch ** Changed in: systemd (Ubuntu Zesty) Status: Fix Committed => Confirmed ** Changed in: systemd (Ubuntu Yakkety) Status: New => Confirmed **

[Bug 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

** Patch added: "xenial.patch" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1621396/+attachment/4881430/+files/xenial.patch -- 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:

[Bug 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

** Patch added: "yakkety.patch" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1621396/+attachment/4881441/+files/yakkety.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1621396

[Bug 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

** Changed in: systemd (Ubuntu Zesty) Status: New => Fix Committed -- 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

[Bug 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

** Changed in: systemd (Ubuntu) Status: Confirmed => Fix Committed -- 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

[Bug 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

** Tags added: patch -- 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:

[Bug 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

** Information type changed from Private Security to Public Security -- 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()