From: Chen Jun <chenjun102@huawei.com>
To: <gregkh@linuxfoundation.org>
Cc: <cve@kernel.org>, <linux-cve-announce@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, Chen Jun <chenjun102@huawei.com>
Subject: Re: CVE-2024-43867: drm/nouveau: prime: fix refcount underflow
Date: Mon, 2 Sep 2024 16:01:14 +0800 [thread overview]
Message-ID: <20240902080114.69287-1-chenjun102@huawei.com> (raw)
In-Reply-To: <2024082157-CVE-2024-43867-0620@gregkh>
Hi,
This issue seems to be introduced by 019cbd4a4feb instead of ab9ccb96a6e6.
Could anyone help check again?
Thanks.
next parent reply other threads:[~2024-09-02 8:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2024082157-CVE-2024-43867-0620@gregkh>
2024-09-02 8:01 ` Chen Jun [this message]
2024-09-08 14:19 ` CVE-2024-43867: drm/nouveau: prime: fix refcount underflow Greg KH
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=20240902080114.69287-1-chenjun102@huawei.com \
--to=chenjun102@huawei.com \
--cc=cve@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@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