In the Linux kernel, the following vulnerability has been resolved: tracing/osnoise: Call synchronize_rcu() when unregistering This ensures that any… (CVE-2026-72012)
A vulnerability in the Linux kernel's tracing/osnoise component was resolved by ensuring that synchronize_rcu() is called when unregistering. This change guarantees that any Read-Copy-Update (RCU) readers traversing the instance list complete before the reference to the tracer is released.
AI Analysis
Technical Summary
The Linux kernel contained a vulnerability in the tracing/osnoise subsystem where unregistering an instance did not call synchronize_rcu(). This omission could lead to use-after-free or similar race conditions because RCU readers might still be traversing the instance list while the tracer reference is released. The fix involves calling synchronize_rcu() during unregistering to ensure all RCU readers have finished before releasing the tracer reference, preventing potential memory safety issues.
Potential Impact
The vulnerability could cause memory safety issues such as use-after-free conditions in the kernel tracing subsystem, potentially leading to system instability or crashes. No known exploits in the wild have been reported. The impact is limited to kernel tracing functionality and does not indicate direct remote code execution or privilege escalation based on the provided data.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to call synchronize_rcu() when unregistering the tracer instance. Users should apply the official kernel updates that include this fix. Since no patch links or vendor advisories are provided, check the Linux kernel official repositories or vendor advisories for the specific patched versions and update accordingly.
In the Linux kernel, the following vulnerability has been resolved: tracing/osnoise: Call synchronize_rcu() when unregistering This ensures that any… (CVE-2026-72012)
Description
A vulnerability in the Linux kernel's tracing/osnoise component was resolved by ensuring that synchronize_rcu() is called when unregistering. This change guarantees that any Read-Copy-Update (RCU) readers traversing the instance list complete before the reference to the tracer is released.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel contained a vulnerability in the tracing/osnoise subsystem where unregistering an instance did not call synchronize_rcu(). This omission could lead to use-after-free or similar race conditions because RCU readers might still be traversing the instance list while the tracer reference is released. The fix involves calling synchronize_rcu() during unregistering to ensure all RCU readers have finished before releasing the tracer reference, preventing potential memory safety issues.
Potential Impact
The vulnerability could cause memory safety issues such as use-after-free conditions in the kernel tracing subsystem, potentially leading to system instability or crashes. No known exploits in the wild have been reported. The impact is limited to kernel tracing functionality and does not indicate direct remote code execution or privilege escalation based on the provided data.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to call synchronize_rcu() when unregistering the tracer instance. Users should apply the official kernel updates that include this fix. Since no patch links or vendor advisories are provided, check the Linux kernel official repositories or vendor advisories for the specific patched versions and update accordingly.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-jc7h-x8xh-33g2
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-72012"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a808b78bf8831d539502181
Added to database: 08/15/2026, 15:53:28 UTC
Last enriched: 08/15/2026, 17:09:12 UTC
Last updated: 08/15/2026, 18:21:08 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.