Linux Kernel: Use-After-Free (CVE-2026-46285)
Published Last modified Sources: SUSE, Debian LTS, Ubuntu, BSI, Msrc Update Guide, CVE.org
What is affected, what to do
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.
Update Linux Kernel to version 5.10.258, Linux Kernel to version 5.15.209, Linux Kernel to version 6.1.175.
- Affected
- Linux Kernel
lt 5.8..5.10.258 - Linux Kernel
lt 5.11..5.15.209 - Linux Kernel
lt 5.16..6.1.175 - Linux Kernel
lt 6.2..6.6.140 - Linux Kernel
lt 6.7..6.12.86 - Linux Kernel
lt 6.13..6.18.27 - Linux Kernel
lt 6.19..7.0.4
- Linux Kernel
- Fixed in
- Linux Kernel
5.10.258 - Linux Kernel
5.15.209 - Linux Kernel
6.1.175 - Linux Kernel
6.6.140 - Linux Kernel
6.12.86 - Linux Kernel
6.18.27 - Linux Kernel
7.0.4 - Linux Kernel
7.1
- Linux Kernel
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
7.1
Priority
XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.
Source: NVD, CVSS v3
7.1
CVSS v3
Severity High on the scale from 0 to 10.
Source: SUSE, Debian LTS, Ubuntu, BSI, Msrc Update Guide, CVE.org
0.1 %
EPSS score
Low — model estimates < 1% exploitation likelihood.
Source: FIRST EPSS, percentile 2.2
Show all metrics
- Severity
- High
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 54.15 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
XIEM Effective CVSS
XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.
Read in glossary- 7.1 Methodology
CVSS v3
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 7.1
EPSS score
The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.
Read in glossary- 0.1 %
- Low — model estimates < 1% exploitation likelihood.
EPSS percentile
The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.
Read in glossary- 2.2
- Low — this CVE sits in the lower 10% of all CVEs scored today.
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
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.
Source: suse_csaf, Debian LTS Advisories, Ubuntu Security Notices, BSI WID Portal, BSI CSAF, Microsoft Security Update Guide, cvelistv5, NVD (NIST), CVE.org (MITRE)
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Affected versions | Fixed in | ||
|---|---|---|---|
| Linux | Linux |
|
|
Vendors and products
Affected operating systems
| Linux | debian | linux | bookworm |
| Linux | debian | linux | bullseye |
| Linux | debian | linux-6.1 | bullseye |
| Linux | ubuntu | linux-raspi | jammy |
| Linux | linux | linux_kernel | — |
References & sources
- git.kernel.orgstable/c/8408655ec8344511667b61d8257dc59c80ee3391
- git.kernel.orgstable/c/f5d2ed4ed47d3906e2495a3537a48b127f497a17
- git.kernel.orgstable/c/2bf706fe7831b319f23a85b9728f961cfed40c3e
- git.kernel.orgstable/c/d26f8c361f751c188b7ebaf8189aa0258968fd98
- git.kernel.orgstable/c/16f6588a3b7a2a20d10ad9b766be74c60ba347cc
- git.kernel.orgstable/c/d89044889ecd11b0c2f86663597246e9bdd25679
- git.kernel.orgstable/c/d49628d63d4e6bbc8a1621afb88e5fc901611bee
- git.kernel.orgstable/c/ca19808bc6fac7e29420d8508df569b346b3e339
Changes to this CVE
Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).
ReceivedLinux
Description added or changed
New 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
and 4 more references
Show 9 original changes
Individual changes of this event as published by NVD Type Action Before After Description added —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.Reference added —https://git.kernel.org/stable/c/16f6588a3b7a2a20d10ad9b766be74c60ba347ccReference added —https://git.kernel.org/stable/c/2bf706fe7831b319f23a85b9728f961cfed40c3eReference added —https://git.kernel.org/stable/c/8408655ec8344511667b61d8257dc59c80ee3391Reference added —https://git.kernel.org/stable/c/ca19808bc6fac7e29420d8508df569b346b3e339Reference added —https://git.kernel.org/stable/c/d26f8c361f751c188b7ebaf8189aa0258968fd98Reference added —https://git.kernel.org/stable/c/d49628d63d4e6bbc8a1621afb88e5fc901611beeReference added —https://git.kernel.org/stable/c/d89044889ecd11b0c2f86663597246e9bdd25679Reference added —https://git.kernel.org/stable/c/f5d2ed4ed47d3906e2495a3537a48b127f497a17Source identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
One NVD translation into another language is hidden.
Linked advisories
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2026-46285"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-46285.svg?lang=en" alt="CVE-2026-46285 – NEOSEC Intel" height="20"></a>