CVE-2026-64239

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-24. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

mm/damon/sysfs-schemes: delete tried region in regions_rmdirs()

DAMON sysfs maintains the DAMOS tried region directory objects via a linked list. When the user requests refresh of the directories, DAMON sysfs removes all the region directories first, and then generate updated regions directory on the empty space. The removal function (damon_sysfs_scheme_regions_rm_dirs()) only puts the kobj objects. Deletion of the container region object from the linked list is done inside the kobj release callback function.

If somehow the callback invocation is delayed, the list will contain regions list that gonna be freed. If the updated region directories creation is started in this situation, the list can be corrupted and use-after-free can happen.

Because the kobj objects are managed by only DAMON sysfs, the issue cannot happen in normal situation. But, such delays can be made on kernels that built with CONFIG_DEBUG_KOBJECT_RELEASE. On the kernel, the issue can indeed be reproduced like below.

# damo start --damos_action stat # cd /sys/kernel/mm/damon/admin/kdamonds/0/ # for i in {1..10}; do echo update_schemes_tried_regions > state; done # dmesg | grep underflow [ 89.296152] refcount_t: underflow; use-after-free.

Fix the issue by removing the region object from the list when decrementing the reference count.

Also update damos_sysfs_populate_region_dir() to add the region object to the list only after the kobject_init_and_add() is success, so that fail of kobject_init_and_add() is not leaving the deallocated object on the list.

The issue was discovered [1] by Sashiko.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

July 24, 2026

Last Modified

August 13, 2026

Advisory Details (5)

Auto-updated Aug 13, 2026
No patch confirmed yet.
generic

mm/damon/sysfs-schemes: delete tried region in regions_rmdirs() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c0e37017a452addec873865c94cf7a665663a9b2
generic

mm/damon/sysfs-schemes: delete tried region in regions_rmdirs() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a5fa42214de55e43d165144727ce9facb9fc6b08
generic

mm/damon/sysfs-schemes: delete tried region in regions_rmdirs() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/441f92f7d386b85bad16de49db95a307cba048a2
generic

mm/damon/sysfs-schemes: delete tried region in regions_rmdirs() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2c33177023c92e76806c535ddbffaa3d3fc37777
generic

mm/damon/sysfs-schemes: delete tried region in regions_rmdirs() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0ba6c05156d9ff9fc6ca22b7690e2eec9eca66f7

Vendor Advisories for CVE-2026-64239(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)

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 rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (138 versions)7.0.12-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

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 30× in last 7d / 109× 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.

Showing the most recent 100 of 125 total refreshes for this CVE.

  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-30 00:18 UTCEG score recompute
  3. 2026-08-30 00:18 UTCVendor advisory
  4. 2026-08-30 00:18 UTCGHSA enrichment
  5. 2026-08-28 21:42 UTCEPSS rescore
  6. 2026-08-27 23:49 UTCEG score recompute
  7. 2026-08-27 23:49 UTCVendor advisory
  8. 2026-08-27 23:49 UTCGHSA enrichment
  9. 2026-08-27 12:27 UTCVendor advisory
  10. 2026-08-27 12:27 UTCGHSA enrichment
  11. 2026-08-27 01:05 UTCEG score recompute
  12. 2026-08-27 01:05 UTCVendor advisory
  13. 2026-08-27 01:05 UTCGHSA enrichment
  14. 2026-08-26 14:47 UTCEPSS rescore
  15. 2026-08-26 13:39 UTCVendor advisory
  16. 2026-08-26 13:39 UTCGHSA enrichment
  17. 2026-08-26 01:47 UTCVendor advisory
  18. 2026-08-26 01:47 UTCGHSA enrichment
  19. 2026-08-25 14:26 UTCVendor advisory
  20. 2026-08-25 14:25 UTCGHSA enrichment
  21. 2026-08-25 02:42 UTCVendor advisory
  22. 2026-08-25 02:42 UTCGHSA enrichment
  23. 2026-08-24 15:21 UTCEG score recompute
  24. 2026-08-24 15:21 UTCVendor advisory
  25. 2026-08-24 15:20 UTCGHSA enrichment
