CVE-2011-1769: Divide by Zero
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.
Other sources
SystemTap 1.4 and earlier, when unprivileged (aka stapusr) mode is enabled, allows local users to cause a denial of service (divide-by-zero error and OOPS) via a crafted ELF program with DWARF expressions that are not properly handled by a stap script that performs context variable access.
Affected Software
Remediation
Patch Available
Patch Available
Event History
Parent advisories
This vulnerability appears in the following advisories.
Frequently Asked Questions
What is the severity of CVE-2011-1769?
CVE-2011-1769 has been classified as a moderate severity vulnerability due to potential kernel panic risks.
How do I fix CVE-2011-1769?
To fix CVE-2011-1769, you should update to systemtap versions 0:1.3-4.el5_6.1 or 0:1.4-6.el6_1.1 depending on your system.
What are the potential effects of CVE-2011-1769?
Exploitation of CVE-2011-1769 can lead to a kernel divide-by-zero message and possible busywait which may impact system performance.
Which software versions are affected by CVE-2011-1769?
CVE-2011-1769 affects various systemtap versions including but not limited to 0.3, 0.4, and 1.1.
Is CVE-2011-1769 remotely exploitable?
CVE-2011-1769 is not considered remotely exploitable as it requires local access for exploitation.