From: Greg KH <gregkh@linuxfoundation.org>
To: Ma Ke <make24@iscas.ac.cn>
Cc: ajd@linux.ibm.com, arnd@arndb.de, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, manoj@linux.vnet.ibm.com,
imunsie@au1.ibm.com, fbarrat@linux.ibm.com,
linuxppc-dev@lists.ozlabs.org, clombard@linux.vnet.ibm.com
Subject: Re: [PATCH v2] cxl: Fix possible null pointer dereference in read_handle()
Date: Wed, 10 Jul 2024 12:59:52 +0200 [thread overview]
Message-ID: <2024071052-squad-glorify-0830@gregkh> (raw)
In-Reply-To: <20240710103352.1890726-1-make24@iscas.ac.cn>
On Wed, Jul 10, 2024 at 06:33:52PM +0800, Ma Ke wrote:
> In read_handle(), of_get_address() may return NULL which is later
> dereferenced. Fix this by adding NULL check.
>
> Cc: stable@vger.kernel.org
> Fixes: 14baf4d9c739 ("cxl: Add guest-specific code")
> Signed-off-by: Ma Ke <make24@iscas.ac.cn>
> ---
> Changes in v2:
> - The potential vulnerability was discovered as follows: based on our
> customized static analysis tool, extract vulnerability features[1], and
> then match similar vulnerability features in this function.
You need to follow the rules outlined in
Documentation/process/researcher-guidelines.rst when doing stuff like
this. Otherwise all of your patches will have to be rejected.
Please fix up the changelog text of all of the patches you have
submitted recently to follow those rules.
thanks,
greg k-h
next prev parent reply other threads:[~2024-07-10 11:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 10:33 [PATCH v2] cxl: Fix possible null pointer dereference in read_handle() Ma Ke
2024-07-10 10:59 ` Greg KH [this message]
2024-07-10 13:05 ` [v2] " Markus Elfring
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=2024071052-squad-glorify-0830@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=ajd@linux.ibm.com \
--cc=arnd@arndb.de \
--cc=clombard@linux.vnet.ibm.com \
--cc=fbarrat@linux.ibm.com \
--cc=imunsie@au1.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=make24@iscas.ac.cn \
--cc=manoj@linux.vnet.ibm.com \
--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;
as well as URLs for NNTP newsgroup(s).