All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
To: Greg KH <gregkh@linuxfoundation.org>
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 14:18:02 +0530	[thread overview]
Message-ID: <2045efe8-9e32-4a38-a7a7-799cca1dca89@oracle.com> (raw)
In-Reply-To: <2025031043-parcel-uncharted-0d8c@gregkh>

Hi Greg,

On 10/03/25 13:07, Greg KH wrote:
...
>> 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?
> 

Ah yes, I agree, thanks for explaining.

...
>> 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.
>

Thanks a lot!


Regards,
Harshit

> greg k-h


  reply	other threads:[~2025-03-10  8:48 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
2025-03-10  8:48   ` Harshit Mogalapalli [this message]
  -- 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=2045efe8-9e32-4a38-a7a7-799cca1dca89@oracle.com \
    --to=harshit.m.mogalapalli@oracle.com \
    --cc=Jesse.Zhang@amd.com \
    --cc=adobriyan@gmail.com \
    --cc=andypma@tencent.com \
    --cc=cve@kernel.org \
    --cc=forst@pen.gy \
    --cc=gregkh@linuxfoundation.org \
    --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.