linux: In the Linux kernel, the following vulnerability has been resolved: mm/damon/core: validate damos_quota_goal->nid fo...
CVE-2026-46020 is fixed in 19 products on 1 platform, first by ALAS2023-2026-1754, released May 25, 2026. It is not reported as exploited. Patch Radar priority: High.
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.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| bpftool6.18 · amzn 2023 | 1:6.18.30-61.116.amzn2023 | ALAS2023-2026-1754 | May 25, 2026 |
| bpftool6.18-debuginfo · amzn 2023 | 1:6.18.30-61.116.amzn2023 | ALAS2023-2026-1754 | May 25, 2026 |
| kernel-livepatch-6.18.30-61.116 · amzn 2023 | 1:1.0-0.amzn2023 | ALAS2023-2026-1754 | May 25, 2026 |
| kernel6.18 · amzn 2023 | 1:6.18.30-61.116.amzn2023 | ALAS2023-2026-1754 | May 25, 2026 |
| kernel6.18-debuginfo · amzn 2023 | 1:6.18.30-61.116.amzn2023 | ALAS2023-2026-1754 | May 25, 2026 |
| kernel6.18-debuginfo-common-aarch64 · amzn 2023 | 1:6.18.30-61.116.amzn2023 | ALAS2023-2026-1754 | May 25, 2026 |
| kernel6.18-debuginfo-common-x86_64 · amzn 2023 | 1:6.18.30-61.116.amzn2023 | ALAS2023-2026-1754 | May 25, 2026 |
| kernel6.18-devel · amzn 2023 | 1:6.18.30-61.116.amzn2023 | ALAS2023-2026-1754 | May 25, 2026 |
| kernel6.18-headers · amzn 2023 | 1:6.18.30-61.116.amzn2023 | ALAS2023-2026-1754 | May 25, 2026 |
| kernel6.18-modules-extra · amzn 2023 | 1:6.18.30-61.116.amzn2023 | ALAS2023-2026-1754 | May 25, 2026 |
| kernel6.18-modules-extra-common · amzn 2023 | 1:6.18.30-61.116.amzn2023 | ALAS2023-2026-1754 | May 25, 2026 |
| kernel6.18-tools · amzn 2023 | 1:6.18.30-61.116.amzn2023 | ALAS2023-2026-1754 | May 25, 2026 |
| kernel6.18-tools-debuginfo · amzn 2023 | 1:6.18.30-61.116.amzn2023 | ALAS2023-2026-1754 | May 25, 2026 |
| kernel6.18-tools-devel · amzn 2023 | 1:6.18.30-61.116.amzn2023 | ALAS2023-2026-1754 | May 25, 2026 |
| linux · Debian 14 | 7.0.4-1 | DEBIAN-CVE-2026-46020 | May 27, 2026 |
| perf6.18 · amzn 2023 | 1:6.18.30-61.116.amzn2023 | ALAS2023-2026-1754 | May 25, 2026 |
| perf6.18-debuginfo · amzn 2023 | 1:6.18.30-61.116.amzn2023 | ALAS2023-2026-1754 | May 25, 2026 |
| python3-perf6.18 · amzn 2023 | 1:6.18.30-61.116.amzn2023 | ALAS2023-2026-1754 | May 25, 2026 |
| python3-perf6.18-debuginfo · amzn 2023 | 1:6.18.30-61.116.amzn2023 | ALAS2023-2026-1754 | May 25, 2026 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.