linux-kernel - Re: [PATCH] drm/mst: Fix NULL pointer dereference in drm_dp_add_payload

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID:
 <CO6PR12MB5489C2D62025CDFDC71C3C21FC092@CO6PR12MB5489.namprd12.prod.outlook.com>
Date: Mon, 15 Apr 2024 02:53:24 +0000
From: "Lin, Wayne" <Wayne.Lin@....com>
To: Jeff Mahoney <jeffm@...e.com>, "dri-devel@...ts.freedesktop.org"
	<dri-devel@...ts.freedesktop.org>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, David
 Airlie <airlied@...il.com>, Daniel Vetter <daniel@...ll.ch>,
	"stable@...r.kernel.org" <stable@...r.kernel.org>
Subject: Re: [PATCH] drm/mst: Fix NULL pointer dereference in
 drm_dp_add_payload_part2 (again)

[Public]

Hi Jeff,

I have a patch sent for this before but not yet get reviewed. Will ping again.
https://patchwork.freedesktop.org/series/130852/

Thanks!

Regards,
Wayne

________________________________________
From: Jeff Mahoney <jeffm@...e.com>
Sent: Saturday, April 13, 2024 08:57
To: Lin, Wayne; dri-devel@...ts.freedesktop.org
Cc: linux-kernel@...r.kernel.org; David Airlie; Daniel Vetter; stable@...r.kernel.org
Subject: Re: [PATCH] drm/mst: Fix NULL pointer dereference in drm_dp_add_payload_part2 (again)

As a follow up, I read through the original thread before sending this
and my understanding is that this message probably shouldn't be getting
printed in the first place.  I've turned on KMS, ATOMIC, STATE, and DP
debugging to see what shakes out.  I have a KVM on my desk that I use to
switch between systems fairly frequently.  I'm speculating that the
connecting and disconnecting is related, so I'm hopeful I can trigger it
quickly.

-Jeff

On 4/12/24 20:22, Jeff Mahoney wrote:
> Commit 54d217406afe (drm: use mgr->dev in drm_dbg_kms in
> drm_dp_add_payload_part2) appears to have been accidentially reverted as
> part of commit 5aa1dfcdf0a42 (drm/mst: Refactor the flow for payload
> allocation/removement).
>
> I've been seeing NULL pointer dereferences in drm_dp_add_payload_part2
> due to state->dev being NULL in the debug message printed if the payload
> allocation has failed.
>
> This commit restores mgr->dev to avoid the Oops.
>
> Fixes: 5aa1dfcdf0a42 ("drm/mst: Refactor the flow for payload allocation/removement")
> Cc: stable@...r.kernel.org
> Signed-off-by: Jeff Mahoney <jeffm@...e.com>
> ---
>   drivers/gpu/drm/display/drm_dp_mst_topology.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/display/drm_dp_mst_topology.c b/drivers/gpu/drm/display/drm_dp_mst_topology.c
> index 03d528209426..3dc966f25c0c 100644
> --- a/drivers/gpu/drm/display/drm_dp_mst_topology.c
> +++ b/drivers/gpu/drm/display/drm_dp_mst_topology.c
> @@ -3437,7 +3437,7 @@ int drm_dp_add_payload_part2(struct drm_dp_mst_topology_mgr *mgr,
>
>       /* Skip failed payloads */
>       if (payload->payload_allocation_status != DRM_DP_MST_PAYLOAD_ALLOCATION_DFP) {
> -             drm_dbg_kms(state->dev, "Part 1 of payload creation for %s failed, skipping part 2\n",
> +             drm_dbg_kms(mgr->dev, "Part 1 of payload creation for %s failed, skipping part 2\n",
>                           payload->port->connector->name);
>               return -EIO;
>       }

--
Jeff Mahoney
VP Engineering, Linux Systems