usb_modeswitch crashed with SIGSEGV in libusb_exit()

Bug #1569600 reported by djameloter on 2016-04-12
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
usb-modeswitch (Ubuntu)
Medium
Unassigned

Bug Description

Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 006: ID 04f2:b3b1 Chicony Electronics Co., Ltd
Bus 001 Device 007: ID 0930:0220 Toshiba Corp.
Bus 001 Device 012: ID 12d1:1c0b Huawei Technologies Co., Ltd. E173s 3G broadband stick (modem off)
Bus 001 Device 003: ID 05e3:0745 Genesys Logic, Inc. Logilink CR0012
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: usb-modeswitch 2.2.5+repack0-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
Uname: Linux 4.4.0-18-generic x86_64
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Tue Apr 12 23:40:19 2016
ExecutablePath: /usr/sbin/usb_modeswitch
InstallationDate: Installed on 2016-02-12 (60 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
ProcCmdline: usb_modeswitch -c /etc/usb_modeswitch.d/12d1:1c0b
SegvAnalysis:
 Segfault happened at: 0x7effe96afdf6 <libusb_exit+134>: mov 0x210(%rbx),%rdx
 PC (0x7effe96afdf6) ok
 source "0x210(%rbx)" (0x00000210) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: usb-modeswitch
StacktraceTop:
 libusb_exit () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
 ?? ()
 abort ()
 ?? ()
 ?? ()
Title: usb_modeswitch crashed with SIGSEGV in libusb_exit()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

djameloter (djameloter) wrote :

StacktraceTop:
 libusb_exit () from /tmp/apport_sandbox_EmG7Do/lib/x86_64-linux-gnu/libusb-1.0.so.0
 close_all () at usb_modeswitch.c:2011
 abort () at usb_modeswitch.c:2019
 ReadParseParam (FileName=<optimized out>, FileName@entry=0x7fff6f49f80a "/etc/usb_modeswitch.d/12d1:1c0b", VariableName=VariableName@entry=0x40837d "TargetVendor") at usb_modeswitch.c:1881
 readConfigFile (configFilename=0x7fff6f49f80a "/etc/usb_modeswitch.d/12d1:1c0b") at usb_modeswitch.c:212

Changed in usb-modeswitch (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace

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
Launchpad Janitor (janitor) wrote :

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

Changed in usb-modeswitch (Ubuntu):
status: New → Confirmed
Mantas Kriaučiūnas (mantas) wrote :

I've backported usb-modeswitch 2.4 and usb-modeswich-data 2017-01 from Ubuntu 17.04 (Zesty) to 16.04 LTS (Xenial), you can update packages from ppa:baltix-members , see
https://launchpad.net/~baltix-members/+archive

Please reboot after installing usb-modeswitch 2.4 and usb-modeswich-data 2017-01 from ppa:baltix-members , test if your USB modem works correctly with updated packages and write a comment here in any case (works or not).

Thanks,
Mantas Kriaučiūnas
Developer of Baltix GNU/Linux Ubuntu derivative

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers