mm/mmu_notifier: set ->mm only after mmgrab()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel fe3b7bf598ba708431d531cfbb1035b8a463eed9, Kernel 0d9450d006506d2af7016afd435b9c1a24985d02, Kernel 3df451b65b6bc342d9291b1132baf4a4dd3a7b63 and 4 more.
In the Linux kernel, the following vulnerability has been resolved: mm/mmu_notifier: set ->mm only after mmgrab() Radeon uses a non-NULL notifier->mm to decide whether to call mmu_interval_notifier_remove() when freeing a buffer object. __mmu_interval_notifier_insert() sets ->mm before validating the range, so a wrapping userptr range can leave ->mm set after insertion fails. Cleanup then tries to remove an unregistered notifier for which no mm reference was acquired. Set ->mm only after mmgrab(), once insertion can no longer fail. While we could fix radeon's code instead, setting ->mm on success only makes the code more robust. Fix generated by an LLM and sent by Chris Mason in private. [ david: simplify description ]
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=3506ff69c3ec725b9c3e7f074fd2d265922f139a <fe3b7bf598ba708431d531cfbb1035b8a463eed9, >=3506ff69c3ec725b9c3e7f074fd2d265922f139a <0d9450d006506d2af7016afd435b9c1a24985d02, >=3506ff69c3ec725b9c3e7f074fd2d265922f139a <3df451b65b6bc342d9291b1132baf4a4dd3a7b63, >=3506ff69c3ec725b9c3e7f074fd2d265922f139a <5ad9e4b0f1104f5dbfb41125c34bb30ea6dc7a94, =5.5 | fe3b7bf598ba708431d531cfbb1035b8a463eed9, 0d9450d006506d2af7016afd435b9c1a24985d02, 3df451b65b6bc342d9291b1132baf4a4dd3a7b63, 5ad9e4b0f1104f5dbfb41125c34bb30ea6dc7a94 |
| linux-kernel: Kernel | >=6.13.0 <6.18.64, >=6.19.0 <7.3.5, >=5.5.0 <6.12.118 | 6.18.64, 7.3.5, 6.12.118 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket