CVE-2026-53141: drm/v3d: Fix global performance monitor reference counting

Published Jun 25, 2026
·
Updated

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

drm/v3d: Fix global performance monitor reference counting

In the SETGLOBAL ioctl, v3dperfmonfind() bumps the reference count on the perfmon it returns, but v3dperfmonsetglobalioctl() and v3dperfmondelete() fail to release that reference on several paths:

1. v3dperfmonsetglobalioctl() leaks the reference on its error paths.

2. CLEARGLOBAL leaks both the find reference and the reference previously stashed in v3d->globalperfmon by the SETGLOBAL ioctl that configured it.

3. Destroying a perfmon that is the current global perfmon leaks the reference stashed by the SETGLOBAL ioctl.

Release each of these references explicitly.

Affected Software

9 affected components
Linux Linux kernel
Linux Linux kernel>=6.14<6.18.36
Linux Linux kernel>=6.19<7.0.13
Linux Linux kernel=7.1-rc1
Linux Linux kernel=7.1-rc2
Linux Linux kernel=7.1-rc3
Linux Linux kernel=7.1-rc4
Linux Linux kernel=7.1-rc5
Linux Linux kernel=7.1-rc6

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Compensating control

    Release each of the leaked references explicitly when calling v3d_perfmon_set_global_ioctl() and v3d_perfmon_delete(), ensuring the reference bumped by v3d_perfmon_find() is released on all error paths (the material states releases are needed because SET_GLOBAL ioctl and global perfmon destroy currently fail to release references on several paths).

Event History

Jun 25, 2026
CVE Published
via MITRE·08:38 AM
Data Sourced
via MITRE·08:38 AM
Description
Data Sourced
via NVD·09:16 AM
RemedyDescriptionSeverityAffected Software

Frequently Asked Questions

1

What access does an attacker need to exploit this issue?

The CVSS vector indicates local access with low privileges is required. No user interaction is required.

2

What is the expected security impact?

The issue is rated as having high availability impact, with no confidentiality or integrity impact. The underlying flaw is unreleased performance-monitor references that can accumulate on affected paths.

3

Which operations are associated with the reference leaks?

Leaks occur on error paths in SET_GLOBAL, when CLEAR_GLOBAL is used, and when a performance monitor that is currently configured as global is destroyed.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203