mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: make24@iscas.ac.cn, linuxppc-dev@lists.ozlabs.org,
	kernel-janitors@vger.kernel.org
Cc: stable@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Aleksandr Mishin <amishin@t-argos.ru>,
	Andrew Donnellan <ajd@linux.ibm.com>,
	Arnd Bergmann <arnd@arndb.de>,
	Christophe Lombard <clombard@linux.vnet.ibm.com>,
	Frederic Barrat <fbarrat@linux.ibm.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Ian Munsie <imunsie@au1.ibm.com>,
	"Manoj N. Kumar" <manoj@linux.ibm.com>,
	Maxime Ripard <mripard@kernel.org>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Shuah Khan <shuah@kernel.org>, Wei Liu <wei.liu@kernel.org>
Subject: Re: [v2] cxl: Fix possible null pointer dereference in read_handle()
Date: Wed, 10 Jul 2024 15:05:31 +0200	[thread overview]
Message-ID: <17c94d87-e260-4155-90c1-b7e5013ac69e@web.de> (raw)
In-Reply-To: <20240710103352.1890726-1-make24@iscas.ac.cn>

…
> - The potential vulnerability was discovered as follows: based on our
> customized static analysis tool,

I became curious in which time range further corresponding information will be published.


>                                  extract vulnerability features[1],

Various software corrections were published through the years.

Several error (or weakness) categories are known already.
https://cwe.mitre.org/
https://wiki.sei.cmu.edu/confluence/display/c/


> and then match similar vulnerability features in this function.
> - Reference link:
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=2d9adecc88ab678785b581ab021f039372c324cb

Another reference format can be helpful also for the commit c534b63bede6cb987c2946ed4d0b0013a52c5ba7
("drm: vc4: Fix possible null pointer dereference") from 2024-04-15.

Regards,
Markus

      parent reply	other threads:[~2024-07-10 13:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-10 10:33 [PATCH v2] " Ma Ke
2024-07-10 10:59 ` Greg KH
2024-07-10 13:05 ` Markus Elfring [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=17c94d87-e260-4155-90c1-b7e5013ac69e@web.de \
    --to=markus.elfring@web.de \
    --cc=ajd@linux.ibm.com \
    --cc=amishin@t-argos.ru \
    --cc=arnd@arndb.de \
    --cc=clombard@linux.vnet.ibm.com \
    --cc=fbarrat@linux.ibm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=imunsie@au1.ibm.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=make24@iscas.ac.cn \
    --cc=manoj@linux.ibm.com \
    --cc=mpe@ellerman.id.au \
    --cc=mripard@kernel.org \
    --cc=shuah@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=wei.liu@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
all inboxes | Powered by JetHome®