dumpe2fs crashed with SIGSEGV in e2p_is_null_uuid()

Bug #1796379 reported by Peter Müller on 2018-10-05
This bug affects 1 person
Affects Status Importance Assigned to Milestone
e2fsprogs (Ubuntu)

Bug Description

when using gnome control center (no idea, if related)

ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: e2fsprogs 1.44.4-2
ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
Uname: Linux 4.18.0-8-generic x86_64
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
Date: Fri Oct 5 19:27:27 2018
ExecutablePath: /sbin/dumpe2fs
InstallationDate: Installed on 2018-10-05 (0 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20181004)
ProcCmdline: dumpe2fs -h /dev/sdc1
 Segfault happened at: 0x7fa1b9836ffc <e2p_is_null_uuid+12>: cmpb $0x0,-0x1(%rdi)
 PC (0x7fa1b9836ffc) ok
 source "$0x0" ok
 destination "-0x1(%rdi)" (0x7ffcdb8f3000) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: e2fsprogs
 e2p_is_null_uuid () from /lib/x86_64-linux-gnu/libe2p.so.2
 e2p_uuid2str () from /lib/x86_64-linux-gnu/libe2p.so.2
 e2p_list_journal_super () from /lib/x86_64-linux-gnu/libe2p.so.2
 ?? ()
 ?? ()
Title: dumpe2fs crashed with SIGSEGV in e2p_is_null_uuid()
UpgradeStatus: No upgrade log present (probably fresh install)

Peter Müller (ng0177) wrote :

 e2p_is_null_uuid (uu=uu@entry=0x7ffcdb8f3000) at ../../../../lib/e2p/uuid.c:32
 e2p_uuid2str (uu=uu@entry=0x7ffcdb8f3000) at ../../../../lib/e2p/uuid.c:80
 e2p_list_journal_super (f=0x7fa1b95de760 <_IO_2_1_stdout_>, journal_sb_buf=0x7ffcdb8f1db0 "\300;9\230", exp_block_size=4096, flags=<optimized out>) at ../../../../lib/e2p/ljs.c:105
 print_inline_journal_information (fs=0x555fb1e382d0) at ../../../misc/dumpe2fs.c:395
 main (argc=<optimized out>, argv=<optimized out>) at ../../../misc/dumpe2fs.c:733

Changed in e2fsprogs (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
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers