{"api_version":"1","generated_at":"2026-05-28T07:33:02+00:00","cve":"CVE-2026-46067","urls":{"html":"https://cve.report/CVE-2026-46067","api":"https://cve.report/api/cve/CVE-2026-46067.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-46067","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-46067"},"summary":{"title":"mm/damon/core: validate damos_quota_goal->nid for node_memcg_{used,free}_bp","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nmm/damon/core: validate damos_quota_goal->nid for node_memcg_{used,free}_bp\n\nUsers can set damos_quota_goal->nid with arbitrary value for\nnode_memcg_{used,free}_bp.  But DAMON core is using those for NODE-DATA()\nwithout a validation of the value.  This can result in out of bounds\nmemory access.  The issue can actually triggered using DAMON user-space\ntool (damo), like below.\n\n    $ sudo mkdir /sys/fs/cgroup/foo\n    $ sudo ./damo start --damos_action stat --damos_quota_interval 1s \\\n            --damos_quota_goal node_memcg_used_bp 50% -1 /foo\n    $ sudo dmseg\n    [...]\n    [  524.181426] Unable to handle kernel paging request at virtual address 0000000000002c00\n\nFix this issue by adding the validation of the given node id.  If an\ninvalid node id is given, it returns 0% for used memory ratio, and 100%\nfor free memory ratio.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-05-27 14:17:27","updated_at":"2026-05-27 14:48:03"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/a34dac6482e53e2c76944f25b1489b9b7da3a6e6","name":"https://git.kernel.org/stable/c/a34dac6482e53e2c76944f25b1489b9b7da3a6e6","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/da10db73ada26345244ea5dc52f974692bd05f66","name":"https://git.kernel.org/stable/c/da10db73ada26345244ea5dc52f974692bd05f66","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-46067","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46067","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected b74a120bcf50787e5b9a2c3dcff999f9836ce1db da10db73ada26345244ea5dc52f974692bd05f66 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected b74a120bcf50787e5b9a2c3dcff999f9836ce1db a34dac6482e53e2c76944f25b1489b9b7da3a6e6 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.19","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.19 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.0.4 7.0.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1-rc1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["mm/damon/core.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"da10db73ada26345244ea5dc52f974692bd05f66","status":"affected","version":"b74a120bcf50787e5b9a2c3dcff999f9836ce1db","versionType":"git"},{"lessThan":"a34dac6482e53e2c76944f25b1489b9b7da3a6e6","status":"affected","version":"b74a120bcf50787e5b9a2c3dcff999f9836ce1db","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["mm/damon/core.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.19"},{"lessThan":"6.19","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"7.0.*","status":"unaffected","version":"7.0.4","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.1-rc1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.0.4","versionStartIncluding":"6.19","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1-rc1","versionStartIncluding":"6.19","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nmm/damon/core: validate damos_quota_goal->nid for node_memcg_{used,free}_bp\n\nUsers can set damos_quota_goal->nid with arbitrary value for\nnode_memcg_{used,free}_bp.  But DAMON core is using those for NODE-DATA()\nwithout a validation of the value.  This can result in out of bounds\nmemory access.  The issue can actually triggered using DAMON user-space\ntool (damo), like below.\n\n    $ sudo mkdir /sys/fs/cgroup/foo\n    $ sudo ./damo start --damos_action stat --damos_quota_interval 1s \\\n            --damos_quota_goal node_memcg_used_bp 50% -1 /foo\n    $ sudo dmseg\n    [...]\n    [  524.181426] Unable to handle kernel paging request at virtual address 0000000000002c00\n\nFix this issue by adding the validation of the given node id.  If an\ninvalid node id is given, it returns 0% for used memory ratio, and 100%\nfor free memory ratio."}],"providerMetadata":{"dateUpdated":"2026-05-27T12:57:45.648Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/da10db73ada26345244ea5dc52f974692bd05f66"},{"url":"https://git.kernel.org/stable/c/a34dac6482e53e2c76944f25b1489b9b7da3a6e6"}],"title":"mm/damon/core: validate damos_quota_goal->nid for node_memcg_{used,free}_bp","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-46067","datePublished":"2026-05-27T12:57:45.648Z","dateReserved":"2026-05-13T15:03:33.095Z","dateUpdated":"2026-05-27T12:57:45.648Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-05-27 14:17:27","lastModifiedDate":"2026-05-27 14:48:03","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"46067","Ordinal":"1","Title":"mm/damon/core: validate damos_quota_goal->nid for node_memcg_{us","CVE":"CVE-2026-46067","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"46067","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nmm/damon/core: validate damos_quota_goal->nid for node_memcg_{used,free}_bp\n\nUsers can set damos_quota_goal->nid with arbitrary value for\nnode_memcg_{used,free}_bp.  But DAMON core is using those for NODE-DATA()\nwithout a validation of the value.  This can result in out of bounds\nmemory access.  The issue can actually triggered using DAMON user-space\ntool (damo), like below.\n\n    $ sudo mkdir /sys/fs/cgroup/foo\n    $ sudo ./damo start --damos_action stat --damos_quota_interval 1s \\\n            --damos_quota_goal node_memcg_used_bp 50% -1 /foo\n    $ sudo dmseg\n    [...]\n    [  524.181426] Unable to handle kernel paging request at virtual address 0000000000002c00\n\nFix this issue by adding the validation of the given node id.  If an\ninvalid node id is given, it returns 0% for used memory ratio, and 100%\nfor free memory ratio.","Type":"Description","Title":"mm/damon/core: validate damos_quota_goal->nid for node_memcg_{us"}]}}}