LiveActive security incident?Get immediate response
CVE Record

CVE-2024-58086: drm/v3d: Stop active perfmon if it is being destroyed

In the Linux kernel, the following vulnerability has been resolved: drm/v3d: Stop active perfmon if it is being destroyed If the active performance monitor (`v3d->active_perfmon`) is being destroyed, stop it first. Currently, the active perfmon is not stopped during destruction, leaving the `v3d->active_perfmon` pointer stale. This can lead to undefined behavior and instability. This patch ensures that the active perfmon is stopped before being destroyed, aligning with the behavior introduced in commit 7d1fd3638ee3 ("drm/v3d: Stop the active perfmon before being destroyed").

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel graphics driver stability flaw in drm/v3d. If an active performance monitor is destroyed without first being stopped, the kernel can retain a stale pointer, causing undefined behavior and instability. Business impact is most relevant for Linux systems using this driver; severity is not scored in the provided sources.

Executive priority

Treat this as a targeted Linux kernel maintenance item, not an emergency based on current evidence. Prioritize patching for affected Linux fleets using v3d graphics, embedded devices, and vendor-managed products named in advisories.

Technical view

CVE-2024-58086 fixes drm/v3d perfmon destruction handling. The active perfmon pointer, v3d->active_perfmon, could remain stale when the active performance monitor was destroyed. Stable kernel commits stop the active perfmon before destruction, aligning behavior with the referenced upstream fix.

Likely exposure

Likely exposure is Linux systems running affected kernel branches with the drm/v3d driver present or enabled. Systems without this driver are less likely affected. The provided bundle also cites Debian LTS and Siemens advisories, but product-specific impact must be checked there.

Exploitation context

The CVE is not listed as KEV in the supplied bundle, and no cited source states active exploitation. The available evidence describes a kernel driver correctness and stability issue, not a public exploit scenario.

Researcher notes

The root issue is stale active_perfmon state during destruction in drm/v3d. The source bundle provides fix commits but no CVSS, CWE, exploit details, or complete product matrix. Avoid broad impact claims without confirming driver presence and vendor kernel backports.

Mitigation direction

  • Update affected Linux kernels to vendor builds containing the stable fixes.
  • Review Debian LTS guidance if using Debian-based long-term support systems.
  • Review Siemens SSA-019113 if Siemens products are in scope.
  • Prioritize systems where drm/v3d is enabled or graphics workloads are exposed.
  • If no vendor package is available, monitor vendor guidance for fixed kernel releases.

Validation and detection

  • Inventory kernel versions across Linux assets.
  • Check whether drm/v3d is built, loaded, or enabled.
  • Compare deployed kernels against vendor advisories and stable fix references.
  • Review kernel logs for drm/v3d instability indicators.
  • Confirm updated systems are running the patched kernel after reboot.
Prepared
Confidence
medium
Sources
10

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-58086 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
9Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
siemens-SADPADP container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux26a4dc29b74a137f45665089f6d3d633fcc9b662, 26a4dc29b74a137f45665089f6d3d633fcc9b662, 26a4dc29b74a137f45665089f6d3d633fcc9b662, 26a4dc29b74a137f45665089f6d3d633fcc9b662, 26a4dc29b74a137f45665089f6d3d633fcc9b662, 26a4dc29b74a137f45665089f6d3d633fcc9b662unaffected
LinuxLinux5.15, 0, 5.15.179, 6.1.129, 6.6.79, 6.12.16, 6.13.4, 6.14affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.