Bug 2347836 (CVE-2022-49203) - CVE-2022-49203 kernel: drm/amd/display: Fix double free during GPU reset on DC streams
Summary: CVE-2022-49203 kernel: drm/amd/display: Fix double free during GPU reset on D...
Keywords:
Status: NEW
Alias: CVE-2022-49203
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-02-26 03:08 UTC by OSIDB Bzimport
Modified: 2025-02-27 09:20 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2025-02-26 03:08:28 UTC
In the Linux kernel, the following vulnerability has been resolved:

drm/amd/display: Fix double free during GPU reset on DC streams

[Why]
The issue only occurs during the GPU reset code path.

We first backup the current state prior to commiting 0 streams
internally from DM to DC. This state backup contains valid link
encoder assignments.

DC will clear the link encoder assignments as part of current state
(but not the backup, since it was a copied before the commit) and
free the extra stream reference it held.

DC requires that the link encoder assignments remain cleared/invalid
prior to commiting. Since the backup still has valid assignments we
call the interface post reset to clear them. This routine also
releases the extra reference that the link encoder interface held -
resulting in a double free (and eventually a NULL pointer dereference).

[How]
We'll have to do a full DC commit anyway after GPU reset because
the stream count previously went to 0.

We don't need to retain the assignment that we had backed up, so
just copy off of the now clean current state assignment after the
reset has occcurred with the new link_enc_cfg_copy() interface.

Comment 1 Avinash Hanwate 2025-02-26 21:06:01 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2025022618-CVE-2022-49203-48ec@gregkh/T


Note You need to log in before you can comment on or make changes to this bug.