{"api_version":"1","generated_at":"2026-06-26T17:47:44+00:00","cve":"CVE-2026-53162","urls":{"html":"https://cve.report/CVE-2026-53162","api":"https://cve.report/api/cve/CVE-2026-53162.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-53162","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-53162"},"summary":{"title":"memcg: use round-robin victim selection in refill_stock","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nmemcg: use round-robin victim selection in refill_stock\n\nHarry Yoo reported that get_random_u32_below() is not safe to call in the\nnmi context and memcg charge draining can happen in nmi context.\n\nMore specifically get_random_u32_below() is neither reentrant- nor\nNMI-safe: it acquires a per-cpu local_lock via local_lock_irqsave() on the\nbatched_entropy_u32 state.  An NMI that lands on a CPU mid-update of the\nChaCha batch state and recurses into the random subsystem would corrupt\nthat state.  The memcg_stock local_trylock prevents re-entry on the percpu\nstock itself, but cannot protect an unrelated subsystem's per-cpu lock.\n\nReplace the random pick with a per-cpu round-robin counter stored in\nmemcg_stock_pcp and serialized by the same local_trylock that already\nguards cached[] and nr_pages[].  No atomics, no random calls, no extra\nlocks needed.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-06-25 09:16:33","updated_at":"2026-06-25 09:16:33"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/89bd8215e25aa6999cc51696da418e0d422bc5e0","name":"https://git.kernel.org/stable/c/89bd8215e25aa6999cc51696da418e0d422bc5e0","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/00731bd7e18f182a32ca54d6b176eaa470b51ed7","name":"https://git.kernel.org/stable/c/00731bd7e18f182a32ca54d6b176eaa470b51ed7","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/c0cafe24d3f6534294c4b2bc2d47734ff7cbd313","name":"https://git.kernel.org/stable/c/c0cafe24d3f6534294c4b2bc2d47734ff7cbd313","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-53162","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53162","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected f735eebe55f8f61758fe014bd0b02ab50b059e4d 89bd8215e25aa6999cc51696da418e0d422bc5e0 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected f735eebe55f8f61758fe014bd0b02ab50b059e4d 00731bd7e18f182a32ca54d6b176eaa470b51ed7 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected f735eebe55f8f61758fe014bd0b02ab50b059e4d c0cafe24d3f6534294c4b2bc2d47734ff7cbd313 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.16","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.16 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":"53162","cve":"CVE-2026-53162","epss":"0.001730000","percentile":"0.069790000","score_date":"2026-06-25","updated_at":"2026-06-26 00:06:14"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["mm/memcontrol.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"89bd8215e25aa6999cc51696da418e0d422bc5e0","status":"affected","version":"f735eebe55f8f61758fe014bd0b02ab50b059e4d","versionType":"git"},{"lessThan":"00731bd7e18f182a32ca54d6b176eaa470b51ed7","status":"affected","version":"f735eebe55f8f61758fe014bd0b02ab50b059e4d","versionType":"git"},{"lessThan":"c0cafe24d3f6534294c4b2bc2d47734ff7cbd313","status":"affected","version":"f735eebe55f8f61758fe014bd0b02ab50b059e4d","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["mm/memcontrol.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.16"},{"lessThan":"6.16","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.16","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.0.13","versionStartIncluding":"6.16","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1","versionStartIncluding":"6.16","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nmemcg: use round-robin victim selection in refill_stock\n\nHarry Yoo reported that get_random_u32_below() is not safe to call in the\nnmi context and memcg charge draining can happen in nmi context.\n\nMore specifically get_random_u32_below() is neither reentrant- nor\nNMI-safe: it acquires a per-cpu local_lock via local_lock_irqsave() on the\nbatched_entropy_u32 state.  An NMI that lands on a CPU mid-update of the\nChaCha batch state and recurses into the random subsystem would corrupt\nthat state.  The memcg_stock local_trylock prevents re-entry on the percpu\nstock itself, but cannot protect an unrelated subsystem's per-cpu lock.\n\nReplace the random pick with a per-cpu round-robin counter stored in\nmemcg_stock_pcp and serialized by the same local_trylock that already\nguards cached[] and nr_pages[].  No atomics, no random calls, no extra\nlocks needed."}],"providerMetadata":{"dateUpdated":"2026-06-25T08:38:43.453Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/89bd8215e25aa6999cc51696da418e0d422bc5e0"},{"url":"https://git.kernel.org/stable/c/00731bd7e18f182a32ca54d6b176eaa470b51ed7"},{"url":"https://git.kernel.org/stable/c/c0cafe24d3f6534294c4b2bc2d47734ff7cbd313"}],"title":"memcg: use round-robin victim selection in refill_stock","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-53162","datePublished":"2026-06-25T08:38:43.453Z","dateReserved":"2026-06-09T07:44:35.388Z","dateUpdated":"2026-06-25T08:38:43.453Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-06-25 09:16:33","lastModifiedDate":"2026-06-25 09:16:33","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"53162","Ordinal":"1","Title":"memcg: use round-robin victim selection in refill_stock","CVE":"CVE-2026-53162","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"53162","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nmemcg: use round-robin victim selection in refill_stock\n\nHarry Yoo reported that get_random_u32_below() is not safe to call in the\nnmi context and memcg charge draining can happen in nmi context.\n\nMore specifically get_random_u32_below() is neither reentrant- nor\nNMI-safe: it acquires a per-cpu local_lock via local_lock_irqsave() on the\nbatched_entropy_u32 state.  An NMI that lands on a CPU mid-update of the\nChaCha batch state and recurses into the random subsystem would corrupt\nthat state.  The memcg_stock local_trylock prevents re-entry on the percpu\nstock itself, but cannot protect an unrelated subsystem's per-cpu lock.\n\nReplace the random pick with a per-cpu round-robin counter stored in\nmemcg_stock_pcp and serialized by the same local_trylock that already\nguards cached[] and nr_pages[].  No atomics, no random calls, no extra\nlocks needed.","Type":"Description","Title":"memcg: use round-robin victim selection in refill_stock"}]}}}