From: Greg KH <gregkh@linuxfoundation.org>
To: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
Cc: cve@kernel.org, andypma@tencent.com, Jesse.Zhang@amd.com,
forst@pen.gy, adobriyan@gmail.com, vegard.nossum@oracle.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add vulnerable commits for few CVEs
Date: Mon, 10 Mar 2025 08:37:28 +0100 [thread overview]
Message-ID: <2025031043-parcel-uncharted-0d8c@gregkh> (raw)
In-Reply-To: <20250310062349.206687-1-harshit.m.mogalapalli@oracle.com>
On Sun, Mar 09, 2025 at 11:23:49PM -0700, Harshit Mogalapalli wrote:
> CVE-2024-49994: block: fix integer overflow in BLKSECDISCARD
> — Fixes: 44abff2c0b97 ("block: decouple REQ_OP_SECURE_ERASE from REQ_OP_DISCARD")
> Reason: The overflowing addition in blk_ioctl_secure_erase() is added in
> above mentioned broken commit.
>
> CVE-2024-46861 kernel: usbnet: ipheth: do not stop RX on failing RX callback
> — Fixes: a2d274c62e44 ("usbnet: ipheth: add CDC NCM support")
> Reason: dev->rcvbulk_callback() was added in the broken commit, and the
> CVE fix is to remove the return statement on failure.
> Note: The CVE fix is preventing driver to stop on non-critical failures
> -- I think this shouldn't be a CVE
It's it a denial of service if the driver does not work for normal
issues that can be triggered?
> CVE-2024-46819 kernel: drm/amdgpu: the warning dereferencing obj for nbio_v7_4
> - Fixes: 28f87950d935 ("drm/amdgpu: clear ras controller status registers when interrupt occurs")
> Reason: ras_manager was first brought into usage in the above mentioned
> broken commit.
>
> CVE-2024-40997 kernel: cpufreq: amd-pstate: fix memory leak on CPU EPP exit
> — Fixes: ffa5096a7c33 ("cpufreq: amd-pstate: implement Pstate EPP support for the AMD processors")
> Reason: memory allocation in amd_pstate_epp_cpu_init() with kzalloc is
> added in the above mentioned broken commit.
>
> Signed-off-by: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
Thanks for all of these, I'll go apply this now and update the database
entries.
greg k-h
next prev parent reply other threads:[~2025-03-10 7:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-10 6:23 [PATCH] Add vulnerable commits for few CVEs Harshit Mogalapalli
2025-03-10 7:37 ` Greg KH [this message]
2025-03-10 8:48 ` Harshit Mogalapalli
-- strict thread matches above, loose matches on Subject: below --
2025-05-10 16:10 Harshit Mogalapalli
2025-05-10 16:47 ` Greg KH
2025-05-10 16:56 ` Harshit Mogalapalli
2025-01-20 17:10 Harshit Mogalapalli
2025-01-21 10:56 ` 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=2025031043-parcel-uncharted-0d8c@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Jesse.Zhang@amd.com \
--cc=adobriyan@gmail.com \
--cc=andypma@tencent.com \
--cc=cve@kernel.org \
--cc=forst@pen.gy \
--cc=harshit.m.mogalapalli@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vegard.nossum@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.