{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2026-99657","assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","state":"PUBLISHED","assignerShortName":"Linux","dateReserved":"2026-09-25T10:25:14.427Z","datePublished":"2026-11-20T05:50:09.250Z","dateUpdated":"2026-11-22T11:09:28.093Z"},"containers":{"cna":{"providerMetadata":{"orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux","dateUpdated":"2026-11-22T11:09:28.093Z"},"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nmm/mmu_notifier: set ->mm only after mmgrab()\n\nRadeon uses a non-NULL notifier->mm to decide whether to call\nmmu_interval_notifier_remove() when freeing a buffer object.\n__mmu_interval_notifier_insert() sets ->mm before validating the range,\nso a wrapping userptr range can leave ->mm set after insertion fails.\nCleanup then tries to remove an unregistered notifier for which no mm\nreference was acquired.\n\nSet ->mm only after mmgrab(), once insertion can no longer fail. While\nwe could fix radeon's code instead, setting ->mm on success only makes\nthe code more robust.\n\nFix generated by an LLM and sent by Chris Mason in private.\n\n[ david: simplify description ]"}],"metrics":[{"cvssV3_1":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","baseScore":7.8,"baseSeverity":"HIGH"},"scenarios":[{"lang":"en","value":"AV:L - The wrapping range is the addr and size of DRM_IOCTL_RADEON_GEM_USERPTR, passed by radeon_gem_userptr_ioctl into radeon_mn_register then mmu_interval_notifier_insert/__mmu_interval_notifier_insert. Those bytes come from the local ioctl argument, not from a remote protocol or from disk.\nAC:L - radeon_gem_userptr_ioctl only rejects a non-page-aligned addr|size, so the caller can choose a range whose start+length-1 overflows check_add_overflow. The -EOVERFLOW path always drops the GEM object, and radeon_gem_object_free calls radeon_mn_unregister. The attacker issues that ioctl; no external state is required.\nPR:L - radeon_ioctls_kms marks RADEON_GEM_USERPTR DRM_AUTH|DRM_RENDER_ALLOW, and drm_ioctl_permit() skips DRM_AUTH for a render client. An unprivileged process that can open the radeon render node reaches radeon_gem_userptr_ioctl without CAP_SYS_ADMIN.\nUI:N - The attacker opens the radeon render node and calls radeon_gem_userptr_ioctl with the wrapping userptr. No other user has to mount media or act on the range.\nS:U - The unpaired mmdrop frees the caller's own mm_struct in the host kernel. That is kernel memory corruption in the same security authority as the radeon ioctl, the usual kernel privilege-escalation scope.\nC:H - On overflow __mmu_interval_notifier_insert set interval_sub->mm and returned before mmgrab, but radeon_mn_unregister still calls mmu_interval_notifier_remove, which mmdrops that mm. __mmdrop then pgd_free's and free_mm's a live mm (mm_init sets mm_count to 1), a page-table use-after-free that can disclose memory.\nI:H - The same unpaired mmdrop in mmu_interval_notifier_remove frees the active mm and its PGD while other threads of that process still run with CR3 aimed at it. Reclaiming the freed PGD gives a write primitive.\nA:H - __mmdrop of current->mm, reached from radeon_gem_object_free on the failed userptr ioctl, runs mm_free_pgd and free_mm on the live address space. The ioctl then keeps using that mm and returns to user mode, which oopses the kernel."}]}],"affected":[{"product":"Linux","vendor":"Linux","defaultStatus":"unaffected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["mm/mmu_notifier.c"],"versions":[{"version":"3506ff69c3ec725b9c3e7f074fd2d265922f139a","lessThan":"fe3b7bf598ba708431d531cfbb1035b8a463eed9","status":"affected","versionType":"git"},{"version":"3506ff69c3ec725b9c3e7f074fd2d265922f139a","lessThan":"3df451b65b6bc342d9291b1132baf4a4dd3a7b63","status":"affected","versionType":"git"},{"version":"3506ff69c3ec725b9c3e7f074fd2d265922f139a","lessThan":"0d9450d006506d2af7016afd435b9c1a24985d02","status":"affected","versionType":"git"},{"version":"3506ff69c3ec725b9c3e7f074fd2d265922f139a","lessThan":"5ad9e4b0f1104f5dbfb41125c34bb30ea6dc7a94","status":"affected","versionType":"git"}]},{"product":"Linux","vendor":"Linux","defaultStatus":"affected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["mm/mmu_notifier.c"],"versions":[{"version":"5.5","status":"affected"},{"version":"0","lessThan":"5.5","status":"unaffected","versionType":"semver"},{"version":"6.12.118","lessThanOrEqual":"6.12.*","status":"unaffected","versionType":"semver"},{"version":"6.18.64","lessThanOrEqual":"6.18.*","status":"unaffected","versionType":"semver"},{"version":"7.3.5","lessThanOrEqual":"7.3.*","status":"unaffected","versionType":"semver"},{"version":"7.4-rc2","lessThanOrEqual":"*","status":"unaffected","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.5","versionEndExcluding":"6.12.118"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.5","versionEndExcluding":"6.18.64"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.5","versionEndExcluding":"7.3.5"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.5","versionEndExcluding":"7.4-rc2"}]}]}],"references":[{"url":"https://git.kernel.org/stable/c/fe3b7bf598ba708431d531cfbb1035b8a463eed9"},{"url":"https://git.kernel.org/stable/c/3df451b65b6bc342d9291b1132baf4a4dd3a7b63"},{"url":"https://git.kernel.org/stable/c/0d9450d006506d2af7016afd435b9c1a24985d02"},{"url":"https://git.kernel.org/stable/c/5ad9e4b0f1104f5dbfb41125c34bb30ea6dc7a94"}],"title":"mm/mmu_notifier: set ->mm only after mmgrab()","x_generator":{"engine":"bippy-1.2.0"}}}}