VulnerabilityPublished 25 Jul 2026

CVE-2026-64299: Linux kernel · tracing: Prevent out-of-bounds read in glob matching

Source GCVE Database

Authoritative record:CVE-2026-64299· High 7.1

Not known to be exploited · CVSS 7.1 High · fixed in ee5b8888d3248618251fb69a2fad92afcb81557e : patch Linux kernel soon.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score

7.1High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in ee5b8888d3248618251fb69a2fad92afcb81557e, ebb55902856973906c8bb339a3a34824ed4a5086, e5d5f3bd053a5f14787526c9f0f55ef900d43ac6 +5

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-fv73-wvqp-hjm7

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 60f1d5e3bac44b598f67d36062da96c095d2b700, < ee5b8888d3248618251fb69a2fad92afcb81557e	Fixed in ee5b8888d3248618251fb69a2fad92afcb81557e
LinuxLinux	Affected ≥ 60f1d5e3bac44b598f67d36062da96c095d2b700, < ebb55902856973906c8bb339a3a34824ed4a5086	Fixed in ebb55902856973906c8bb339a3a34824ed4a5086
LinuxLinux	Affected ≥ 60f1d5e3bac44b598f67d36062da96c095d2b700, < e5d5f3bd053a5f14787526c9f0f55ef900d43ac6	Fixed in e5d5f3bd053a5f14787526c9f0f55ef900d43ac6
LinuxLinux	Affected ≥ 60f1d5e3bac44b598f67d36062da96c095d2b700, < 265f3a690f6c7d69ef7d2ca50b04b4853a211df3	Fixed in 265f3a690f6c7d69ef7d2ca50b04b4853a211df3
LinuxLinux	Affected ≥ 60f1d5e3bac44b598f67d36062da96c095d2b700, < 56d4c9ab84714eebb285a2fee68aaedf81e3ef15	Fixed in 56d4c9ab84714eebb285a2fee68aaedf81e3ef15
LinuxLinux	Affected ≥ 60f1d5e3bac44b598f67d36062da96c095d2b700, < 35ae19764eabfe9c29029d3b5713c86e6855acdf	Fixed in 35ae19764eabfe9c29029d3b5713c86e6855acdf

AI-suggested

A fix has been implemented in the Linux kernel to address this issue by adding length-bounded glob matching. Users should apply the official kernel updates that include this patch. Since this is not a cloud service, remediation requires updating the affected Linux kernel versions once the patch is released. Patch status is not explicitly confirmed in the provided data; check the vendor advisory for current remediation guidance.

Description

In the Linux kernel, the following vulnerability has been resolved: tracing: Prevent out-of-bounds read in glob matching String event fields are not necessarily NUL-terminated, so the filter predicate functions (filter_pred_string(), filter_pred_strloc() and filter_pred_strrelloc()) pass the field length to the regex match callbacks, and the length-aware matchers honour it. regex_match_glob() was the exception: it ignored the length and called glob_match(), which scans the string until it hits a NUL byte. Some string fields are not NUL-terminated. One example is the dynamic char array of the xfs_* namespace tracepoints, which is copied without a trailing NUL. For such a field, glob matching reads past the end of the event field, causing a KASAN slab-out-of-bounds read in glob_match(), reached via regex_match_glob() and filter_match_preds() from the xfs_lookup tracepoint. Add a length-bounded glob_match_len() and use it from regex_match_glob() so glob matching always stops at the field boundary. The matching loop is factored into a shared helper so glob_match() keeps its behaviour.

Impact

The vulnerability causes out-of-bounds reads in kernel memory during tracing operations, which can lead to kernel memory corruption detection alerts (KASAN) and potentially destabilize the kernel. There is no indication of code execution or privilege escalation from the provided data. No known exploits in the wild have been reported.

Summary

The Linux kernel tracing subsystem had a vulnerability (CVE-2026-64299) where string event fields that are not NUL-terminated could cause out-of-bounds reads during glob pattern matching. While most filter predicate functions respected the string length, regex_match_glob() called glob_match(), which scanned until a NUL byte, ignoring the length. This led to a kernel address sanitizer (KASAN) slab-out-of-bounds read, notably triggered via the xfs_lookup tracepoint's dynamic char array fields. The fix involved adding a length-bounded glob_match_len() function used by regex_match_glob() to ensure matching respects field boundaries, preventing out-of-bounds access.

References

Community reviews

Loading reviews…