REDHAT-BUG-702687: Divide by Zero

Published May 6, 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 (paniconoops), 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.

Affected Software

1 affected component

SystemTap SystemTap

Event History

May 6, 2011

Data Sourced

via Red Hat·03:19 PM

DescriptionSeverityAffected Software

Frequently Asked Questions

What is the severity of REDHAT-BUG-702687?

The severity of REDHAT-BUG-702687 has been classified as a significant issue due to its potential to cause a kernel panic.

How do I fix REDHAT-BUG-702687?

To fix REDHAT-BUG-702687, update your systemtap to the latest version that addresses this vulnerability.

What symptoms indicate a problem related to REDHAT-BUG-702687?

Symptoms of REDHAT-BUG-702687 may include kernel divide-by-zero messages or system hangs during stap module shutdown.

Who is affected by REDHAT-BUG-702687?

Administrators running systemtap on affected versions are at risk from REDHAT-BUG-702687.

Is there a workaround for REDHAT-BUG-702687?

Disabling systemtap on affected systems can serve as a temporary workaround for REDHAT-BUG-702687.