Freed kernel memory access via stale docg3 dereference
Published Jun 8, 2026 · Updated Jun 8, 2026
Use-after-free in the docg3 MTD driver in Linux Kernel releases starting at 5.8 allows local users to access freed kernel memory. In docg3_release(), doc_release_device() frees the cached docg3 structure inside the floor-removal loop before docg3->cascade->bch reads through that stale pointer. Reachability requires CAP_SYS_ADMIN to unbind the platform device through sysfs or CAP_SYS_MODULE to unload the driver, and published sources establish no consequence beyond the freed-memory access.
Summary
What happened
Use-after-free in the docg3 MTD driver in Linux Kernel releases starting at 5.8 allows local users to access freed kernel memory. In docg3_release(), doc_release_device() frees the cached docg3 structure inside the floor-removal loop before docg3->cascade->bch reads through that stale pointer. Reachability requires CAP_SYS_ADMIN to unbind the platform device through sysfs or CAP_SYS_MODULE to unload the driver, and published sources establish no consequence beyond the freed-memory access.
The record
- CVE
- CVE-2026-46285
- Published
- Jun 8, 2026
- Updated
- Jun 8, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-416
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jun 8, 2026CVE publishedPublication date reported by the CVE source.
- Jun 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.8
- Affected versionversion=c8ae3f744ddca0da164bcacee42d1d4b6fe7027d <16f6588a3b7a2a20d10ad9b766be74c60ba347cc
- Affected versionversion=c8ae3f744ddca0da164bcacee42d1d4b6fe7027d <2bf706fe7831b319f23a85b9728f961cfed40c3e
- Affected versionversion=c8ae3f744ddca0da164bcacee42d1d4b6fe7027d <8408655ec8344511667b61d8257dc59c80ee3391
- Affected versionversion=c8ae3f744ddca0da164bcacee42d1d4b6fe7027d <ca19808bc6fac7e29420d8508df569b346b3e339
- Affected versionversion=c8ae3f744ddca0da164bcacee42d1d4b6fe7027d <d26f8c361f751c188b7ebaf8189aa0258968fd98
- Affected versionversion=c8ae3f744ddca0da164bcacee42d1d4b6fe7027d <d49628d63d4e6bbc8a1621afb88e5fc901611bee
- Affected versionversion=c8ae3f744ddca0da164bcacee42d1d4b6fe7027d <d89044889ecd11b0c2f86663597246e9bdd25679
- Affected versionversion=c8ae3f744ddca0da164bcacee42d1d4b6fe7027d <f5d2ed4ed47d3906e2495a3537a48b127f497a17
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo