# CVE-2026-46285: mtd: docg3: fix use-after-free in docg3_release()

> A use-after-free vulnerability in the Linux kernel's docg3 driver allows attackers to potentially execute arbitrary code or escalate privileges.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Jun 2026
- **Updated:** 14 Jun 2026
- **Also known as:** BELL-CVE-2026-46285, DEBIAN-CVE-2026-46285, GHSA-42x9-78r4-7gj5, ROOT-OS-DEBIAN-11-CVE-2026-46285, ROOT-OS-DEBIAN-12-CVE-2026-46285, UBUNTU-CVE-2026-46285

## What is CVE-2026-46285?

CVE-2026-46285 is a high-severity use after free vulnerability in Linux kernel, published on 8 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2026-46285?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2026-46285?

Apply the vendor's patch.

## Is CVE-2026-46285 being exploited?

There is no known exploitation of CVE-2026-46285 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-46285 and fix it if it is affected.

What it is: CVE-2026-46285 is a high-severity use after free vulnerability in Linux kernel, published on 8 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-46285 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-46285/ (Markdown: https://insights.sbomify.com/CVE-2026-46285/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-46285
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-46285
- OSV: https://osv.dev/vulnerability/CVE-2026-46285

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-46285/
Summaries are generated and may contain mistakes; the official description above is the record.