mtd: docg3: fix use-after-free in docg3_release()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ c8ae3f744ddca0da164bcacee42d1d4b6fe7027d · < d89044889ecd11b0c2f86663597246e9bdd25679| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
mtd: docg3: fix use-after-free in docg3_release()
In docg3_release(), the docg3 pointer is obtained from cascade->floors[0]->priv before the loop that calls doc_release_device() on each floor. doc_release_device() frees the docg3 struct via kfree(docg3) at line 1881. After the loop, docg3->cascade->bch dereferences the already-freed pointer.
Fix this by accessing cascade->bch directly, which is equivalent since docg3->cascade points back to the same cascade struct, and is already available as a local variable. This also removes the now-unused docg3 local variable.
From the CVE record · Linux
The Linux kernel’s mtd docg3 driver dereferences a freed pointer when releasing a device. This creates a use-after-free; the input does not establish how an attacker could trigger it or whether access, authentication, or user interaction is required.
Teams running Linux kernels with the mtd docg3 driver should check their versions; affected versions were not provided.