systemd-resolved crashed with SIGSEGV in internal_hashmap_iterate()

[Lukas Raska]

possibly happened when user disconnected from VPN (openconnect)

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: systemd 234-2ubuntu1
ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
Uname: Linux 4.11.0-10-generic x86_64
ApportVersion: 2.20.6-0ubuntu4
Architecture: amd64
Date: Sun Jul 30 20:53:58 2017
ExecutablePath: /lib/systemd/systemd-resolved
InstallationDate: Installed on 2015-07-21 (740 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: LENOVO 20AQ007TMS
ProcCmdline: /lib/systemd/systemd-resolved
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-10-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7f86f1c932da: movzbl 0x2f(%rdi),%eax
 PC (0x7f86f1c932da) ok
 source "0x2f(%rdi)" (0x00000067) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: systemd
StacktraceTop:
 ?? () from /lib/systemd/libsystemd-shared-234.so
 internal_hashmap_iterate () from /lib/systemd/libsystemd-shared-234.so
 ?? ()
 ?? ()
 ?? ()
Title: systemd-resolved crashed with SIGSEGV in internal_hashmap_iterate()
UpgradeStatus: Upgraded to artful on 2017-07-04 (26 days ago)
UserGroups:

dmi.bios.date: 09/03/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: GJET79WW (2.29 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20AQ007TMS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50510 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrGJET79WW(2.29):bd09/03/2014:svnLENOVO:pn20AQ007TMS:pvrThinkPadT440s:rvnLENOVO:rn20AQ007TMS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 20AQ007TMS
dmi.product.version: ThinkPad T440s
dmi.sys.vendor: LENOVO

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1664886, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.