Bug 2324569 (CVE-2024-50187) - CVE-2024-50187 kernel: drm/vc4: Stop the active perfmon before being destroyed
Summary: CVE-2024-50187 kernel: drm/vc4: Stop the active perfmon before being destroyed
Keywords:
Status: NEW
Alias: CVE-2024-50187
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: 2324694
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-11-08 13:45 UTC by OSIDB Bzimport
Modified: 2024-11-21 18:51 UTC (History)
4 users (show)

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


Attachments (Terms of Use)

Description OSIDB Bzimport 2024-11-08 13:45:57 UTC
In the Linux kernel, the following vulnerability has been resolved:

drm/vc4: Stop the active perfmon before being destroyed

Upon closing the file descriptor, the active performance monitor is not
stopped. Although all perfmons are destroyed in `vc4_perfmon_close_file()`,
the active performance monitor's pointer (`vc4->active_perfmon`) is still
retained.

If we open a new file descriptor and submit a few jobs with performance
monitors, the driver will attempt to stop the active performance monitor
using the stale pointer in `vc4->active_perfmon`. However, this pointer
is no longer valid because the previous process has already terminated,
and all performance monitors associated with it have been destroyed and
freed.

To fix this, when the active performance monitor belongs to a given
process, explicitly stop it before destroying and freeing it.


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