Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
json-c (Ubuntu) |
Fix Released
|
Critical
|
Unassigned |
Bug Description
Installing the 0.11-4ubuntu2.1 security update on a Xenial system with upstart installed, the system crashes with a kernel panic.
The error message is:
[ 99.992278] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100
[ 99.992278]
[ 99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu
[ 99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006
[ 99.996057] 0000000000000086 0f10ff6977efbf32 ffff88003d45fe10 ffffffff8140926b
[ 99.996057] ffffffff81caddf8 ffff88003d45fea8 ffff88003d45fe98 ffffffff81195a84
[ 99.996057] ffff880000000010 ffff88003d45fea8 ffff88003d45fe40 0f10ff6977efbf32
[ 99.996057] Call Trace:
[ 99.996057] [<ffffffff81409
[ 99.996057] [<ffffffff81195
[ 99.996057] [<ffffffff81088
[ 99.996057] [<ffffffff81088
[ 99.996057] [<ffffffff81088
[ 99.996057] [<ffffffff81844
[ 99.996057] Kernel Offset: disabled
Downgrading to libjson-
Steps to reproduce:
* Create a system with Xenial installed (I'm using an AWS instance with AMI ami-0f2ed58082c
* Install upstart: apt-get install upstart-sysv
* Reboot
* Update apt and upgrade the packages: apt-get update && apt-get upgrade . This causes the kernel panic.
* To repeat the kernel panic, run dpkg --configure -a
CVE References
Changed in json-c (Ubuntu): | |
importance: | Undecided → Critical |
tags: | added: id-5ebe6d95d5ae066b83cac917 |
Changed in json-c (Ubuntu): | |
status: | Fix Released → Triaged |
Changed in json-c (Ubuntu): | |
status: | Triaged → Fix Released |
Status changed to 'Confirmed' because the bug affects multiple users.