drm/nouveau/dmem: fix callocated underflow on large folio split
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 0163b92946d0a7c816f619c57a4d9867954dd106 and Kernel c2256c044a1df39c8aad4dd2d6f709b2533e2d7a.
In the Linux kernel, the following vulnerability has been resolved: drm/nouveau/dmem: fix callocated underflow on large folio split nouveau_dmem_folio_free() drops chunk->callocated once per freed folio, while a large (compound) device-private folio is only counted once when it is allocated. When such a folio is split, the mm core invokes ->folio_split() (nouveau_dmem_folio_split()) once for each new sub-folio, but the hook only fixes up the sub-folio metadata and leaves chunk->callocated unchanged. Each resulting sub-folio is later freed separately, so after a split the single allocation (+1) is met by N frees (-N), leaving chunk->callocated short by N-1. On the first split/free cycle it underflows: WARN_ON(!chunk->callocated) fires, the unsigned counter wraps and never returns to zero, so the chunk can no longer be reclaimed (nouveau_dmem_fini() also warns on the leaked count). Account for the new sub-folio in the split hook, under the same lock as nouveau_dmem_folio_free(), so the count stays balanced.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.19, >=c3228747107705d47c7e9a03598a434a0380cb73 <0163b92946d0a7c816f619c57a4d9867954dd106, >=c3228747107705d47c7e9a03598a434a0380cb73 <c2256c044a1df39c8aad4dd2d6f709b2533e2d7a | 0163b92946d0a7c816f619c57a4d9867954dd106, c2256c044a1df39c8aad4dd2d6f709b2533e2d7a |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket