easy to crash polkitd by passing bad pid to pkcheck
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
policykit (Ubuntu) |
Invalid
|
Medium
|
Unassigned | ||
Hardy |
Invalid
|
Medium
|
Unassigned | ||
Intrepid |
Invalid
|
Medium
|
Unassigned | ||
Jaunty |
Invalid
|
Medium
|
Unassigned | ||
Karmic |
Invalid
|
Medium
|
Unassigned | ||
Lucid |
Invalid
|
Medium
|
Unassigned | ||
policykit-1 (Ubuntu) |
Fix Released
|
Medium
|
Martin Pitt | ||
Hardy |
Invalid
|
Undecided
|
Unassigned | ||
Intrepid |
Invalid
|
Undecided
|
Unassigned | ||
Jaunty |
Invalid
|
Undecided
|
Unassigned | ||
Karmic |
Won't Fix
|
Medium
|
Unassigned | ||
Lucid |
Fix Released
|
Medium
|
Martin Pitt |
Bug Description
Binary package hint: policykit-1
The crash occured while investigating bug #540247.
ProblemType: Crash
Architecture: amd64
Date: Wed Mar 17 20:30:52 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
NonfreeKernelMo
Package: policykit-1 0.96-1
ProcCmdline: /usr/lib/
ProcVersionSign
SegvAnalysis:
Segfault happened at: 0x7fb76001f054: repz cmpsb %es:(%rdi)
PC (0x7fb76001f054) ok
source "%es:(%rdi)" (0x7fb76002d3ba) ok
destination "%ds:(%rsi)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: policykit-1
StacktraceTop:
?? () from /usr/lib/
egg_dbus_
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: polkitd crashed with SIGSEGV in egg_dbus_
Uname: Linux 2.6.32-16-generic x86_64
UserGroups:
Related branches
summary: |
- polkitd crashed with SIGSEGV in - egg_dbus_method_invocation_return_gerror() + easy to crash polkitd by passing bad pid to pkcheck |
visibility: | public → private |
Changed in policykit-1 (Ubuntu): | |
status: | New → Triaged |
Changed in policykit1: | |
status: | Unknown → Confirmed |
visibility: | private → public |
Changed in policykit-1 (Ubuntu Lucid): | |
milestone: | none → ubuntu-10.04-beta-2 |
importance: | Medium → High |
importance: | High → Medium |
Changed in policykit-1 (Ubuntu Jaunty): | |
status: | New → Invalid |
Changed in policykit-1 (Ubuntu Intrepid): | |
status: | New → Invalid |
Changed in policykit-1 (Ubuntu Hardy): | |
status: | New → Invalid |
Changed in policykit (Ubuntu Lucid): | |
status: | New → Triaged |
Changed in policykit (Ubuntu Lucid): | |
importance: | Undecided → Medium |
Changed in policykit (Ubuntu Hardy): | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in policykit (Ubuntu Intrepid): | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in policykit (Ubuntu Jaunty): | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in policykit (Ubuntu Karmic): | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in policykit-1 (Ubuntu Karmic): | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in policykit-1 (Ubuntu Lucid): | |
assignee: | nobody → Martin Pitt (pitti) |
milestone: | ubuntu-10.04-beta-2 → ubuntu-10.04 |
status: | Triaged → In Progress |
Changed in policykit1: | |
importance: | Unknown → High |
Changed in policykit1: | |
importance: | High → Unknown |
status: | Confirmed → Fix Released |
Changed in policykit1: | |
importance: | Unknown → High |
I think the crash occurred when I passed the wrong process id to pkcheck: user-interactio n --process 666 --action-id org.freedesktop .systemtoolsbac kends.set" , where 666 is an invalid pid.
"pkcheck --allow-