From: Bart Van Assche <bvanassche@acm.org>
To: jackysliu <1972843537@qq.com>
Cc: James.Bottomley@HansenPartnership.com,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
martin.petersen@oracle.com
Subject: Re: [PATCH] scsi: fix out of bounds error in /drivers/scsi
Date: Wed, 18 Jun 2025 08:26:14 -0700 [thread overview]
Message-ID: <dc972e6f-b846-4445-a347-c6fbf72ba429@acm.org> (raw)
In-Reply-To: <tencent_D9A0F9052526AD09F7FF76DD5F2529FDDD05@qq.com>
On 6/17/25 11:31 PM, jackysliu wrote:
> Can I know what kind of impact this vulnerability will have?
The worst possible impact I see is that the Linux kernel would decide
that RSCS is supported although the device doesn't support it. This
could cause sd_read_io_hints() to print incorrect information. The
following message could be printed when it should not be printed:
"Unexpected: RSCS has been set and the permanent stream count is %u\n"
> And is it possible to get a cve number?
You are asking the wrong person. I don't know how to get a CVE number.
Bart.
next prev parent reply other threads:[~2025-06-18 15:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-17 9:03 [PATCH] scsi: fix out of bounds error in /drivers/scsi jackysliu
2025-06-17 20:44 ` Bart Van Assche
2025-06-18 6:31 ` jackysliu
2025-06-18 15:26 ` Bart Van Assche [this message]
2025-06-30 8:21 ` jackysliu
2025-06-19 4:03 ` [PATCH v2] " jackysliu
2025-07-15 7:56 ` [PATCH v2] usb: gadget: functioni: Fix a oob problem in rndis jackysliu
2025-07-15 13:00 ` [PATCH v2] scsi: fix out of bounds error in /drivers/scsi Bart Van Assche
2025-07-15 15:36 ` Krzysztof Kozlowski
2025-07-15 16:57 ` Bart Van Assche
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=dc972e6f-b846-4445-a347-c6fbf72ba429@acm.org \
--to=bvanassche@acm.org \
--cc=1972843537@qq.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@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.