{"api_version":"1","generated_at":"2026-07-05T10:11:59+00:00","cve":"CVE-2026-53334","urls":{"html":"https://cve.report/CVE-2026-53334","api":"https://cve.report/api/cve/CVE-2026-53334.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-53334","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-53334"},"summary":{"title":"mm/damon/reclaim: handle ctx allocation failure","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nmm/damon/reclaim: handle ctx allocation failure\n\nPatch series \"mm/damon/{reclaim,lru_sort}: handle ctx allocation failures\".\n\nDAMON_RECLAIM and DAMON_LRU_SORT could dereference NULL pointers if their\ndamon_ctx object allocations fail.  The bugs are expected to happen\ninfrequently because the allocations are arguably too small to fail on\ncommon setups.  But theoretically they are possible and the consequences\nare bad.  Fix those.\n\nThe issues were discovered [1] by Sashiko.\n\n\nThis patch (of 2):\n\nDAMON_RECLAIM allocates the damon_ctx object for its kdamond in its init\nfunction.  damon_reclaim_enabled_store() wrongly assumes the allocation\nwill always succeed once tried.  If the damon_ctx allocation was failed,\ntherefore, code execution reaches to damon_commit_ctx() while 'ctx' is\nNULL.  As a result, it dereferences the NULL 'ctx' pointer.  Avoid the\nNULL dereference by returning -ENOMEM if 'ctx' is NULL.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-07-01 14:16:41","updated_at":"2026-07-01 14:16:41"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/635b45ce61de53a9357e28ac97461428cdb650f0","name":"https://git.kernel.org/stable/c/635b45ce61de53a9357e28ac97461428cdb650f0","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/66bc00ea37fa8ec14be5a3909d067a5967ef234b","name":"https://git.kernel.org/stable/c/66bc00ea37fa8ec14be5a3909d067a5967ef234b","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/7e2ed8a29427af534bf2cb9b8bc51762b8b6e654","name":"https://git.kernel.org/stable/c/7e2ed8a29427af534bf2cb9b8bc51762b8b6e654","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-53334","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53334","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 3f7a914ab9a5e46cf8aac7de270f02aa3f63de04 66bc00ea37fa8ec14be5a3909d067a5967ef234b git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 3f7a914ab9a5e46cf8aac7de270f02aa3f63de04 635b45ce61de53a9357e28ac97461428cdb650f0 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 3f7a914ab9a5e46cf8aac7de270f02aa3f63de04 7e2ed8a29427af534bf2cb9b8bc51762b8b6e654 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.18","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.36 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.0.13 7.0.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"53334","cve":"CVE-2026-53334","epss":"0.001660000","percentile":"0.062090000","score_date":"2026-07-04","updated_at":"2026-07-05 00:02:27"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["mm/damon/reclaim.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"66bc00ea37fa8ec14be5a3909d067a5967ef234b","status":"affected","version":"3f7a914ab9a5e46cf8aac7de270f02aa3f63de04","versionType":"git"},{"lessThan":"635b45ce61de53a9357e28ac97461428cdb650f0","status":"affected","version":"3f7a914ab9a5e46cf8aac7de270f02aa3f63de04","versionType":"git"},{"lessThan":"7e2ed8a29427af534bf2cb9b8bc51762b8b6e654","status":"affected","version":"3f7a914ab9a5e46cf8aac7de270f02aa3f63de04","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["mm/damon/reclaim.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.18"},{"lessThan":"6.18","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.36","versionType":"semver"},{"lessThanOrEqual":"7.0.*","status":"unaffected","version":"7.0.13","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.36","versionStartIncluding":"6.18","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.0.13","versionStartIncluding":"6.18","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1","versionStartIncluding":"6.18","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nmm/damon/reclaim: handle ctx allocation failure\n\nPatch series \"mm/damon/{reclaim,lru_sort}: handle ctx allocation failures\".\n\nDAMON_RECLAIM and DAMON_LRU_SORT could dereference NULL pointers if their\ndamon_ctx object allocations fail.  The bugs are expected to happen\ninfrequently because the allocations are arguably too small to fail on\ncommon setups.  But theoretically they are possible and the consequences\nare bad.  Fix those.\n\nThe issues were discovered [1] by Sashiko.\n\n\nThis patch (of 2):\n\nDAMON_RECLAIM allocates the damon_ctx object for its kdamond in its init\nfunction.  damon_reclaim_enabled_store() wrongly assumes the allocation\nwill always succeed once tried.  If the damon_ctx allocation was failed,\ntherefore, code execution reaches to damon_commit_ctx() while 'ctx' is\nNULL.  As a result, it dereferences the NULL 'ctx' pointer.  Avoid the\nNULL dereference by returning -ENOMEM if 'ctx' is NULL."}],"providerMetadata":{"dateUpdated":"2026-07-01T13:32:17.419Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/66bc00ea37fa8ec14be5a3909d067a5967ef234b"},{"url":"https://git.kernel.org/stable/c/635b45ce61de53a9357e28ac97461428cdb650f0"},{"url":"https://git.kernel.org/stable/c/7e2ed8a29427af534bf2cb9b8bc51762b8b6e654"}],"title":"mm/damon/reclaim: handle ctx allocation failure","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-53334","datePublished":"2026-07-01T13:32:17.419Z","dateReserved":"2026-06-09T07:44:35.398Z","dateUpdated":"2026-07-01T13:32:17.419Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-07-01 14:16:41","lastModifiedDate":"2026-07-01 14:16:41","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"53334","Ordinal":"1","Title":"mm/damon/reclaim: handle ctx allocation failure","CVE":"CVE-2026-53334","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"53334","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nmm/damon/reclaim: handle ctx allocation failure\n\nPatch series \"mm/damon/{reclaim,lru_sort}: handle ctx allocation failures\".\n\nDAMON_RECLAIM and DAMON_LRU_SORT could dereference NULL pointers if their\ndamon_ctx object allocations fail.  The bugs are expected to happen\ninfrequently because the allocations are arguably too small to fail on\ncommon setups.  But theoretically they are possible and the consequences\nare bad.  Fix those.\n\nThe issues were discovered [1] by Sashiko.\n\n\nThis patch (of 2):\n\nDAMON_RECLAIM allocates the damon_ctx object for its kdamond in its init\nfunction.  damon_reclaim_enabled_store() wrongly assumes the allocation\nwill always succeed once tried.  If the damon_ctx allocation was failed,\ntherefore, code execution reaches to damon_commit_ctx() while 'ctx' is\nNULL.  As a result, it dereferences the NULL 'ctx' pointer.  Avoid the\nNULL dereference by returning -ENOMEM if 'ctx' is NULL.","Type":"Description","Title":"mm/damon/reclaim: handle ctx allocation failure"}]}}}