CVE-2024-58086: drm/v3d: Stop active perfmon if it is being destroyed
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 1c5673a2c8926adbb61f340c779b28e18188a8cd, 21f1435b1e6b012a07c42f36b206d2b66fc8f13b, 22e19c8c5f6b709f4ae40227392a30d57bac187d.
- Severity is disputed: the assigning authority (CNA) scores it 7.8, NVD 5.5.
Low priority for now. Upgrade to Linux Linux 1c5673a2c8926adbb61f340c779b28e18188a8cd, 21f1435b1e6b012a07c42f36b206d2b66fc8f13b, 22e19c8c5f6b709f4ae40227392a30d57bac187d or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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").
- Published
- Mar 6, 2025
- Updated
- Oct 15, 2026
- EPSS
- 0.1% · 9th percentile
- CWE
- —
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- 5.5
- CNA · Linux
- 7.8
- 2.3 point gap
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.15 and later · before 5.15.179
- linux linux kernel5.16 and later · before 6.1.129
- linux linux kernel6.2 and later · before 6.6.79
- linux linux kernel6.7 and later · before 6.12.16
- linux linux kernel6.13 and later · before 6.13.4
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.15affected
- 26a4dc29b74a137f45665089f6d3d633fcc9b662 and later · before 22e19c8c5f6b709f4ae40227392a30d57bac187daffected · git
- 26a4dc29b74a137f45665089f6d3d633fcc9b662 and later · before 95036d4c01167568166108d42c2b0e9f8dbd7d2baffected · git
- 26a4dc29b74a137f45665089f6d3d633fcc9b662 and later · before eb0e0eca0eab93f310c6c37b8564049366704691affected · git
- 26a4dc29b74a137f45665089f6d3d633fcc9b662 and later · before 1c5673a2c8926adbb61f340c779b28e18188a8cdaffected · git
- 26a4dc29b74a137f45665089f6d3d633fcc9b662 and later · before f8805b12f477bd964e2820a87921c7b58cc2dee3affected · git
- 26a4dc29b74a137f45665089f6d3d633fcc9b662 and later · before 21f1435b1e6b012a07c42f36b206d2b66fc8f13baffected · git
- before 5.15not affected · semver
- 5.15.179 and later · up to and including 5.15.*not affected · semver
- 6.1.129 and later · up to and including 6.1.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.129-1 | 6.1.129-1 |
| Debian:13 | linux | before 6.12.16-1 | 6.12.16-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-58083Mar 6, 2025 · KVM: Explicitly verify target vCPU is online in kvm_get_vcpu()31Monitor
- ← EarlierCVE-2024-58085Mar 6, 2025 · tomoyo: don't emit warning in tomoyo_write_control()22Monitor
- Later →CVE-2025-21830Mar 6, 2025 · landlock: Handle weird files22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1c5673a2c8926adbb61f340c779b28e18188a8cd | Vendor (CNA) |
| Linux Linux | 21f1435b1e6b012a07c42f36b206d2b66fc8f13b | Vendor (CNA) |
| Linux Linux | 22e19c8c5f6b709f4ae40227392a30d57bac187d | Vendor (CNA) |
| Linux Linux | 95036d4c01167568166108d42c2b0e9f8dbd7d2b | Vendor (CNA) |
| Linux Linux | eb0e0eca0eab93f310c6c37b8564049366704691 | Vendor (CNA) |
| Linux Linux | f8805b12f477bd964e2820a87921c7b58cc2dee3 | Vendor (CNA) |
| debian:linux | 6.1.129-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- git.kernel.org/stable/c/21f1435b1e6b012a07c42f36b206d2b66fc8f13b
- git.kernel.org/stable/c/22e19c8c5f6b709f4ae40227392a30d57bac187d
- git.kernel.org/stable/c/95036d4c01167568166108d42c2b0e9f8dbd7d2b
- git.kernel.org/stable/c/eb0e0eca0eab93f310c6c37b8564049366704691
- git.kernel.org/stable/c/f8805b12f477bd964e2820a87921c7b58cc2dee3
- lists.debian.org/debian-lts-announce/2025/03/msg00028.html
- cert-portal.siemens.com/productcert/html/ssa-019113.html
- cert-portal.siemens.com/productcert/html/ssa-457936.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.