What’s Vulnerable › Vulnerabilities
CVE-2026-46285: mtd: docg3: fix use-after-free in docg3_release()
- Severity: high (CVSS 7.8 v3.1)
- Exploited in the wild: not listed in CISA KEV
- EPSS: 0.1% probability of exploitation in the next 30 days
- Public exploit or detection template: none known
- Published: 2026-06-08 · updated 2026-07-23
- Weakness: CWE-416
Description
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.
Affected products
- Linux kernel: from 5.8 before 5.10.258; from 5.11 before 5.15.209; from 5.16 before 6.1.175; from 6.2 before 6.6.140; from 6.7 before 6.12.86; from 6.13 before 6.18.27 — fixed in 5.10.258, 5.15.209, 6.1.175, 6.12.86, 6.18.27, 6.6.140
How to fix
Upgrade to a fixed version: Linux kernel 5.10.258, 5.15.209, 6.1.175, 6.12.86. Check the vendor advisory for mitigations.
References
- https://git.kernel.org/stable/c/16f6588a3b7a2a20d10ad9b766be74c60ba347cc
- https://git.kernel.org/stable/c/2bf706fe7831b319f23a85b9728f961cfed40c3e
- https://git.kernel.org/stable/c/8408655ec8344511667b61d8257dc59c80ee3391
- https://git.kernel.org/stable/c/ca19808bc6fac7e29420d8508df569b346b3e339
- https://git.kernel.org/stable/c/d26f8c361f751c188b7ebaf8189aa0258968fd98
- https://git.kernel.org/stable/c/d49628d63d4e6bbc8a1621afb88e5fc901611bee
- https://git.kernel.org/stable/c/d89044889ecd11b0c2f86663597246e9bdd25679
- https://git.kernel.org/stable/c/f5d2ed4ed47d3906e2495a3537a48b127f497a17
Get alerted when CVE-2026-46285 or the next vulnerability affects your stack