First published: Fri May 06 2011(Updated: )
A flaw was discovered in systemtap's handling of DWARF expressions where it did not guard against two cases of divide by zero. This can result in a kernel div-by-zero message and possible busywait during stap module shutdown. A div-by-zero could cause the kernel to panic and if the kernel reboot on panic flag was set (panic_on_oops), it would cause the system to reboot. In order to trigger this flaw, it would require a user with staprun or stapdev group membership (or root privileges) to run a particular stap script operation on a hand-corrupted elf program.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Systemtap Systemtap | =1.1 | |
Systemtap Systemtap | =1.2 | |
Systemtap Systemtap | =0.3 | |
Systemtap Systemtap | =0.9.5 | |
Systemtap Systemtap | =0.4 | |
Systemtap Systemtap | =0.6.2 | |
Systemtap Systemtap | =0.5.10 | |
Systemtap Systemtap | =0.8 | |
Systemtap Systemtap | =0.9 | |
Systemtap Systemtap | =0.5.14 | |
Systemtap Systemtap | =0.7.2 | |
Systemtap Systemtap | =0.9.8 | |
Systemtap Systemtap | =0.7 | |
Systemtap Systemtap | =0.5.12 | |
Systemtap Systemtap | =0.5.4 | |
Systemtap Systemtap | =0.6 | |
Systemtap Systemtap | =0.5.7 | |
Systemtap Systemtap | =0.9.7 | |
Systemtap Systemtap | =0.9.9 | |
Systemtap Systemtap | =0.5.8 | |
Systemtap Systemtap | =0.5.3 | |
Systemtap Systemtap | =0.2.2 | |
Systemtap Systemtap | =0.5.5 | |
Systemtap Systemtap | =0.5.13 | |
Systemtap Systemtap | =0.5.9 | |
Systemtap Systemtap | <=1.4 | |
Systemtap Systemtap | =1.0 | |
Systemtap Systemtap | =1.3 | |
Systemtap Systemtap | =0.5 | |
redhat/systemtap | <0:1.3-4.el5_6.1 | 0:1.3-4.el5_6.1 |
redhat/systemtap | <0:1.4-6.el6_1.1 | 0:1.4-6.el6_1.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.