dbcve.org
Linux KernelOperating system · Linux

CVE-2026-46285

HIGH · 7.8 CVSS v3.1 Published 2026-06-08
Fix available
A fix is available. Upgrade to 5.10.258 / 5.15.209 or later.
See remediation →
80/100
Remediation priority · High
Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Use-after-free vulnerability in Linux kernel's MTD docg3 driver where a docg3 pointer obtained from cascade->floors[0]->priv is freed via kfree() inside a loop by doc_release_device(), but the code then attempts to access docg3->cascade->bch after the pointer has already been freed.

MitigationApply the kernel patch to access cascade->bch directly instead of through the freed docg3 pointer, which removes the now-unnecessary docg3 local variable.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 5.8, < 5.10.258>= 5.11, < 5.15.209>= 5.16, < 6.1.175>= 6.2, < 6.6.140>= 6.7, < 6.12.86>= 6.13, < 6.18.27>= 6.19, < 7.0.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check kernel version
    Run `uname -r` or read `/proc/version` to get the running kernel version
    Affected if The kernel version falls within any of these ranges: >=5.8 and <5.10.258, >=5.11 and <5.15.209, >=5.16 and <6.1.175, >=6.2 and <6.6.140, >=6.7 and <6.12.86, >=6.13 and <6.18.27, >=6.19 and <7.0.4
  2. Determine if docg3 driver is loaded
    Run `lsmod | grep docg3` or check `/proc/modules` for the docg3 module
    Affected if The docg3 module is currently loaded in memory (indicating active use of DiskOnChip hardware)
  3. Check if docg3 is compiled into the kernel
    Check the kernel config or boot logs for CONFIG_DOCG3=y, or search System.map for docg3_release function
    Affected if The docg3 driver is built-in to the kernel (not a module) and the kernel is in the affected version range
  4. Verify DiskOnChip hardware presence
    Check dmesg for DOC Millennium or DiskOnChip device initialization messages, or check /proc/bus/pci or lsdev for relevant hardware
    Affected if DiskOnChip hardware is present and the kernel version is in the affected range (the vulnerable code path requires this specific hardware)
  5. Identify the vulnerable code path
    Review the docg3_release() function in the kernel source for the specific pattern: kfree(docg3) followed by dereference of docg3->cascade->bch. In a live system, this would manifest as a kernel panic if triggered.
    Affected if The vulnerable code pattern exists (automatic if kernel version is in affected range and docg3 driver is in use)

You are affected if you are running a kernel version within the affected ranges AND the docg3 driver is loaded or built-in AND DiskOnChip hardware is present, as only then would the vulnerable code path in docg3_release() be exercised.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.10.258 / 5.15.209 / 6.1.175 or later
Fixed in 5.10.2585.15.2096.1.175
Vendor patch git.kernel.org →
Interim mitigation

Apply the kernel patch to access cascade->bch directly instead of through the freed docg3 pointer, which removes the now-unnecessary docg3 local variable.

Recommended fix High confidence

Upgrade to kernel 5.10.258, 5.15.209, 6.1.175, or 6.6.140 (whichever is the next stable release for your branch)

  1. Identify the currently running Linux kernel version using `uname -r`
  2. Check which affected version range your kernel falls into (5.8-5.10.x, 5.11-5.15.x, 5.16-6.1.x, or 6.2-6.6.x)
  3. Obtain and install the appropriate fixed kernel version: 5.10.258, 5.15.209, 6.1.175, or 6.6.140 respectively
  4. Reboot the system to load the patched kernel
  5. Verify the fix is applied by checking the docg3 driver code or kernel release notes
Caveat Kernel upgrades may require rebuild of out-of-tree modules; ensure driver compatibility before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,340
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,144.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46285 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-46285 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data