network-manager segfaults on multiple wifi scans

Bug #2056529 reported by Felix Kopf
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Confirmed
Low
Unassigned

Bug Description

When I quickly fire

nmcli d wifi rescan ssid test-hidden

multiple times, the network-manager crashes with segfault.

Here a coredump:

PID: 4760 (NetworkManager)
UID: 0 (root)
GID: 0 (root)
Signal: 11 (SEGV)
Timestamp: Wed 2024-03-06 11:39:52 CET (9min ago)
Command Line: /usr/sbin/NetworkManager --no-daemon
Executable: /sbin/NetworkManager
Control Group: /system.slice/NetworkManager.service
Unit: NetworkManager.service
Slice: system.slice
Boot ID: <boot-id>
Machine ID: <machine-id>
Hostname: <hostname>
Storage:
/var/lib/systemd/coredump/core.NetworkManager.0.7f830276610c4ea886c51f8b922e9e3d.47
60.1709721592000000000000.lz4
Message: Process 4760 (NetworkManager) of user 0 dumped core.
Stack trace of thread 4760:
#0 0x00007f1780fa2efb c_list_unlink_stale (libnm-device-plugin-wifi.so + 0x17efb)
#1 0x00007f1780fa349f _scan_request_ssids_remove (libnm-device-plugin-wifi.so + 0x1849f)
#2 0x00007f1780fa37e8 _scan_request_ssids_fetch (libnm-device-plugin-wifi.so + 0x187e8)
#3 0x00007f1780fa70aa _scan_request_ssids_build_hidden (libnm-device-plugin-wifi.so + 0x1c0aa)
#4 0x00007f1780fa945a _scan_kickoff (libnm-device-plugin-wifi.so + 0x1e45a)
#5 0x00007f1780fa7d0a _scan_kickoff_timeout_cb (libnm-device-plugin-wifi.so + 0x1cd0a)
#6 0x00007f1787bd4be8 n/a (libglib-2.0.so.0 + 0x52be8)
#7 0x00007f1787bd404e g_main_context_dispatch (libglib-2.0.so.0 + 0x5204e)
#8 0x00007f1787bd4400 n/a (libglib-2.0.so.0 + 0x52400)
#9 0x00007f1787bd46f3 g_main_loop_run (libglib-2.0.so.0 + 0x526f3)
#10 0x0000564a05942577 n/a (/sbin/NetworkManager + 0x3c577)
#11 0x00007f1787989083 __libc_start_main (libc.so.6 + 0x24083)
#12 0x0000564a059410de n/a (/sbin/NetworkManager + 0x3b0de)

Ubuntu 22.04.3 LTS
network-manager 1.36.6-0ubuntu2

Changed in network-manager (Ubuntu):
importance: Undecided → Low
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.