Kernel instability via stale perfmon pointer
Published Mar 6, 2025 · Updated Sep 8, 2026
Improper input validation in Linux drm/v3d allows local users to destabilize affected kernels by destroying an active performance monitor. The v3d_perfmon_destroy_ioctl path releases an active monitor without stopping it first, leaving v3d->active_perfmon pointing to released state. Reaching the flaw requires local access to the V3D performance-monitor interface; the bounded consequence is undefined behavior, instability, or kernel service interruption.
Summary
What happened
Improper input validation in Linux drm/v3d allows local users to destabilize affected kernels by destroying an active performance monitor. The v3d_perfmon_destroy_ioctl path releases an active monitor without stopping it first, leaving v3d->active_perfmon pointing to released state. Reaching the flaw requires local access to the V3D performance-monitor interface; the bounded consequence is undefined behavior, instability, or kernel service interruption.
The record
- CVE
- CVE-2024-58086
- Published
- Mar 6, 2025
- Updated
- Sep 8, 2026
- Vendor
- Siemens
- Product
- SIPLUS S7-1500 CPU 1518-4 PN/DP MFP
- Classifications
- CWE-20
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 6, 2025CVE publishedPublication date reported by the CVE source.
- Sep 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=V3.1.6 <*
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo