fprintd crashed with SIGSEGV in log_v() from usbi_log() from libusb_unref_device()

Bug #1960387 reported by ssfrolov
22
This bug affects 2 people
Affects Status Importance Assigned to Milestone
libusb
Fix Released
Unknown
fprintd (Ubuntu)
Won't Fix
High
Unassigned
libusb (Ubuntu)
Fix Committed
High
Sebastien Bacher

Bug Description

+

ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: fprintd 1.94.1-1
ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
Uname: Linux 5.15.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu76
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Mon Feb 7 21:58:32 2022
ExecutablePath: /usr/libexec/fprintd
InstallationDate: Installed on 2021-12-21 (50 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
ProcCmdline: /usr/libexec/fprintd
ProcEnviron:
 LANG=ru_RU.UTF-8
 PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x7fd8a7a3855f: call *%rax
 PC (0x7fd8a7a3855f) ok
 source "*%rax" (0xd86d54af5d1db0f9) not located in a known VMA region (needed readable region)!
 destination "(%rsp)" (0x7ffdceacc590) ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: fprintd
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
 libusb_unref_device () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libgusb.so.2
 g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: fprintd crashed with SIGSEGV in libusb_unref_device()
UpgradeStatus: Upgraded to jammy on 2022-01-16 (23 days ago)
UserGroups: N/A
separator:

Revision history for this message
ssfrolov (ssf) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 log_v (ctx=0x562f76815000, level=LIBUSB_LOG_LEVEL_DEBUG, function=<optimized out>, format=0x7fd8a7a4893f "destroy device %d.%d", args=args@entry=0x7ffdceacca00) at ../../libusb/core.c:2653
 usbi_log (ctx=<optimized out>, level=level@entry=LIBUSB_LOG_LEVEL_DEBUG, function=function@entry=0x7fd8a7a4ada0 <__func__.24.lto_priv.0> "libusb_unref_device", format=format@entry=0x7fd8a7a4893f "destroy device %d.%d") at ../../libusb/core.c:2663
 libusb_unref_device (dev=0x562f7681e480) at ../../libusb/core.c:1190
 libusb_unref_device (dev=0x562f7681e480) at ../../libusb/core.c:1179
 g_usb_device_dispose (object=0x562f7682d560) at ../gusb/gusb-device.c:87

tags: removed: need-amd64-retrace
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 fprintd (Ubuntu):
importance: Undecided → Medium
summary: - fprintd crashed with SIGSEGV in libusb_unref_device()
+ fprintd crashed with SIGSEGV in log_v()
Revision history for this message
Launchpad Janitor (janitor) wrote : Re: fprintd crashed with SIGSEGV in log_v()

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

Changed in fprintd (Ubuntu):
status: New → Confirmed
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

This appears to match most of the crashes reported against fprintd:

https://errors.ubuntu.com/?release=Ubuntu%2022.04&package=fprintd&period=month

We just can't link them because of missing symbols.

information type: Private → Public
summary: - fprintd crashed with SIGSEGV in log_v()
+ fprintd crashed with SIGSEGV in log_v() from usbi_log() from
+ libusb_unref_device()
tags: added: rls-jj-incoming
Revision history for this message
Sebastien Bacher (seb128) wrote :

Trevinho pointed out we might want https://github.com/libusb/libusb/pull/1073 there

Changed in fprintd (Ubuntu):
importance: Medium → High
affects: libfprint → libusb
Changed in fprintd (Ubuntu):
status: Confirmed → Won't Fix
Changed in libusb (Ubuntu):
importance: Undecided → High
status: New → Confirmed
Changed in libusb:
status: Unknown → New
Changed in libusb (Ubuntu):
assignee: nobody → Sebastien Bacher (seb128)
tags: removed: rls-jj-incoming
Changed in libusb (Ubuntu):
status: Confirmed → Fix Committed
Changed in libusb:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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