Skip to main content
← Vulnerabilities

tracing: Hold trace_types_lock when resetting last boot data from readers

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

7.8HighCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Specific setups only
Published
Last modified
Published
Not listed in CISA KEV
38/100 · provisional
Specific setups only
None on Exploit-DB, Metasploit or GitHub
On X
View the cve.now post

Summary

The Linux kernel's tracing subsystem (ftrace) is affected, where concurrent readers can race when resetting last-boot trace module data, potentially causing a double free and memory corruption. The impact could include kernel crashes or instability, and possibly other security consequences from memory corruption.

Read the original description

In the Linux kernel, the following vulnerability has been resolved: tracing: Hold trace_types_lock when resetting last boot data from readers update_last_data_if_empty() is called from tracing_open() with O_TRUNC, tracing_read_pipe() and tracing_buffers_read() without trace_types_lock. Two readers can both pass the LAST_BOOT test and free module_delta twice, and a module notifier can update module_delta while it is being freed. Take trace_types_lock in those paths and keep the callers that already hold it on an unlocked variant.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now

Affected versions

  • Linux Linux

    Version range not reported

  • Linux Linux

    6.16

Evidence 3

  1. Link
  2. Link
  3. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.