Hide Forgot
Description of problem: When cabled internet is shared via WLAN, wpa_supplicant keeps segfaulting if some conditions are meet. Version-Release number of selected component (if applicable): wpa_supplicant.x86_64 How reproducible: Share you ethernet connection via wifi and let some Android devices authenticate with correct WPA-PSK password. Wpa_supplicant module can segfault during key exchange, and keeps segfaulting while the offending Android device tries to authenticate again. Steps to Reproduce: 1. Create and enable a shared wifi connection via network manager 2. Connect to the wifi connection to activate it 3. When some Android devices try to autenticate, wpa_supplicant module can segfault 4. The wireless interface disappears from NetworkManager. 5. Issue the command "sudo systemctl restart wpa_supplicant" on terminal 6. The interface reappears in NetworkManager and can be used again 7. If the affected Android device tries to authenticate again, wpa_supplicant can segfault another time. Go to step 5. 8. Disable then enable wifi on affected Android device 9. The device authenticates as expected and works, then wpa_supplicant segfaults on next key exchange. Actual results: [73262.834508] wpa_supplicant[975]: segfault at 0 ip 0000555e4dc1b010 sp 00007fff056539e0 error 4 in wpa_supplicant[555e4dbb7000+1b7000] [75767.531598] wpa_supplicant[8836]: segfault at 0 ip 000056158601a010 sp 00007fff9035c080 error 4 in wpa_supplicant[561585fb6000+1b7000] [84275.606511] wpa_supplicant[10814]: segfault at 0 ip 000055db124c2010 sp 00007ffc72609000 error 4 in wpa_supplicant[55db1245e000+1b7000] Expected results: Client is being authenticated without issue Additional info: Some Android clients do not trigger the bug. Others cause wpa_supplicant to segfault on sight. Hardware description: Lenovo M93 Desktop product: Centrino Wireless-N 2230 vendor: Intel Corporation bus info: pci@0000:02:00.0 logical name: wlp2s0 version: c4 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=4.8.6-201.fc24.x86_64 firmware=18.168.6.1 latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: irq:31 memory:f7c00000-f7c01fff Possible Android versions causing the bug: 4.2.2 Possible Android kernel causing the bug: 3.4.39 Possible Android wpa_supplicant version: unknown
update: Version of wpa_supplicant on Android device: v2.0-devel-4.2.2
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.