CVE-2026-46020
Last modified
CVE-2026-46020 is a high-severity vulnerability rated 7.1/10 on the CVSS scale. 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. EPSS estimates a 0.12% chance of exploitation in the next 30 days.
Description
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 6.16, < 6.18.27 |
| Linux | Linux Kernel | >= 6.19, < 7.0.4 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-46020?
How severe is CVE-2026-46020?
How do I fix CVE-2026-46020?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-46015In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-46016In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-46017In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2026-46018In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-46019In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-4602Versions of the package jsrsasign before 11.1.1 are vulnerab…7.7
- CVE-2026-46021In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-46022In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-46023In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-46024In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-46025In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2026-46026In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2026-46020?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
