Ubuntu
upstart package

init crashed with SIGSEGV in GI_nss_lookup_function()

Bug #1279024 reported by 188236 on 2014-02-11

10

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	upstart (Ubuntu)	New	Medium	Unassigned

Bug Description

?

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: upstart 1.11-0ubuntu3
ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
Uname: Linux 3.13.0-8-generic i686
ApportVersion: 2.13.2-0ubuntu2
Architecture: i386
Date: Tue Feb 11 20:21:52 2014
ExecutablePath: /sbin/init
InstallationDate: Installed on 2014-02-09 (2 days ago)
InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204)
ProcCmdline: /sbin/init
ProcEnviron:
TERM=linux
PATH=(custom, no user)
Signal: 11
SourcePackage: upstart
StacktraceTop:
__GI___nss_lookup_function (ni=0xb780fb58, fct_name=fct_name@entry=0xb760c584 "getgrnam_r") at nsswitch.c:468
__GI___nss_lookup (ni=ni@entry=0xbfd924b8, fct_name=0xb760c584 "getgrnam_r", fct2_name=0x0, fctp=fctp@entry=0xbfd924bc) at nsswitch.c:229
__GI___nss_group_lookup2 (ni=ni@entry=0xbfd924b8, fct_name=fct_name@entry=0xb760c584 "getgrnam_r", fct2_name=fct2_name@entry=0x0, fctp=fctp@entry=0xbfd924bc) at XXX-lookup.c:75
__getgrnam_r (name=name@entry=0xb760bc93 "tty", resbuf=resbuf@entry=0xbfd92920, buffer=buffer@entry=0xbfd92500 "", buflen=1024, result=result@entry=0xbfd9291c) at ../nss/getXXbyYY_r.c:205
grantpt (fd=34) at ../sysdeps/unix/grantpt.c:152
Title: init crashed with SIGSEGV in __GI___nss_lookup_function()
UpgradeStatus: Upgraded to trusty on 2014-02-11 (0 days ago)
UpstartBugCategory: Session
UpstartRunningSessionCount: 2
UpstartRunningSystemVersion: init (upstart 1.11)
UserGroups:

Tags:

Revision history for this message

188236 (christian-bernstein) wrote on 2014-02-11:

#1

Dependencies.txt Edit (2.7 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (1.1 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (4.5 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (753 bytes, text/plain; charset="utf-8")
Registers.txt Edit (532 bytes, text/plain; charset="utf-8")
SegvAnalysis.txt Edit (207 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (2.2 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (2.3 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2014-02-11:

#2

StacktraceTop:
__GI___nss_lookup_function (ni=0xb780fb58, fct_name=fct_name@entry=0xb760c584 "getgrnam_r") at nsswitch.c:468
__GI___nss_lookup (ni=ni@entry=0xbfd924b8, fct_name=0xb760c584 "getgrnam_r", fct2_name=0x0, fctp=fctp@entry=0xbfd924bc) at nsswitch.c:229
__GI___nss_group_lookup2 (ni=ni@entry=0xbfd924b8, fct_name=fct_name@entry=0xb760c584 "getgrnam_r", fct2_name=fct2_name@entry=0x0, fctp=fctp@entry=0xbfd924bc) at XXX-lookup.c:75
__getgrnam_r (name=name@entry=0xb760bc93 "tty", resbuf=resbuf@entry=0xbfd92920, buffer=buffer@entry=0xbfd92500 "", buflen=1024, result=result@entry=0xbfd9291c) at ../nss/getXXbyYY_r.c:205
grantpt (fd=34) at ../sysdeps/unix/grantpt.c:152

Revision history for this message

Apport retracing service (apport) wrote on 2014-02-11: Stacktrace.txt

#3

Stacktrace.txt Edit (7.6 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2014-02-11: StacktraceSource.txt

#4

StacktraceSource.txt Edit (4.2 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2014-02-11: ThreadStacktrace.txt

#5

ThreadStacktrace.txt Edit (7.7 KiB, text/plain)

Changed in upstart (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-i386-retrace

Revision history for this message

188236 (christian-bernstein) wrote on 2014-02-12:

#6

Crashed at startup

188236 (christian-bernstein) on 2014-03-10

information type:

Private → Private Security

Revision history for this message

Seth Arnold (seth-arnold) wrote on 2014-03-11: Bug is not a security issue

#7

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

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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