tcpdump segfaults because of apparmor

Bug #585150 reported by Fabien Tassin
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tcpdump (Ubuntu)
Fix Released
Medium
Jamie Strandboge

Bug Description

Binary package hint: tcpdump

on maverick, tcpdump segfaults because of apparmor

[12181.133140] type=1503 audit(1274734610.178:15): operation="open" pid=5244 parent=4999 profile="/usr/sbin/tcpdump" requested_mask="r::" denied_mask="r::" fsuid=0 ouid=0 name="/sys/class/net/"
[12181.133180] tcpdump[5244]: segfault at 4 ip 00d8356e sp bf958134 error 6 in libc-2.11.1.so[cee000+157000]

Program received signal SIGSEGV, Segmentation fault.
0x001d856e in readdir64 () from /lib/libc.so.6
(gdb) bt
#0 0x001d856e in readdir64 () from /lib/libc.so.6
#1 0xb78568d0 in ?? ()

Tags: apparmor

Related branches

tags: added: apparmor
Revision history for this message
Jamie Strandboge (jdstrand) wrote :

Fabien, is this in Lucid or Maverick? How are you starting tcpdump?

Changed in tcpdump (Ubuntu):
status: New → Incomplete
assignee: nobody → Jamie Strandboge (jdstrand)
Revision history for this message
Fabien Tassin (fta) wrote :

as mentioned in the original report, it's in maverick.
nothing fancy, just "tcpdump" as root crashes.

Revision history for this message
Jamie Strandboge (jdstrand) wrote :

Sorry, missed that. Will get this fixed up in the next upload. Thanks for the report!

Changed in tcpdump (Ubuntu):
status: Incomplete → Triaged
Changed in tcpdump (Ubuntu):
status: Triaged → In Progress
importance: Undecided → Medium
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package tcpdump - 4.0.0-6ubuntu4

---------------
tcpdump (4.0.0-6ubuntu4) maverick; urgency=low

  * debian/usr.sbin.tcpdump:
    - allow device probing (LP: #585150)
    - allow 'w' access to /dev/bus/usb/**/[0-9]*, needed for proper USB
      probing with libpcap 1.1 and higher
 -- Jamie Strandboge <email address hidden> Thu, 10 Jun 2010 14:54:22 -0500

Changed in tcpdump (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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