cfg80211 crashes when trying to connect to encrypted access point

Bug #1738067 reported by Jakob Kramer
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

I am using Xubuntu 16.04 with the latest software.

# Steps to reproduce

1. Select specific access point in the dropdown menu of the default graphical network manager’s “indicator”.
2. Enter WiFi encryption password.

# What I expected

A connection to the access point is established.

# What happened instead

1. Wait a few seconds.
2. The window for password entry opened.
3. After entering the password again, go to 1.

I checked `dmesg`. This is what it reported to me:

[ 539.742755] ------------[ cut here ]------------
[ 539.742780] WARNING: CPU: 0 PID: 6 at /build/linux-yM3O3R/linux-4.4.0/net/wireless/sme.c:728 __cfg80211_connect_result+0x3b2/0x420 [cfg80211]()
[ 539.742781] Modules linked in: rfcomm bnep rtsx_usb_ms memstick dell_wmi sparse_keymap dell_laptop dcdbas dell_smm_hwmon snd_hda_codec_hdmi snd_hda_codec_conexant snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm btusb btrtl btbcm btintel bluetooth intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_seq_midi snd_seq_midi_event wl(POE) kvm_intel uvcvideo kvm snd_rawmidi videobuf2_vmalloc videobuf2_memops irqbypass videobuf2_v4l2 videobuf2_core v4l2_common input_leds videodev joydev serio_raw media snd_seq snd_seq_device snd_timer cfg80211 snd soundcore shpchp lpc_ich mei_me mei mac_hid dell_smo8800 parport_pc ppdev lp parport autofs4 drbg ansi_cprng algif_skcipher af_alg dm_crypt rtsx_usb_sdmmc rtsx_usb crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel
[ 539.742818] i915 aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd i2c_algo_bit drm_kms_helper syscopyarea psmouse sysfillrect sysimgblt fb_sys_fops drm ahci r8169 libahci mii wmi video fjes
[ 539.742831] CPU: 0 PID: 6 Comm: kworker/u16:0 Tainted: P W OE 4.4.0-103-generic #126-Ubuntu
[ 539.742832] Hardware name: Dell Inc. Vostro 3560/05GV6H, BIOS A07 05/17/2012
[ 539.742843] Workqueue: cfg80211 cfg80211_event_work [cfg80211]
[ 539.742844] 0000000000000286 b07824d3e76384b6 ffff880149c1fca0 ffffffff813fb523
[ 539.742847] 0000000000000000 ffffffffc03faf30 ffff880149c1fcd8 ffffffff810812e2
[ 539.742849] ffff8801472b7800 0000000000000000 0000000000000000 ffff8801470bb000
[ 539.742851] Call Trace:
[ 539.742856] [<ffffffff813fb523>] dump_stack+0x63/0x90
[ 539.742859] [<ffffffff810812e2>] warn_slowpath_common+0x82/0xc0
[ 539.742861] [<ffffffff8108142a>] warn_slowpath_null+0x1a/0x20
[ 539.742874] [<ffffffffc03d85f2>] __cfg80211_connect_result+0x3b2/0x420 [cfg80211]
[ 539.742885] [<ffffffffc03af46f>] cfg80211_process_wdev_events+0x13f/0x1b0 [cfg80211]
[ 539.742895] [<ffffffffc03af512>] cfg80211_process_rdev_events+0x32/0x70 [cfg80211]
[ 539.742904] [<ffffffffc03aa01e>] cfg80211_event_work+0x1e/0x30 [cfg80211]
[ 539.742908] [<ffffffff8109a635>] process_one_work+0x165/0x480
[ 539.742910] [<ffffffff8109a99b>] worker_thread+0x4b/0x4d0
[ 539.742912] [<ffffffff8109a950>] ? process_one_work+0x480/0x480
[ 539.742914] [<ffffffff810a0cd5>] kthread+0xe5/0x100
[ 539.742916] [<ffffffff810a0bf0>] ? kthread_create_on_node+0x1e0/0x1e0
[ 539.742921] [<ffffffff81844c0f>] ret_from_fork+0x3f/0x70
[ 539.742922] [<ffffffff810a0bf0>] ? kthread_create_on_node+0x1e0/0x1e0
[ 539.742924] ---[ end trace 447e5e9ec93ecc5d ]---

Revision history for this message
Jakob Kramer (jakobk) wrote :

Actually, I just entered the wrong password. But anyway the kernel panicked.

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1738067/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
affects: ubuntu → linux (Ubuntu)
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1738067

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: xenial
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.15 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc3

Changed in linux (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
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.