From: Michal Hocko <mhocko@suse.com>
To: cve@kernel.org, linux-kernel@vger.kernel.org
Cc: Lee Jones <lee@kernel.org>
Subject: Re: CVE-2023-52496: mtd: maps: vmu-flash: Fix the (mtd core) switch to ref counters
Date: Fri, 8 Mar 2024 11:08:51 +0100 [thread overview]
Message-ID: <Zerjs8hlMJOXt0Sv@tiehlicka> (raw)
In-Reply-To: <20240229155245.1571576-37-lee@kernel.org>
On Thu 29-02-24 15:52:56, Lee Jones wrote:
> Description
> ===========
>
> In the Linux kernel, the following vulnerability has been resolved:
>
> mtd: maps: vmu-flash: Fix the (mtd core) switch to ref counters
>
> While switching to ref counters for track mtd devices use, the vmu-flash
> driver was forgotten. The reason for reading the ref counter seems
> debatable, but let's just fix the build for now.
Do we really consider build fixes as CVE?
--
Michal Hocko
SUSE Labs
next parent reply other threads:[~2024-03-08 10:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240229155245.1571576-37-lee@kernel.org>
2024-03-08 10:08 ` Michal Hocko [this message]
2024-03-08 10:27 ` CVE-2023-52496: mtd: maps: vmu-flash: Fix the (mtd core) switch to ref counters Greg KH
2024-03-08 10:26 ` Robert Frohl
2024-03-08 16:02 ` Greg KH
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=Zerjs8hlMJOXt0Sv@tiehlicka \
--to=mhocko@suse.com \
--cc=cve@kernel.org \
--cc=lee@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;
as well as URLs for NNTP newsgroup(s).