Skip to content
statance
MenuClose
high · CVSS 7.8

CVE-2026-99238

tracing: Hold trace_types_lock when updating modules in persistent instances

Published 2 Nov 2026 · Source updated 3 Nov 2026 · Retrieved 2026-11-04 20:14 UTC

Monitor this CVE ↗Full CVE monitoring on Pro and Business

What happened?

In the Linux kernel, the following vulnerability has been resolved:

tracing: Hold trace_types_lock when updating modules in persistent instances

trace_module_record() walks ftrace_trace_arrays from the module notifier without trace_types_lock. A concurrent rmdir of an instance removes it from the list and frees it under that lock, so a module load or unload can walk into a freed trace_array.

Description supplied by CVE Program. Formatting is simplified; follow the original advisory for full details.

Affected software and versions

Source-provided software and version information
SoftwareVersion informationFixed version
LinuxLinuxaffected: 5f3719f697c3fdfae5cd6805f10ac7a04b0f4e43 to < 57408eac99b0d8a005796346d317d31f0ca4e07a; affected: 5f3719f697c3fdfae5cd6805f10ac7a04b0f4e43 to < dab2bd4d67ad5eaa95019a9511f8d379401b5021; affected: 5f3719f697c3fdfae5cd6805f10ac7a04b0f4e43 to < 244c442f54601a24c86ad90572bf36fc3df41c5e; affected: 5f3719f697c3fdfae5cd6805f10ac7a04b0f4e43 to < 66877a312ae3c2c3d849e82e882f642ffd4ec3e2See vendor advisory
LinuxLinuxaffected: 6.15; unaffected: 0 to < 6.15; unaffected: 6.18.60 to ≤ 6.18.*; unaffected: 7.2.14 to ≤ 7.2.*; unaffected: 7.3.1 to ≤ 7.3.*; unaffected: 7.4-rc1 to ≤ *See vendor advisory

Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.

Is it being exploited?

This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.

CISA data retrieved 2026-11-06 16:38 UTC. Check CISA ↗

How to respond

  1. Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
  2. Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
  3. Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.

Sources and remediation references

This public advisory does not determine whether a particular server is affected. Records are refreshed as sources change; verify urgent decisions against the original advisory.

← Browse the public CVE feed