NetworkManager crashed with SIGSEGV in nm_device_uses_assumed_connection()

Bug #1503578 reported by khanpakpum@gmail.com
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

์NA

ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: network-manager 1.0.4-0ubuntu4
Uname: Linux 4.3.0-040300rc4-lowlatency x86_64
NonfreeKernelModules: wl
ApportVersion: 2.19-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Wed Oct 7 10:02:05 2015
ExecutablePath: /usr/sbin/NetworkManager
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2015-09-28 (8 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
IpRoute:
 default via 192.168.1.1 dev wlxc412f52dbaf9 proto static metric 600
 default via 192.168.1.1 dev wlp3s0 proto static metric 601
 169.254.0.0/16 dev wlxc412f52dbaf9 scope link metric 1000
 192.168.1.0/24 dev wlxc412f52dbaf9 proto kernel scope link src 192.168.1.5 metric 600
 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.4 metric 601
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
ProcCmdline: /usr/sbin/NetworkManager --no-daemon
SegvAnalysis:
 Segfault happened at: 0x44cc09 <nm_device_uses_assumed_connection+25>: cmpq $0x0,0x108(%rbx)
 PC (0x0044cc09) ok
 source "$0x0" ok
 destination "0x108(%rbx)" (0x00000108) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: network-manager
StacktraceTop:
 nm_device_uses_assumed_connection ()
 ?? ()
 ?? ()
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: NetworkManager crashed with SIGSEGV in nm_device_uses_assumed_connection()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

nmcli-dev:
 DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH
 wlp3s0 wifi connected /org/freedesktop/NetworkManager/Devices/0 PK 1 ef2cbce8-ea7f-4133-819b-761e6257c919 /org/freedesktop/NetworkManager/ActiveConnection/0
 wlxc412f52dbaf9 wifi connected /org/freedesktop/NetworkManager/Devices/3 PK 89f141a2-e7ee-4b60-82dd-ac23152176c3 /org/freedesktop/NetworkManager/ActiveConnection/1
 enp4s0f1 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- -- --
 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/2 -- -- --
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'.

Revision history for this message
khanpakpum@gmail.com (khanpakpum) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 nm_device_uses_assumed_connection (self=self@entry=0x285e800) at devices/nm-device.c:946
 _set_state_full (self=self@entry=0x285e800, state=NM_DEVICE_STATE_FAILED, reason=reason@entry=NM_DEVICE_STATE_REASON_IP_CONFIG_UNAVAILABLE, quitting=quitting@entry=0) at devices/nm-device.c:8436
 nm_device_state_changed (self=self@entry=0x285e800, state=<optimized out>, reason=reason@entry=NM_DEVICE_STATE_REASON_IP_CONFIG_UNAVAILABLE) at devices/nm-device.c:8514
 nm_device_check_ip_failed (self=self@entry=0x285e800, may_fail=may_fail@entry=0) at devices/nm-device.c:5171
 nm_device_activate_ip4_config_timeout (user_data=<optimized out>) at devices/nm-device.c:5344

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in network-manager (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Seth Arnold (seth-arnold) wrote : Bug is not a security issue

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

information type: Private Security → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in network-manager (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.