From: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: cve@kernel.org, vegard.nossum@oracle.com,
linux-kernel@vger.kernel.org,
Martin Petersen <martin.petersen@oracle.com>,
skashyap@marvell.com, qutran@marvell.com,
Himanshu Madhani <himanshu.madhani@oracle.com>
Subject: Re: [PATCH] CVE-2024-26929: Add vulnerable commit information
Date: Fri, 3 Jan 2025 13:53:19 +0530 [thread overview]
Message-ID: <29eba901-ef67-41e6-b2a5-3f653861874d@oracle.com> (raw)
In-Reply-To: <2025010329-kelp-chump-18ac@gregkh>
Hi Greg,
+CC qla2xxx experts
On 03/01/25 12:22, Greg KH wrote:
> On Thu, Jan 02, 2025 at 12:48:26PM -0800, Harshit Mogalapalli wrote:
>> This CVE fixes: 4895009c4bb7 ("scsi: qla2xxx: Prevent command send on
>> chip reset") so add that information in vulnerable commit.
>>
>> Signed-off-by: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
>> ---
>> cve/published/2024/CVE-2024-26929.vulnerable | 1 +
>> 1 file changed, 1 insertion(+)
>> create mode 100644 cve/published/2024/CVE-2024-26929.vulnerable
>>
>> diff --git a/cve/published/2024/CVE-2024-26929.vulnerable b/cve/published/2024/CVE-2024-26929.vulnerable
>> new file mode 100644
>> index 000000000000..b946d6f2786b
>> --- /dev/null
>> +++ b/cve/published/2024/CVE-2024-26929.vulnerable
>> @@ -0,0 +1 @@
>> +4895009c4bb72f71f2e682f1e7d2c2d96e482087
>> --
>> 2.46.0
>>
>>
>
> Ok, by doing this it means this whole CVE needs to be rejected as the
> vulnerable commit never shows up in a a release on its own. Are you
> sure about this? If so, let's just reject the CVE.
>
My reasoning is as follows:
The CVE fix commit: 82f522ae0d97 ("scsi: qla2xxx: Fix double free of
fcport") states,
""
Remove one of the free calls and add check for valid fcport. Also use
function qla2x00_free_fcport() instead of kfree().
@@ -2784,7 +2786,6 @@ qla24xx_els_dcmd_iocb(scsi_qla_host_t *vha, int
els_opcode,
fcport->d_id.b.area, fcport->d_id.b.al_pa);
wait_for_completion(&elsio->u.els_logo.comp);
- qla2x00_free_fcport(fcport);
/* ref: INIT */
kref_put(&sp->cmd_kref, qla2x00_sp_release);
""
and the same function has this sp->free = qla2x00_els_dcmd_sp_free; so
fcport is freed twice.
and this qla2xxx_free_fcport(fcport) in the success path is added by
commit: 4895009c4bb7 ("scsi: qla2xxx: Prevent command send on chip
reset") so I think this commit introduced the problem.
Thanks,
Harshit
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2025-01-03 8:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-02 20:48 [PATCH] CVE-2024-26929: Add vulnerable commit information Harshit Mogalapalli
2025-01-03 6:52 ` Greg KH
2025-01-03 8:23 ` Harshit Mogalapalli [this message]
2025-01-06 16:25 ` 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=29eba901-ef67-41e6-b2a5-3f653861874d@oracle.com \
--to=harshit.m.mogalapalli@oracle.com \
--cc=cve@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=himanshu.madhani@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=qutran@marvell.com \
--cc=skashyap@marvell.com \
--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