From: Greg KH <gregkh@linuxfoundation.org>
To: Delene Tchio Romuald <delenetchior1@gmail.com>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] staging: greybus: fix size_t underflow in cap_get_ims_certificate()
Date: Sun, 5 Apr 2026 10:00:50 +0200 [thread overview]
Message-ID: <2026040508-portable-natural-47ee@gregkh> (raw)
In-Reply-To: <20260404232242.68423-1-delenetchior1@gmail.com>
On Sun, Apr 05, 2026 at 12:22:42AM +0100, Delene Tchio Romuald wrote:
> In cap_get_ims_certificate(), the certificate size is computed as:
>
> *size = op->response->payload_size - sizeof(*response);
>
> Both operands are size_t (unsigned), so if a malformed Greybus module
> sends a response with payload_size smaller than sizeof(*response),
> the subtraction wraps to a very large value. The subsequent memcpy()
> then causes a heap buffer overflow.
How can you have a "malformed greybus module"?
Please fix your ai tool's threat model to be realistic :)
thanks,
greg k-h
prev parent reply other threads:[~2026-04-05 8:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-04 23:22 [PATCH] staging: greybus: fix size_t underflow in cap_get_ims_certificate() Delene Tchio Romuald
2026-04-05 8:00 ` Greg KH [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=2026040508-portable-natural-47ee@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=delenetchior1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=stable@vger.kernel.org \
/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