CVE-2026-46067

HIGHNVD 7.17.1
EchelonGraph scoreMEDIUM confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-05-27. NVD baseline CVSS 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 5 sources updated this week
7.1EG
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.1Exploit: None knownExposed: 0

A fix is available — apply it.

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

mm/damon/core: validate damos_quota_goal->nid for node_memcg_{used,free}_bp

Users can set damos_quota_goal->nid with arbitrary value for node_memcg_{used,free}_bp. But DAMON core is using those for NODE-DATA() without a validation of the value. This can result in out of bounds memory access. The issue can actually triggered using DAMON user-space tool (damo), like below.

$ sudo mkdir /sys/fs/cgroup/foo $ sudo ./damo start --damos_action stat --damos_quota_interval 1s \ --damos_quota_goal node_memcg_used_bp 50% -1 /foo $ sudo dmseg [...] [ 524.181426] Unable to handle kernel paging request at virtual address 0000000000002c00

Fix this issue by adding the validation of the given node id. If an invalid node id is given, it returns 0% for used memory ratio, and 100% for free memory ratio.

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
36(Track)
EG Risk 36/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
Severity71% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

May 27, 2026

Last Modified

June 24, 2026

Advisory Details (2)

Auto-updated Jun 24, 2026
No patch confirmed yet.
generic

mm/damon/core: validate damos_quota_goal->nid for node_memcg_{used,free}_bp - kernel/git/stable/linux.git - Linux kernel stable tree

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

mm/damon/core: validate damos_quota_goal->nid for node_memcg_{used,free}_bp - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a34dac6482e53e2c76944f25b1489b9b7da3a6e6

Vendor Advisories for CVE-2026-46067(1)

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

Patch Availability(7)

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

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.4-1~bpo13+1 (134 versions)7.0.4-1

Weakness Classification(1)

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

All Vendor Advisories

(6)

Data Freshness Timeline

(refreshed 10× in last 7d / 43× 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 234 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-46067?
CVE-2026-46067 is a high vulnerability published on May 27, 2026. In the Linux kernel, the following vulnerability has been resolved: mm/damon/core: validate damosquotagoal->nid for nodememcg{used,free}_bp Users can set damosquotagoal->nid with arbitrary value for nodememcg{used,free}_bp. But DAMON core is using those for NODE-DATA() without a validation of the…
When was CVE-2026-46067 disclosed?
CVE-2026-46067 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on June 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46067 actively exploited?
CVE-2026-46067 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.1% of all scored CVEs.
What is the CVSS score of CVE-2026-46067?
CVE-2026-46067 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-46067?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46067, 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-46067

Explore →

Is Your Infrastructure Affected by CVE-2026-46067?

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