References to Advisories, Solutions, and Tools

By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to nvd@nist.gov.

Change History

https://git.kernel.org/stable/c/2ef98c6d753a744e333b7e34b9cf687040fba57d

https://git.kernel.org/stable/c/e5ffd1263dd5b44929c676171802e7b6af483f21

In the Linux kernel, the following vulnerability has been resolved:

drm/amd/display: Wake DMCUB before executing GPINT commands

[Why]
DMCUB can be in idle when we attempt to interface with the HW through
the GPINT mailbox resulting in a system hang.

[How]
Add dc_wake_and_execute_gpint() to wrap the wake, execute, sleep
sequence.

If the GPINT executes successfully then DMCUB will be put back into
sleep after the optional response is returned.

It functions similar to the inbox command interfa

kernel.org https://git.kernel.org/stable/c/2ef98c6d753a744e333b7e34b9cf687040fba57d [No types assigned]

kernel.org https://git.kernel.org/stable/c/e5ffd1263dd5b44929c676171802e7b6af483f21 [No types assigned]