From: Danilo Krummrich <dakr@redhat.com>
To: Ma Ke <make24@iscas.ac.cn>
Cc: dri-devel@lists.freedesktop.org, nouveau@lists.freedesktop.org,
lyude@redhat.com, linux-kernel@vger.kernel.org, daniel@ffwll.ch,
airlied@gmail.com, kherbst@redhat.com,
Jani Nikula <jani.nikula@linux.intel.com>
Subject: Re: [PATCH] drm/nouveau: fix null pointer dereference in nouveau_connector_get_modes
Date: Wed, 26 Jun 2024 16:53:59 +0200 [thread overview]
Message-ID: <0119ce0b-d0e1-48fb-a2e2-2643472bf434@redhat.com> (raw)
In-Reply-To: <875xtwdone.fsf@intel.com>
On 6/26/24 11:44, Jani Nikula wrote:
> On Wed, 26 Jun 2024, Ma Ke <make24@iscas.ac.cn> wrote:
>> In nouveau_connector_get_modes(), the return value of drm_mode_duplicate()
>> is assigned to mode, which will lead to a possible NULL pointer
>> dereference on failure of drm_mode_duplicate(). Add a check to avoid npd.
>>
Please add a "Fixes" tag (also for your previous commits) and CC stable.
>> Signed-off-by: Ma Ke <make24@iscas.ac.cn>
>> ---
>> drivers/gpu/drm/nouveau/nouveau_connector.c | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/nouveau/nouveau_connector.c b/drivers/gpu/drm/nouveau/nouveau_connector.c
>> index 856b3ef5edb8..010eed56b14d 100644
>> --- a/drivers/gpu/drm/nouveau/nouveau_connector.c
>> +++ b/drivers/gpu/drm/nouveau/nouveau_connector.c
>> @@ -1001,6 +1001,8 @@ nouveau_connector_get_modes(struct drm_connector *connector)
>> struct drm_display_mode *mode;
>>
>> mode = drm_mode_duplicate(dev, nv_connector->native_mode);
>> + if (!mode)
>> + return -ENOMEM;
>
> Do not return negative values from .get_modes().
+1
https://elixir.bootlin.com/linux/latest/source/include/drm/drm_modeset_helper_vtables.h#L899
>
> BR,
> Jani.
>
>> drm_mode_probed_add(connector, mode);
>> ret = 1;
>> }
>
next prev parent reply other threads:[~2024-06-26 14:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 1:30 [PATCH] drm/nouveau: fix null pointer dereference in nouveau_connector_get_modes Ma Ke
2024-06-26 9:44 ` Jani Nikula
2024-06-26 14:53 ` Danilo Krummrich [this message]
2024-06-26 11:35 ` 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=0119ce0b-d0e1-48fb-a2e2-2643472bf434@redhat.com \
--to=dakr@redhat.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=kherbst@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lyude@redhat.com \
--cc=make24@iscas.ac.cn \
--cc=nouveau@lists.freedesktop.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