← Back to CVE intelligence
CVE intelligence

CVE-2026-99238

Vulnerability intelligence

Published Nov 2, 2026Sources checked Nov 19, 2026
7.8HIGHCVSS out of 10
What this means

Review the available evidence

CVE-2026-99238 and is rated High severity with a CVSS score of 7.8. It is not in the current CISA KEV record we collected. That does not prove exploitation has not occurred.

What to do next

Remediation and response

Ubuntu Security Notices guidance

Vendor revision: Nov 19, 2026
Vendor remediation details

This update corrects flaws in the following subsystems: - Cryptographic API; - File systems infrastructure; - Key management; - Key Management; - io_uring subsystem; - PID namespace; - Tracing infrastructure; (CVE-2026-99218, CVE-2026-99219, CVE-2026-99220, CVE-2026-99221, CVE-2026-99222, CVE-2026-99223, CVE-2026-99224, CVE-2026-99225, CVE-2026-99226, CVE-2026-99227, CVE-2026-99232, CVE-2026-99233, CVE-2026-99234, CVE-2026-99235, CVE-2026-99236, CVE-2026-99237, CVE-2026-99238, CVE-2026-99244, CVE-2026-99245)

CISA KEVNot listedBased on the latest collected catalog
EPSS0.1%Estimated 30-day exploitation probability
Ransomware useNot markedCISA KEV ransomware field
Threat actors0Source-linked actor relationships
Overview

What is CVE-2026-99238?

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.

Source: NVD