From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-46285: mtd: docg3: fix use-after-free in docg3_release()
Date: Mon, 8 Jun 2026 17:40:49 +0200 [thread overview]
Message-ID: <2026060843-CVE-2026-46285-0239@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
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.
The Linux kernel CVE team has assigned CVE-2026-46285 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.8 with commit c8ae3f744ddca0da164bcacee42d1d4b6fe7027d and fixed in 5.10.258 with commit 8408655ec8344511667b61d8257dc59c80ee3391
Issue introduced in 5.8 with commit c8ae3f744ddca0da164bcacee42d1d4b6fe7027d and fixed in 5.15.209 with commit f5d2ed4ed47d3906e2495a3537a48b127f497a17
Issue introduced in 5.8 with commit c8ae3f744ddca0da164bcacee42d1d4b6fe7027d and fixed in 6.1.175 with commit 2bf706fe7831b319f23a85b9728f961cfed40c3e
Issue introduced in 5.8 with commit c8ae3f744ddca0da164bcacee42d1d4b6fe7027d and fixed in 6.6.140 with commit d26f8c361f751c188b7ebaf8189aa0258968fd98
Issue introduced in 5.8 with commit c8ae3f744ddca0da164bcacee42d1d4b6fe7027d and fixed in 6.12.86 with commit 16f6588a3b7a2a20d10ad9b766be74c60ba347cc
Issue introduced in 5.8 with commit c8ae3f744ddca0da164bcacee42d1d4b6fe7027d and fixed in 6.18.27 with commit d89044889ecd11b0c2f86663597246e9bdd25679
Issue introduced in 5.8 with commit c8ae3f744ddca0da164bcacee42d1d4b6fe7027d and fixed in 7.0.4 with commit d49628d63d4e6bbc8a1621afb88e5fc901611bee
Issue introduced in 5.8 with commit c8ae3f744ddca0da164bcacee42d1d4b6fe7027d and fixed in 7.1-rc1 with commit ca19808bc6fac7e29420d8508df569b346b3e339
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-46285
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/mtd/devices/docg3.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/8408655ec8344511667b61d8257dc59c80ee3391
https://git.kernel.org/stable/c/f5d2ed4ed47d3906e2495a3537a48b127f497a17
https://git.kernel.org/stable/c/2bf706fe7831b319f23a85b9728f961cfed40c3e
https://git.kernel.org/stable/c/d26f8c361f751c188b7ebaf8189aa0258968fd98
https://git.kernel.org/stable/c/16f6588a3b7a2a20d10ad9b766be74c60ba347cc
https://git.kernel.org/stable/c/d89044889ecd11b0c2f86663597246e9bdd25679
https://git.kernel.org/stable/c/d49628d63d4e6bbc8a1621afb88e5fc901611bee
https://git.kernel.org/stable/c/ca19808bc6fac7e29420d8508df569b346b3e339
reply other threads:[~2026-06-08 15:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026060843-CVE-2026-46285-0239@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox