Systemtap is a system instrumentation and dynamic tracing framework widely deployed in Linux environments for performance monitoring and debugging, where its kernel-level probing functionality creates a privileged code-execution context. Vulnerabilities affecting the tool recur around input validation, race conditions, and code-injection pathways that reflect the risks of parsing untrusted trace specifications and managing concurrent access to kernel instrumentation state, and the vendor's disclosures tend to acquire public exploit code. Defenders tracking this tool should prioritize access controls on systemtap's administrative interfaces and audit its use in multi-tenant or exposed environments; live severity, exploitation, and coverage details are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Systemtap over time
Signals from CVEs in this vendor scope (12 CVEs).
12 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2010-4170HIGH The staprun runtime tool in SystemTap 1.3 does not properly clear the environment before executing modprobe, which allows local users to gain privileges by setting the MODPROBE_OPT | Dec 7, 2010 | 7.2 | 45 | NO | YES |
CVE-2009-4273HIGH stap-server in SystemTap before 1.1 allows remote attackers to execute arbitrary commands via shell metacharacters in stap command-line arguments in a request. | Jan 26, 2010 | 10.0 | 44 | NO | YES |
CVE-2010-0411MEDIUM Multiple integer signedness errors in the (1) __get_argv and (2) __get_compat_argv functions in tapset/aux_syscalls.stp in SystemTap 1.1 allow local users to cause a denial of serv | Feb 8, 2010 | 4.9 | 27 | NO | YES |
CVE-2010-0412HIGH stap-server in SystemTap 1.1 does not properly restrict the value of the -B (aka BUILD) option, which allows attackers to have an unspecified impact via vectors associated with exe | Feb 25, 2010 | 7.5 | 22 | NO | NO |
CVE-2012-0875MEDIUM SystemTap 1.7, 1.6.7, and probably other versions, when unprivileged mode is enabled, allows local users to obtain sensitive information from kernel memory or cause a denial of ser | Feb 4, 2014 | 5.4 | 20 | NO | NO |
CVE-2009-0784MEDIUM Race condition in the SystemTap stap tool 0.0.20080705 and 0.0.20090314 allows local users in the stapusr group to insert arbitrary SystemTap kernel modules and gain privileges via | Mar 25, 2009 | 6.3 | 19 | NO | NO |
CVE-2011-2502MEDIUM runtime/staprun/staprun_funcs.c in the systemtap runtime tool (staprun) in SystemTap before 1.6 does not properly validate modules when a module path is specified by a user for use | Jul 26, 2012 | 4.4 | 17 | NO | NO |
The insert_module function in runtime/staprun/staprun_funcs.c in the systemtap runtime tool (staprun) in SystemTap before 1.6 does not properly validate a module when loading it, w | Jul 26, 2012 | 3.7 | 16 | NO | NO |
SystemTap 1.4, 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 | Aug 29, 2011 | 1.2 | 13 | NO | NO |
The staprun runtime tool in SystemTap 1.3 does not verify that a module to unload was previously loaded by SystemTap, which allows local users to cause a denial of service (unloadi | Dec 7, 2010 | 2.1 | 13 | NO | NO |
Signals from CVEs in this vendor scope (12 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Systemtap.
Media articles that mention a CVE ID that affects a product developed by Systemtap — matched by CVE ID, not by vendor name.