CVE-2026-72178

UNRATEDCVSS · not yet scoredTrending — 5 sources updated this week
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: —Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

mm/damon/core: always put unsuccessfully committed target pids

damon_commit_target() puts and gets the destination and the source target pids. It puts the destination target pid because it will be overwritten by the source target pid. It gets the source pid because the caller is supposed to eventually put the pids. In more detail, the caller will call damon_destroy_ctx() after damon_commit_ctx() to destroy the entire source context. And in this case, [f]vaddr operation set's cleanup_target() callback will put the pids.

The commit operation is made at the context level. The operation can fail in multiple places including in the middle and after the targets commit operations. For any such failures, immediately the error is returned to the damon_commit_ctx() caller. If some or all of the source target pids were committed to the destination during the unsuccessful context commit attempt, those pids should be put twice.

The source context will do the put operations using the above explained routine. However, let's suppose the destination context was not originally using [f]vaddr operation set and the commit failed before the ops of the source context is committed. The destination does not have the cleanup_target() ops callback, so it cannot put the pids via the damon_destroy_ctx().

As a result, the pids are leaked. The issue in the real world would be not very common. The commit feature is for changing parameters of running DAMON context while inheriting internal status like the monitoring results. The monitoring results of a physical address range ain't have things that are beneficial to be inherited to a virtual address ranges monitoring. So the problem-causing DAMON control would be not very common in the real world. That said, it is a supported feature. And damon_commit_target() failure due to memory allocation is relatively realistic [1] if there are a huge number of target regions.

Fix by putting the pids in the commit operation in case of the failures.

The issue was discovered [2] by Sashiko.

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0%
EPSS %ILE
10%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 17, 2026

References (4)

Vendor Advisories for CVE-2026-72178(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 17× in last 7d / 17× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-20 04:54 UTCGHSA enrichment
  2. 2026-08-19 17:04 UTCEPSS rescore
  3. 2026-08-18 13:49 UTCEPSS rescore
  4. 2026-08-18 13:49 UTCEPSS rescore
  5. 2026-08-17 13:47 UTCEPSS rescore
  6. 2026-08-17 06:20 UTCGHSA enrichment
  7. 2026-08-17 06:18 UTCNVD update
  8. 2026-08-17 05:32 UTCEG score recompute
  9. 2026-08-17 05:32 UTCGHSA enrichment
  10. 2026-08-17 05:24 UTCMITRE cvelistV5
  11. 2026-08-16 14:56 UTCEPSS rescore
  12. 2026-08-16 14:56 UTCEPSS rescore
  13. 2026-08-16 02:15 UTCEPSS rescore
  14. 2026-08-15 06:41 UTCGHSA enrichment
  15. 2026-08-15 06:23 UTCNVD update
  16. 2026-08-15 06:10 UTCEG score recompute
  17. 2026-08-15 06:02 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-72178?
CVE-2026-72178 is a publicly disclosed vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: mm/damon/core: always put unsuccessfully committed target pids damoncommittarget() puts and gets the destination and the source target pids. It puts the destination target pid because it will be overwritten by the source target…
When was CVE-2026-72178 disclosed?
CVE-2026-72178 was first published in the National Vulnerability Database on August 15, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-72178 actively exploited?
CVE-2026-72178 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 89.8% of all scored CVEs.
How do I remediate CVE-2026-72178?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72178, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-72178

Explore →

Is Your Infrastructure Affected by CVE-2026-72178?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs