From: Greg KH <gregkh@linuxfoundation.org>
To: Berkant Koc <me@berkoc.com>
Cc: security@kernel.org, Zack Rusin <zack.rusin@broadcom.com>,
bcm-kernel-feedback-list@broadcom.com,
dri-devel@lists.freedesktop.org, Daniel Vetter <daniel@ffwll.ch>,
David Airlie <airlied@gmail.com>,
Thomas Zimmermann <tzimmermann@suse.de>
Subject: Re: [REPORT] drm/vmwgfx: vmw_cmd_draw header.size lower-bound missing - guest-local OOB-read/write
Date: Sun, 17 May 2026 15:37:08 +0200 [thread overview]
Message-ID: <2026051743-genre-cacti-bdf3@gregkh> (raw)
In-Reply-To: <20260517-vmwgfx-uaf-report@berkoc.com>
On Sun, May 17, 2026 at 03:00:00PM +0200, Berkant Koc wrote:
> Happy to follow your standard timeline per Documentation/process/security-bugs.rst
> (typically <=7 days post-fix-merge).
You sent this to a public list, there is no "timeline" needed.
Just submit a fix for this now please.
thanks,
greg k-h
next prev parent reply other threads:[~2026-05-17 13:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-17 13:00 [REPORT] drm/vmwgfx: vmw_cmd_draw header.size lower-bound missing - guest-local OOB-read/write Berkant Koc
2026-05-17 13:37 ` Greg KH [this message]
2026-05-17 13:05 ` [PATCH] drm/vmwgfx: validate execbuf header.size lower bound Berkant Koc
2026-05-17 23:23 ` Zack Rusin
2026-05-18 0:56 ` Berkant Koc
2026-05-18 6:07 ` Claude review: " Claude Code Review Bot
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=2026051743-genre-cacti-bdf3@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=airlied@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=me@berkoc.com \
--cc=security@kernel.org \
--cc=tzimmermann@suse.de \
--cc=zack.rusin@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