{"api_version":"1","generated_at":"2026-11-22T20:39:57+00:00","cve":"CVE-2026-99657","urls":{"html":"https://cve.report/CVE-2026-99657","api":"https://cve.report/api/cve/CVE-2026-99657.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-99657","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-99657"},"summary":{"title":"mm/mmu_notifier: set ->mm only after mmgrab()","description":"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 ]","state":"PUBLISHED","assigner":"Linux","published_at":"2026-11-20 06:17:59","updated_at":"2026-11-22 11:17:04"},"problem_types":[],"metrics":[{"version":"3.1","source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","type":"Secondary","score":"7.8","severity":"HIGH","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","data":{"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","attackVector":"LOCAL","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH"}},{"version":"3.1","source":"CNA","type":"DECLARED","score":"7.8","severity":"HIGH","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","data":{"baseScore":7.8,"baseSeverity":"HIGH","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"}}],"references":[{"url":"https://git.kernel.org/stable/c/3df451b65b6bc342d9291b1132baf4a4dd3a7b63","name":"https://git.kernel.org/stable/c/3df451b65b6bc342d9291b1132baf4a4dd3a7b63","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/0d9450d006506d2af7016afd435b9c1a24985d02","name":"https://git.kernel.org/stable/c/0d9450d006506d2af7016afd435b9c1a24985d02","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/5ad9e4b0f1104f5dbfb41125c34bb30ea6dc7a94","name":"https://git.kernel.org/stable/c/5ad9e4b0f1104f5dbfb41125c34bb30ea6dc7a94","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/fe3b7bf598ba708431d531cfbb1035b8a463eed9","name":"https://git.kernel.org/stable/c/fe3b7bf598ba708431d531cfbb1035b8a463eed9","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-99657","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99657","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 3506ff69c3ec725b9c3e7f074fd2d265922f139a fe3b7bf598ba708431d531cfbb1035b8a463eed9 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 3506ff69c3ec725b9c3e7f074fd2d265922f139a 3df451b65b6bc342d9291b1132baf4a4dd3a7b63 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 3506ff69c3ec725b9c3e7f074fd2d265922f139a 0d9450d006506d2af7016afd435b9c1a24985d02 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 3506ff69c3ec725b9c3e7f074fd2d265922f139a 5ad9e4b0f1104f5dbfb41125c34bb30ea6dc7a94 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 5.5","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 5.5 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.118 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.64 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3.5 7.3.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.4-rc2 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"99657","cve":"CVE-2026-99657","epss":"0.001680000","percentile":"0.061980000","score_date":"2026-11-21","updated_at":"2026-11-22 00:14:17"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["mm/mmu_notifier.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"fe3b7bf598ba708431d531cfbb1035b8a463eed9","status":"affected","version":"3506ff69c3ec725b9c3e7f074fd2d265922f139a","versionType":"git"},{"lessThan":"3df451b65b6bc342d9291b1132baf4a4dd3a7b63","status":"affected","version":"3506ff69c3ec725b9c3e7f074fd2d265922f139a","versionType":"git"},{"lessThan":"0d9450d006506d2af7016afd435b9c1a24985d02","status":"affected","version":"3506ff69c3ec725b9c3e7f074fd2d265922f139a","versionType":"git"},{"lessThan":"5ad9e4b0f1104f5dbfb41125c34bb30ea6dc7a94","status":"affected","version":"3506ff69c3ec725b9c3e7f074fd2d265922f139a","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["mm/mmu_notifier.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"5.5"},{"lessThan":"5.5","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.118","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.64","versionType":"semver"},{"lessThanOrEqual":"7.3.*","status":"unaffected","version":"7.3.5","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.4-rc2","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.118","versionStartIncluding":"5.5","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.64","versionStartIncluding":"5.5","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3.5","versionStartIncluding":"5.5","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.4-rc2","versionStartIncluding":"5.5","vulnerable":true}],"negate":false,"operator":"OR"}]}],"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":{"baseScore":7.8,"baseSeverity":"HIGH","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"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."}]}],"providerMetadata":{"dateUpdated":"2026-11-22T11:09:28.093Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"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"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-99657","datePublished":"2026-11-20T05:50:09.250Z","dateReserved":"2026-09-25T10:25:14.427Z","dateUpdated":"2026-11-22T11:09:28.093Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-11-20 06:17:59","lastModifiedDate":"2026-11-22 11:17:04","problem_types":[],"metrics":{"cvssMetricV31":[{"source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","type":"Secondary","cvssData":{"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","attackVector":"LOCAL","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH"},"exploitabilityScore":1.8,"impactScore":5.9}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"99657","Ordinal":"1","Title":"mm/mmu_notifier: set ->mm only after mmgrab()","CVE":"CVE-2026-99657","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"99657","Ordinal":"1","NoteData":"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 ]","Type":"Description","Title":"mm/mmu_notifier: set ->mm only after mmgrab()"}]}}}