The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: cve@kernel.org, linux-kernel@vger.kernel.org,
	Vegard Nossum <vegard.nossum@oracle.com>
Subject: Re: CVE-2024-26929: scsi: qla2xxx: Fix double free of fcport
Date: Sun, 29 Dec 2024 18:17:14 +0530	[thread overview]
Message-ID: <a28ac5fe-932e-4d5c-a0c1-93d00da8ccd7@oracle.com> (raw)
In-Reply-To: <2024122942-blissful-framing-214e@gregkh>

Hi Greg,

On 29/12/24 12:54, Greg Kroah-Hartman wrote:
...
>>
>>
>> I think the broken commit/vuln commit is: 4895009c4bb7 ("scsi: qla2xxx:
>> Prevent command send on chip reset") and this is only present in stable
>> kernels newer than (>=) 5.15.y.
>>
>> Is it worth putting the vuln commit information if we find out what the
>> broken/vuln commit is while trying to backport it to older stable kernels ?
> 
> Yes it is, our tools provide for this, see:
> 	https://git.kernel.org/pub/scm/linux/security/vulns.git/tree/cve/schema#n69
> for how to do it (i.e. give us a git id and we can add a .vulnerable
> file so the tools pick it up properly, or send us a patch for that!)
> 
> Do you want to send a patch for this, or do you need us to?
> 

I will send a patch, thanks for the guidance.


Thanks,
Harshit

> thanks,
> 
> greg k-h


  reply	other threads:[~2024-12-29 12:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2024050122-CVE-2024-26929-07f0@gregkh>
2024-12-28 18:58 ` CVE-2024-26929: scsi: qla2xxx: Fix double free of fcport Harshit Mogalapalli
2024-12-29  7:24   ` Greg Kroah-Hartman
2024-12-29 12:47     ` Harshit Mogalapalli [this message]
2024-12-30 14:19       ` Greg Kroah-Hartman

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=a28ac5fe-932e-4d5c-a0c1-93d00da8ccd7@oracle.com \
    --to=harshit.m.mogalapalli@oracle.com \
    --cc=cve@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox