The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Zhenhao Wan <whi4ed0g@gmail.com>, Dan Williams <djbw@kernel.org>
Cc: Davidlohr Bueso <dave@stgolabs.net>,
	Jonathan Cameron <jic23@kernel.org>,
	Dave Jiang <dave.jiang@intel.com>,
	Alison Schofield <alison.schofield@intel.com>,
	Vishal Verma <vishal.l.verma@intel.com>,
	Ira Weiny <ira.weiny@intel.com>, Li Ming <ming.li@zohomail.com>,
	linux-cxl@vger.kernel.org, linux-kernel@vger.kernel.org,
	Yuhao Jiang <danisjiang@gmail.com>
Subject: Re: [PATCH] cxl/features: bound fwctl command payload to the input buffer
Date: Mon, 6 Jul 2026 12:54:14 -0300	[thread overview]
Message-ID: <20260706155414.GA118978@ziepe.ca> (raw)
In-Reply-To: <20260620-cxl-fwctl-oob-v1-1-5758e34d784a@gmail.com>

On Sat, Jun 20, 2026 at 12:33:15PM +0800, Zhenhao Wan wrote:
> fwctl_cmd_rpc() copies cmd->in_len bytes into inbuf = kvzalloc(cmd->in_len)
> and passes inbuf and in_len to ->fw_rpc(). The CXL callback cxlctl_fw_rpc()
> ignores in_len and never checks the user-controlled op_size against it.
> 
> cxlctl_set_feature() bounds op_size only from below
> (op_size <= sizeof(feat_in->hdr)) and then reads op_size - sizeof(hdr)
> bytes from feat_in->feat_data via cxl_set_feature(). With a small in_len
> and a large op_size the first memcpy() already reads past the
> kvzalloc(in_len) buffer; the out-of-bounds bytes are placed in the mailbox
> payload and sent to the device, and a large enough op_size can walk into
> unmapped memory and oops the kernel. The Get paths pin op_size to a fixed
> size but likewise read the input struct without checking in_len.
> 
> Reject, at the single dispatch point, any request whose fixed header plus
> op_size does not fit in the copied-in buffer. The lower-bound test guards
> the subtraction and ensures op_size was copied in before it is read.
> 
> Fixes: eb5dfcb9e36d ("cxl: Add support to handle user feature commands for set feature")
> Reported-by: Yuhao Jiang <danisjiang@gmail.com>
> Signed-off-by: Zhenhao Wan <whi4ed0g@gmail.com>
> ---
>  drivers/cxl/core/features.c | 8 +++++++-
>  1 file changed, 7 insertions(+), 1 deletion(-)

Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>

CXL folks, you will pick this up?

I think it should be cc stable too

Jason

  reply	other threads:[~2026-07-06 15:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-20  4:33 [PATCH] cxl/features: bound fwctl command payload to the input buffer Zhenhao Wan
2026-07-06 15:54 ` Jason Gunthorpe [this message]
2026-07-06 18:16   ` Dave Jiang
2026-07-06 20:28 ` Dave Jiang

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=20260706155414.GA118978@ziepe.ca \
    --to=jgg@ziepe.ca \
    --cc=alison.schofield@intel.com \
    --cc=danisjiang@gmail.com \
    --cc=dave.jiang@intel.com \
    --cc=dave@stgolabs.net \
    --cc=djbw@kernel.org \
    --cc=ira.weiny@intel.com \
    --cc=jic23@kernel.org \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ming.li@zohomail.com \
    --cc=vishal.l.verma@intel.com \
    --cc=whi4ed0g@gmail.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