Security readout for executives and security teams
Plain-English summary
This Linux kernel issue affects Qualcomm MSM graphics initialization error handling. If driver setup fails before an IRQ is requested, cleanup can incorrectly try to free that IRQ, triggering a kernel warning. The supplied sources do not show active exploitation, CVSS scoring, or business-impact evidence beyond reliability risk on affected systems.
Executive priority
Handle through normal kernel maintenance unless affected Qualcomm-based devices show instability. There is no cited exploitation evidence or CVSS score in the provided bundle, so urgency is driven by exposure to the msm DRM driver and operational reliability needs.
Technical view
The flaw is in drm/msm cleanup: msm_drm_uninit() can run from the msm_drm_init() error path and call free_irq() for an IRQ that was never requested. The reported trace shows a “Trying to free already-free IRQ” warning during deferred probe on Qualcomm SM8350 hardware.
Likely exposure
Exposure appears limited to Linux systems using the Qualcomm MSM DRM driver in the affected kernel versions listed by the CVE bundle. The bundle names Linux kernels including 5.15, 5.15.46, 5.17.14, 5.18.3, and 5.19, but distro backports may change practical exposure.
Exploitation context
The source bundle provides no evidence of active exploitation and KEV is false. The described failure is an initialization cleanup bug observed during driver probing, not a documented remote attack path. Treat exploitability and impact as incomplete until vendor or distribution advisories clarify severity.
Researcher notes
Focus analysis on msm_drm_init() error unwinding into msm_drm_uninit() before request_irq() succeeds. The supplied evidence supports an IRQ lifecycle bug and warning condition, but not a confirmed privilege escalation, remote vector, or weaponized exploit.
Mitigation direction
Check vendor or Linux distribution advisories for fixed kernel packages.
Prioritize systems using Qualcomm MSM/Adreno display hardware or msm DRM modules.
Compare deployed kernels against the referenced stable kernel commits.
Apply vendor-supported kernel updates when available.
Monitor boot and kernel logs for repeated msm DRM IRQ warnings.
Validation and detection
Inventory Linux kernel versions on Qualcomm MSM-based devices.
Confirm whether the msm DRM driver is built, loaded, or used.
Review kernel logs for “Trying to free already-free IRQ” warnings.
Map local kernel source or package changelog to the stable fix commits.
Verify updated systems boot without the reported warning.
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-2022-49458 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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
0ADP providers
5Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Feb 26, 2025, 02:13 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.