CVE-2022-49203

Source
https://nvd.nist.gov/vuln/detail/CVE-2022-49203
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-49203.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2022-49203
Related
Published
2025-02-26T07:00:57Z
Modified
2025-03-18T20:12:03Z
Downstream
Severity
  • 5.5 (Medium) CVSS_V3 - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H CVSS Calculator
Summary
[none]
Details

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 linkenccfg_copy() interface.

References

Affected packages

Debian:12 / linux

Package

Name
linux
Purl
pkg:deb/debian/linux?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
5.17.3-1

Ecosystem specific

{
    "urgency": "not yet assigned"
}

Debian:13 / linux

Package

Name
linux
Purl
pkg:deb/debian/linux?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
5.17.3-1

Ecosystem specific

{
    "urgency": "not yet assigned"
}