apache2 crashed with SIGSEGV in filter_harness()

Bug #1565816 reported by Flávio Oliveira on 2016-04-04
This bug affects 6 people
Affects Status Importance Assigned to Milestone
apache2 (Ubuntu)

Bug Description

After the installation of package and after the reboot system, the problem appeared after I logged in the system.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: apache2-bin 2.4.18-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
Uname: Linux 4.4.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
Date: Sun Apr 3 15:09:16 2016
ExecutablePath: /usr/sbin/apache2
InstallationDate: Installed on 2016-03-19 (16 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
ProcCmdline: /usr/sbin/apache2 -k start
 PATH=(custom, no user)
 Segfault happened at: 0x7ff5c1e54aca: jb 0x7ff5c1e54afb
 PC (0x7ff5c1e54aca) in non-executable VMA region: 0x7ff5c1e00000-0x7ff5c2000000 rw-p None
 source "0x7ff5c1e54afb" (0x7ff5c1e54afb) ok
SegvReason: executing writable VMA None
Signal: 11
SourcePackage: apache2
 ?? ()
 ?? () from /usr/lib/apache2/modules/mod_filter.so
 ?? () from /usr/lib/apache2/modules/libphp7.0.so
 ap_run_handler ()
 ap_invoke_handler ()
Title: apache2 crashed with SIGSEGV in ap_run_handler()
UpgradeStatus: No upgrade log present (probably fresh install)

information type: Private → Public Security

 ?? ()
 filter_harness (f=0x7ff5ca198300, bb=0x7ff5ca198a48) at mod_filter.c:323
 php_handler (r=<optimized out>) at /build/php7.0-XlnpcA/php7.0-7.0.4/sapi/apache2handler/sapi_apache2.c:695
 ap_run_handler (r=r@entry=0x7ff5ca18c0a0) at config.c:169
 ap_invoke_handler (r=r@entry=0x7ff5ca18c0a0) at config.c:433

Changed in apache2 (Ubuntu):
importance: Undecided → Medium
summary: - apache2 crashed with SIGSEGV in ap_run_handler()
+ apache2 crashed with SIGSEGV in filter_harness()
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: Public Security → Public
Launchpad Janitor (janitor) wrote :

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

Changed in apache2 (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers