VulnerabilityPublished 19 Jul 2026Updated 11 Aug 2026

CVE-2026-64184: Linux kernel · mm/damon/sysfs-schemes: call missing mem_cgroup_iter_break()

Source GCVE Database

Not known to be exploited · CVSS 5.5 Medium.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 3.1 base score

5.5Medium

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

EPSS: 0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
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: None: There is no loss of confidentiality within the impacted component.
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 19 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-r9g3-vg72-x365

What to do

AI-suggested

The vulnerability has been resolved in the Linux kernel source by adding the missing mem_cgroup_iter_break() call. Users and administrators should update their Linux kernel to a version that includes this fix. Patch status is not explicitly stated in the provided data; therefore, check the official Linux kernel advisories or vendor updates for the exact fixed versions and apply the official patch accordingly.

Description

A vulnerability in the Linux kernel's memory control group (memcg) subsystem was resolved by ensuring the proper call to mem_cgroup_iter_break() in the damon_sysfs_memcg_path_to_id() function. The issue involved leaking a cgroup reference due to missing this call when breaking an iteration loop. This flaw does not impact confidentiality or integrity but can cause an availability impact. The vulnerability has been fixed in the Linux kernel source. No known exploits are reported in the wild.

Impact

The vulnerability causes a leak of a cgroup reference, which can lead to resource exhaustion and thus impact system availability. There is no impact on confidentiality or integrity. The CVSS score of 5.5 (medium severity) reflects a local attacker with low privileges being able to cause an availability disruption without user interaction.

Summary

The vulnerability in the Linux kernel relates to the damon_sysfs_memcg_path_to_id() function in the mm/damon/sysfs-schemes code. This function breaks out of a mem_cgroup_iter() loop without calling mem_cgroup_iter_break(), which is required to properly release the cgroup reference. The missing call leads to a reference leak, potentially causing resource exhaustion or availability issues. The fix involves adding the missing mem_cgroup_iter_break() call before breaking the loop. The issue was discovered by Sashiko and is tracked as CVE-2026-64184.

References

Community reviews

Loading reviews…