public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Frohl <rfrohl@suse.com>
To: cve@kernel.org, linux-kernel@vger.kernel.org,
	linux-cve-announce@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:26:54 +0100	[thread overview]
Message-ID: <27febaac-ebee-4e49-99ac-68dd9ceca60b@suse.com> (raw)
In-Reply-To: <20240229155245.1571576-37-lee@kernel.org>


[-- Attachment #1.1.1: Type: text/plain, Size: 2552 bytes --]

Hi all,

 > but let's just fix the build for now.

Reads like it is only a build fix, does it really need a CVE ?

Thanks,
Robert

On 29.02.24 16:52, 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.
> 
> The Linux kernel CVE team has assigned CVE-2023-52496 to this issue.
> 
> 
> Affected and fixed versions
> ===========================
> 
> 	Issue introduced in 6.6 with commit 19bfa9ebebb5 and fixed in 6.6.15 with commit 38c12f10990a
> 	Issue introduced in 6.6 with commit 19bfa9ebebb5 and fixed in 6.7.3 with commit 1168d6b79d2f
> 	Issue introduced in 6.6 with commit 19bfa9ebebb5 and fixed in 6.8-rc1 with commit a7d84a2e7663
> 
> Please see https://www.kernel.org or 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-2023-52496
> 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/maps/vmu-flash.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/38c12f10990ad6e63ddef2f20c1b066e5e4d34fd
> 	https://git.kernel.org/stable/c/1168d6b79d2fafb41299fbc1b528e20644c562a5
> 	https://git.kernel.org/stable/c/a7d84a2e7663bbe12394cc771107e04668ea313a
> 

-- 
Security Engineer, SUSE Software Solutions Germany GmbH, Frankenstraße 
146, 90461 Nürnberg, Germany, GF: Ivo Totev, Andrew McDonald, Werner 
Knoblich (HRB 36809, AG Nürnberg)
GPG: D29F 82AA 9FD5 9D6E 74B1  6370 089E DB3D 230A 2404

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 12035 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

  parent reply	other threads:[~2024-03-08 12:39 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 ` CVE-2023-52496: mtd: maps: vmu-flash: Fix the (mtd core) switch to ref counters Michal Hocko
2024-03-08 10:27   ` Greg KH
2024-03-08 10:26 ` Robert Frohl [this message]
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=27febaac-ebee-4e49-99ac-68dd9ceca60b@suse.com \
    --to=rfrohl@suse.com \
    --cc=cve@kernel.org \
    --cc=lee@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