CVE-2026-31541 Details
Description
In the Linux kernel, the following vulnerability has been resolved: tracing: Fix trace_marker copy link list updates When the "copy_trace_marker" option is enabled for an instance, anything written into /sys/kernel/tracing/trace_marker is also copied into that instances buffer. When the option is set, that instance's trace_array descriptor is added to the marker_copies link list. This list is protected by RCU, as all iterations uses an RCU protected list traversal. When the instance is deleted, all the flags that were enabled are cleared. This also clears the copy_trace_marker flag and removes the trace_array descriptor from the list. The issue is after the flags are called, a direct call to update_marker_trace() is performed to clear the flag. This function returns true if the state of the flag changed and false otherwise. If it returns true here, synchronize_rcu() is called to make sure all readers see that its removed from the list. But since the flag was already cleared, the state does not change and the synchronization is never called, leaving a possible UAF bug. Move the clearing of all flags below the updating of the copy_trace_marker option which then makes sure the synchronization is performed. Also use the flag for checking the state in update_marker_trace() instead of looking at if the list is empty.
A use-after-free vulnerability has been identified in the Linux kernel's tracing subsystem, specifically related to the 'copy_trace_marker' feature. When this option is enabled for a tracing instance, data written to '/sys/kernel/tracing/trace_marker' is copied to that instance's buffer. The instance's trace_array descriptor is then added to a list of marker copies, which is protected by Read-Copy Update (RCU) mechanisms. However, when the instance is deleted, the 'copy_trace_marker' flag is cleared, and the trace_array descriptor is removed from the list. The vulnerability arises because the flag is cleared before a direct call to 'update_marker_trace()' is made, which is supposed to synchronize the removal from the list. This oversight leaves a potential use-after-free condition, as the necessary synchronization is not performed, allowing for possible exploitation.
The vulnerability has been addressed in the Linux kernel. Users should upgrade to the latest version where this issue has been fixed.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/07183aac4a6828e474f00b37c9d795d0d99e18a7 | kernel.org | Patch |
| https://git.kernel.org/stable/c/75668e58244e63ec3785098a02e1cdcff14a6c2e | kernel.org | Patch |
| https://git.kernel.org/stable/c/cc267e4b4302247dc67ef937a9ac587a696a43c1 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-416 | Use After Free | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 6.16, < 6.18.20 >= 6.19, < 6.19.10 7.0 rc1 7.0 rc2 7.0 rc3 7.0 rc4 |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Apr 28, 2026 | Initial Analysis | [email protected] |
| Apr 24, 2026 | New CVE Received | kernel.org |