Show 75 more
  1. 2026-08-24 03:59 UTCEG score recompute
  2. 2026-08-24 03:59 UTCVendor advisory
  3. 2026-08-24 03:59 UTCGHSA enrichment
  4. 2026-08-23 16:37 UTCVendor advisory
  5. 2026-08-23 16:37 UTCGHSA enrichment
  6. 2026-08-23 05:16 UTCVendor advisory
  7. 2026-08-23 05:15 UTCGHSA enrichment
  8. 2026-08-22 17:54 UTCVendor advisory
  9. 2026-08-22 17:54 UTCGHSA enrichment
  10. 2026-08-22 06:32 UTCEG score recompute
  11. 2026-08-22 06:32 UTCVendor advisory
  12. 2026-08-22 06:32 UTCGHSA enrichment
  13. 2026-08-21 23:49 UTCEPSS rescore
  14. 2026-08-21 19:10 UTCVendor advisory
  15. 2026-08-21 19:10 UTCGHSA enrichment
  16. 2026-08-21 07:49 UTCEG score recompute
  17. 2026-08-21 07:49 UTCVendor advisory
  18. 2026-08-21 07:49 UTCGHSA enrichment
  19. 2026-08-20 22:55 UTCEPSS rescore
  20. 2026-08-20 20:27 UTCVendor advisory
  21. 2026-08-20 20:27 UTCGHSA enrichment
  22. 2026-08-20 09:06 UTCVendor advisory
  23. 2026-08-20 09:06 UTCGHSA enrichment
  24. 2026-08-19 21:44 UTCEG score recompute
  25. 2026-08-19 21:44 UTCVendor advisory
  26. 2026-08-19 21:44 UTCGHSA enrichment
  27. 2026-08-19 17:04 UTCEPSS rescore
  28. 2026-08-19 10:13 UTCVendor advisory
  29. 2026-08-19 10:13 UTCGHSA enrichment
  30. 2026-08-18 22:49 UTCVendor advisory
  31. 2026-08-18 22:49 UTCGHSA enrichment
  32. 2026-08-18 11:16 UTCVendor advisory
  33. 2026-08-18 11:16 UTCGHSA enrichment
  34. 2026-08-17 23:46 UTCEG score recompute
  35. 2026-08-17 23:46 UTCVendor advisory
  36. 2026-08-17 23:46 UTCGHSA enrichment
  37. 2026-08-17 13:47 UTCEPSS rescore
  38. 2026-08-17 12:24 UTCVendor advisory
  39. 2026-08-17 12:24 UTCGHSA enrichment
  40. 2026-08-17 01:00 UTCEG score recompute
  41. 2026-08-17 01:00 UTCVendor advisory
  42. 2026-08-17 01:00 UTCGHSA enrichment
  43. 2026-08-16 14:56 UTCEPSS rescore
  44. 2026-08-16 13:38 UTCVendor advisory
  45. 2026-08-16 13:38 UTCGHSA enrichment
  46. 2026-08-16 02:16 UTCEG score recompute
  47. 2026-08-16 02:16 UTCVendor advisory
  48. 2026-08-16 02:16 UTCGHSA enrichment
  49. 2026-08-15 14:55 UTCVendor advisory
  50. 2026-08-15 14:55 UTCGHSA enrichment
  51. 2026-08-15 03:33 UTCEG score recompute
  52. 2026-08-15 03:33 UTCVendor advisory
  53. 2026-08-15 03:33 UTCGHSA enrichment
  54. 2026-08-15 01:30 UTCEPSS rescore
  55. 2026-08-14 16:11 UTCVendor advisory
  56. 2026-08-14 16:11 UTCGHSA enrichment
  57. 2026-08-14 04:50 UTCEG score recompute
  58. 2026-08-14 04:50 UTCVendor advisory
  59. 2026-08-14 04:50 UTCGHSA enrichment
  60. 2026-08-13 22:00 UTCEPSS rescore
  61. 2026-08-13 17:28 UTCEG score recompute 7.80
  62. 2026-08-13 17:28 UTCVendor advisory
  63. 2026-08-13 17:28 UTCGHSA enrichment
  64. 2026-08-13 17:27 UTCNVD updateCVSS v3 → 7.8 · severity → HIGH
  65. 2026-08-12 13:51 UTCEPSS rescore
  66. 2026-08-12 09:01 UTCVendor advisory
  67. 2026-08-12 09:00 UTCGHSA enrichment
  68. 2026-08-11 00:00 UTCEPSS rescore
  69. 2026-08-09 13:47 UTCEPSS rescore
  70. 2026-08-09 04:34 UTCVendor advisory
  71. 2026-08-09 04:34 UTCGHSA enrichment
  72. 2026-08-08 16:37 UTCEPSS rescore
  73. 2026-08-06 13:47 UTCEPSS rescore
  74. 2026-08-06 00:08 UTCVendor advisory
  75. 2026-08-06 00:08 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-64239?
CVE-2026-64239 is a high vulnerability published on July 24, 2026. In the Linux kernel, the following vulnerability has been resolved: mm/damon/sysfs-schemes: delete tried region in regions_rmdirs() DAMON sysfs maintains the DAMOS tried region directory objects via a linked list. When the user requests refresh of the directories, DAMON sysfs removes all the region…
When was CVE-2026-64239 disclosed?
CVE-2026-64239 was first published in the National Vulnerability Database on July 24, 2026, with the most recent update on August 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64239 actively exploited?
CVE-2026-64239 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 98.2% of all scored CVEs.
What is the CVSS score of CVE-2026-64239?
CVE-2026-64239 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-64239?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64239, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-64239

Explore →

Is Your Infrastructure Affected by CVE-2026-64239?

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