CVE-2026-46020

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 — 4 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_mem_{used,free}_bp

Patch series "mm/damon/core: validate damos_quota_goal->nid".

node_mem[cg]_{used,free}_bp DAMOS quota goals receive the node id. The node id is used for si_meminfo_node() and NODE_DATA() without proper validation. As a result, privileged users can trigger an out of bounds memory access using DAMON_SYSFS. Fix the issues.

The issue was originally reported [1] with a fix by another author. The original author announced [2] that they will stop working including the fix that was still in the review stage. Hence I'm restarting this.

This patch (of 2):

Users can set damos_quota_goal->nid with arbitrary value for node_mem_{used,free}_bp. But DAMON core is using those for si_meminfo_node() without the 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 ./damo start --damos_action stat \ --damos_quota_goal node_mem_used_bp 50% -1 \ --damos_quota_interval 1s $ sudo dmesg [...] [ 65.565986] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000098

Fix this issue by adding the validation of the given node. 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
3%
KEV
Not listed

Published

May 27, 2026

Last Modified

June 16, 2026

Advisory Details (3)

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

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

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

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

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

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

https://git.kernel.org/stable/c/40250b2dded0604a112be605f3828700d80ad7c2

Vendor Advisories for CVE-2026-46020(1)

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

Patch Availability(6)

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.

Weakness Classification(1)

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

All Vendor Advisories

(6)

Data Freshness Timeline

(refreshed 15× in last 7d / 41× 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 118 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-46020?
CVE-2026-46020 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 nodemem{used,free}_bp Patch series "mm/damon/core: validate damosquotagoal->nid". nodemem[cg]{used,free}_bp DAMOS quota goals receive the node id. The node id is used for…
When was CVE-2026-46020 disclosed?
CVE-2026-46020 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on June 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46020 actively exploited?
CVE-2026-46020 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 97.5% of all scored CVEs.
What is the CVSS score of CVE-2026-46020?
CVE-2026-46020 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-46020?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46020, 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-46020

Explore →

Is Your Infrastructure Affected by CVE-2026-46020?

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