From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Siddh Raman Pant <siddh.raman.pant@oracle.com>
Cc: "cve@kernel.org" <cve@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: CVE-2022-49267: mmc: core: use sysfs_emit() instead of sprintf()
Date: Tue, 24 Mar 2026 09:34:17 +0100 [thread overview]
Message-ID: <2026032404-cling-croon-dd5d@gregkh> (raw)
In-Reply-To: <9f282e5db77c382bff8e33b74a1404f7c680c2da.camel@oracle.com>
On Tue, Mar 24, 2026 at 07:42:23AM +0000, Siddh Raman Pant wrote:
> On Wed, 26 Feb 2025 02:57:52 +0100, Greg Kroah-Hartman wrote:
> > In the Linux kernel, the following vulnerability has been resolved:
> >
> > mmc: core: use sysfs_emit() instead of sprintf()
> >
> > sprintf() (still used in the MMC core for the sysfs output) is vulnerable
> > to the buffer overflow. Use the new-fangled sysfs_emit() instead.
> >
> > Found by Linux Verification Center (linuxtesting.org) with the SVACE static
> > analysis tool.
> >
> > The Linux kernel CVE team has assigned CVE-2022-49267 to this issue.
>
> What overflow does this actually fix? I think this is a defensive patch.
>
> In fact, you asked the same question earlier during stable backport
> which apparently got no reply:
> https://lore.kernel.org/all/2025121205-wool-undesired-0609@gregkh/
You are correct, this is now rejected, thanks for the review.
greg k-h
prev parent reply other threads:[~2026-03-24 8:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2025022629-CVE-2022-49267-b3ac@gregkh>
2026-03-24 7:42 ` Siddh Raman Pant
2026-03-24 8:34 ` gregkh [this message]
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=2026032404-cling-croon-dd5d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=siddh.raman.pant@oracle.com \
/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
all inboxes | Powered by JetHome®