From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: co <co+9d44b184bc8f410d@bugs.sh>
Cc: Bryan Tan <bryan-bt.tan@broadcom.com>,
Vishnu Dasa <vishnu.dasa@broadcom.com>,
Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
George Zhang <georgezhang@vmware.com>,
Dmitry Torokhov <dtor@vmware.com>, Andy king <acking@vmware.com>
Subject: Re: [BUG] drivers/misc: out-of-bounds in qp_memcpy_to_queue_iter()
Date: Thu, 27 Aug 2026 14:51:05 +0200 [thread overview]
Message-ID: <2026082744-tiptoeing-napkin-a2bc@gregkh> (raw)
In-Reply-To: <1wU0VjMckz7b5ly5tzcr7MbjZKdV9kTFjcc4@bugs.sh>
On Thu, Aug 27, 2026 at 12:42:26PM +0000, co wrote:
> We found a bug reachable in:
>
> path drivers/misc/vmw_vmci
> crash out-of-bounds in qp_memcpy_to_queue_iter()
> commit bd5f485f3f02 ("Merge tag 'soc-arm-7.3' of git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc")
>
> Config, environment, the sanitizer report and a C reproducer follow.
>
> == Notes ===============================================================
> If you patch the bug based on our artifacts, a tag would be
> appreciated:
>
> Reported-by: co+9d44b184bc8f410d@bugs.sh
>
> Everything in this mail is validated by the reproducer below.
>
> We also hold an LLM-generated root-cause analysis and a candidate
> patch. The patch passes an A/B test: the same reproducer panics the
> unpatched kernel and runs clean on the patched one. Neither has had
> human review, so both still require validation before you send or
> apply them. Available on:
>
> patch.diff https://bugs.sh/b/9d44b184bc8f410d/patch.diff
> report.md https://bugs.sh/b/9d44b184bc8f410d/report.md
Same here, please do not just send us random links, but rather patches
that you have verified work.
greg k-h
prev parent reply other threads:[~2026-08-27 12:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-27 12:42 co
2026-08-27 12:51 ` Greg Kroah-Hartman [this message]
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=2026082744-tiptoeing-napkin-a2bc@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=acking@vmware.com \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bryan-bt.tan@broadcom.com \
--cc=co+9d44b184bc8f410d@bugs.sh \
--cc=dtor@vmware.com \
--cc=georgezhang@vmware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vishnu.dasa@broadcom.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
all inboxes | Powered by JetHome®