CVE-2026-72012
Received Received - Intake

Linux Kernel RCU Use-After-Free in Tracing Subsystem

Vulnerability report for CVE-2026-72012, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-08-15

Last updated on: 2026-08-23

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: tracing/osnoise: Call synchronize_rcu() when unregistering This ensures that any RCU readers traversing the instance list have finished, before releasing the reference on the tracer that the instance points to.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-15
Last Modified
2026-08-23
Generated
2026-09-04
AI Q&A
2026-08-15
EPSS Evaluated
2026-09-03
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in the Linux kernel involves a missing synchronize_rcu() call when unregistering a tracer in the osnoise subsystem. This could allow RCU readers to still access a tracer instance after it has been freed, potentially leading to use-after-free issues or other memory corruption problems.

Detection Guidance

This vulnerability is specific to the Linux kernel's tracing subsystem and does not have a direct network detection method. To check if your system is affected, verify the kernel version and look for the presence of the vulnerable code path related to osnoise tracer unregistration. Commands like 'uname -a' can show the kernel version, and 'lsmod | grep osnoise' may indicate if the module is loaded.

Impact Analysis

If exploited, this flaw could cause system instability, crashes, or privilege escalation. Attackers might trigger memory corruption by manipulating tracer unregistration, leading to denial-of-service or arbitrary code execution on affected systems.

Compliance Impact

This vulnerability does not directly affect compliance with GDPR, HIPAA, or similar standards as it pertains to a Linux kernel tracing mechanism. No evidence suggests data exposure or privacy risks that would impact regulatory compliance.

Mitigation Strategies

Apply the latest kernel updates from your Linux distribution to ensure the vulnerability is patched. If immediate patching is not possible, consider disabling the osnoise tracer by removing it from loaded kernel modules or restricting access to tracing functionality until the update is applied.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-72012. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart