CVE-2026-72178

UNRATEDCVSS · not yet scored
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.2%
EPSS %ILE
10th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

EG Severity
Not assessed: no CVSS publishedA missing CVSS is not a severity of zero.
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
No SSVC decision: EchelonGraph has not assessed this CVECISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the BOD 26-04 block below.

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

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.

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-oem-7.0 (7.0.0-1015.15) @ resolute2026-10-07ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-38.38) @ resolute2026-10-07ubuntu
ubuntulinux-tools-azure-lts-26.04 (7.0.0-1017.17) @ resolute2026-10-07ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.96-1 (31 versions)
  • every version up to 6.12.100-1: fixed in 6.12.100-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (160 versions)
  • every version up to 7.1.5-1: fixed in 7.1.5-1
—

All Vendor Advisories

(3)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

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

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 84 are merged into the row they repeat.

  1. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  2. 2026-10-18 03:16 UTCEG score recompute
  3. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  4. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  5. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  6. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  7. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  8. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  9. 2026-10-12 15:42 UTCEG score recompute
  10. 2026-10-11 19:27 UTCEG score recompute
  11. 2026-10-11 16:43 UTCEG score recompute
  12. 2026-10-11 14:03 UTCEG score recompute
  13. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  14. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  15. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  16. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  17. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  18. 2026-10-07 02:20 UTCVendor advisory
  19. 2026-10-07 02:20 UTCGHSA enrichmentGHSA-g93q-9jrc-mrwv
  20. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  21. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  22. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  23. 2026-10-04 03:42 UTCGHSA enrichmentGHSA-g93q-9jrc-mrwv
  24. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  25. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 9th percentile
Show 57 more
  1. 2026-10-01 01:39 UTCEG score recompute
  2. 2026-10-01 01:39 UTCGHSA enrichmentGHSA-g93q-9jrc-mrwv
  3. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  4. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  5. 2026-09-28 01:24 UTCGHSA enrichmentGHSA-g93q-9jrc-mrwv
  6. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  7. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  8. 2026-09-25 02:49 UTCGHSA enrichmentGHSA-g93q-9jrc-mrwv
  9. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  10. 2026-09-21 22:12 UTCGHSA enrichmentGHSA-g93q-9jrc-mrwv
  11. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  12. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  13. 2026-09-18 23:38 UTCGHSA enrichmentGHSA-g93q-9jrc-mrwv
  14. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  15. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  16. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  17. 2026-09-16 01:01 UTCGHSA enrichmentGHSA-g93q-9jrc-mrwv
  18. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  19. 2026-09-13 02:04 UTCGHSA enrichmentGHSA-g93q-9jrc-mrwv
  20. 2026-09-12 15:02 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  21. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  22. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  23. 2026-09-10 03:30 UTCGHSA enrichmentGHSA-g93q-9jrc-mrwv
  24. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  25. 2026-09-07 04:57 UTCGHSA enrichmentGHSA-g93q-9jrc-mrwv
  26. 2026-09-06 13:48 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  27. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  28. 2026-09-04 03:53 UTCGHSA enrichmentGHSA-g93q-9jrc-mrwv
  29. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  30. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  31. 2026-09-01 05:19 UTCGHSA enrichmentGHSA-g93q-9jrc-mrwv
  32. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  33. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  34. 2026-08-29 06:40 UTCGHSA enrichmentGHSA-g93q-9jrc-mrwv
  35. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  36. 2026-08-26 14:47 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  37. 2026-08-26 01:59 UTCGHSA enrichmentGHSA-g93q-9jrc-mrwv
  38. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  39. 2026-08-23 03:26 UTCGHSA enrichmentGHSA-g93q-9jrc-mrwv
  40. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  41. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  42. 2026-08-20 22:56 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  43. 2026-08-20 04:54 UTCGHSA enrichmentGHSA-g93q-9jrc-mrwv
  44. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  45. 2026-08-18 13:49 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  46. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  47. 2026-08-17 06:20 UTCGHSA enrichmentGHSA-g93q-9jrc-mrwv
  48. 2026-08-17 06:18 UTCNVD update
  49. 2026-08-17 05:32 UTCEG score recompute
  50. 2026-08-17 05:32 UTCGHSA enrichmentGHSA-g93q-9jrc-mrwv
  51. 2026-08-17 05:24 UTCMITRE cvelistV5
  52. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  53. 2026-08-16 02:15 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  54. 2026-08-15 06:41 UTCGHSA enrichmentGHSA-g93q-9jrc-mrwv
  55. 2026-08-15 06:23 UTCNVD update
  56. 2026-08-15 06:10 UTCEG score recompute
  57. 2026-08-15 06:02 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor)

Frequently asked(4)

What is CVE-2026-72178?
CVE-2026-72178 is a vulnerability whose severity is not yet rated; its CVE record was 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 the CVE record for CVE-2026-72178 published?
The CVE record for CVE-2026-72178 was published on August 15, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 17, 2026; the record at its source may have been updated since.
Is CVE-2026-72178 actively exploited?
CVE-2026-72178 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (10th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-72178?
A fix for CVE-2026-72178 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-72178 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.

Book a Demo →Browse All CVEs