Red Hat Bugzilla – Bug 866558
[abrt] SIGSEGV with NULL avc at "sepol_policydb_free(avc->policydb)" in audit2why.c:finish
Last modified: 2013-08-01 14:42:47 EDT
Version-Release number of selected component:
libreport version: 2.0.13
cmdline: /usr/bin/python -Es /usr/bin/audit2allow -w
:Thread no. 1 (10 frames)
: #0 finish at audit2why.c
: #1 call_function at /usr/src/debug/Python-2.7.3/Python/ceval.c
: #2 PyEval_EvalFrameEx at /usr/src/debug/Python-2.7.3/Python/ceval.c
: #3 fast_function at /usr/src/debug/Python-2.7.3/Python/ceval.c
: #4 call_function at /usr/src/debug/Python-2.7.3/Python/ceval.c
: #5 PyEval_EvalFrameEx at /usr/src/debug/Python-2.7.3/Python/ceval.c
: #6 fast_function at /usr/src/debug/Python-2.7.3/Python/ceval.c
: #7 call_function at /usr/src/debug/Python-2.7.3/Python/ceval.c
: #8 PyEval_EvalFrameEx at /usr/src/debug/Python-2.7.3/Python/ceval.c
: #9 fast_function at /usr/src/debug/Python-2.7.3/Python/ceval.c
Created attachment 627533 [details]
Created attachment 627534 [details]
Created attachment 627535 [details]
Created attachment 627536 [details]
Created attachment 627537 [details]
Created attachment 627538 [details]
Created attachment 627539 [details]
Created attachment 627540 [details]
Created attachment 627541 [details]
Created attachment 627542 [details]
Created attachment 627543 [details]
Thanks for filing this bug report.
What is the output of running:
rpm -q policycoreutils policycoreutils-python
Looking at attachment 627536 [details] I see that a segmentation fault happened in:
#0 0x00007f20085723dc in finish (self=<optimized out>, args=<optimized out>) at audit2why.c:174
0x00007f20085723d5 <+133>: mov 0x228b9c(%rip),%rax # 0x7f200879af78 <avc>
=> 0x00007f20085723dc <+140>: mov 0x8(%rax),%rdi
0x00007f20085723e0 <+144>: callq 0x7f2008571880 <sepol_policydb_free@plt>
and that rax was 0.
Hence this looks like a NULL pointer dereference, with avc == NULL at
Reassigning component to policycoreutils
Could you attach the avc messages used to create this crash
Actually I see the problem.
Fixed in libselinux-2.1.10-5.fc17
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '17'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 17's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 17 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged change the
'version' to a later Fedora version prior to Fedora 17's end of life.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.