Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-50187drm/vc4: Stop the active perfmon before being destroyed

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 18 days later

    Published

  3. · 21 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-50187, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CISA-ADPADP (enrichment)3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.23% · top 86% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 65101d8c9108201118efa7e08f4e2c57f438deb9 – < 75452da51e2403e14be007df80d133e1443fc967
    • affected 65101d8c9108201118efa7e08f4e2c57f438deb9 – < 937943c042503dc6087438bf3557f9057a588ba0
    • affected 65101d8c9108201118efa7e08f4e2c57f438deb9 – < c9adba739d5f7cdc47a7754df4a17b47b1ecf513
    • affected 65101d8c9108201118efa7e08f4e2c57f438deb9 – < 0b2ad4f6f2bec74a5287d96cb2325a5e11706f22
  • Linux · Linux

    • affected 4.17
    • unaffected < 4.17
    • unaffected 6.1.113 – ≤ 6.1.*
    • unaffected 6.6.57 – ≤ 6.6.*
    • unaffected 6.11.4 – ≤ 6.11.*
    • unaffected 6.12 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-50187 badge
[![CVE-2024-50187](https://cveledger.app/badge/CVE-2024-50187.svg)](https://cveledger.app/cve/CVE-2024-50187)

Record last updated .