CVE-2022-49458

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 5.5 from GitHub Security Advisory published 2025-10-22. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2022-54771 (ENISA EUVD) · GHSA-c6q3-q7pq-58wm (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

drm/msm: don't free the IRQ if it was not requested

As msm_drm_uninit() is called from the msm_drm_init() error path, additional care should be necessary as not to call the free_irq() for the IRQ that was not requested before (because an error occured earlier than the request_irq() call).

This fixed the issue reported with the following backtrace:

[ 8.571329] Trying to free already-free IRQ 187 [ 8.571339] WARNING: CPU: 0 PID: 76 at kernel/irq/manage.c:1895 free_irq+0x1e0/0x35c [ 8.588746] Modules linked in: pmic_glink pdr_interface fastrpc qrtr_smd snd_soc_hdmi_codec msm fsa4480 gpu_sched drm_dp_aux_bus qrtr i2c_qcom_geni crct10dif_ce qcom_stats qcom_q6v5_pas drm_display_helper gpi qcom_pil_info drm_kms_helper qcom_q6v5 qcom_sysmon qcom_common qcom_glink_smem qcom_rng mdt_loader qmi_helpers phy_qcom_qmp ufs_qcom typec qnoc_sm8350 socinfo rmtfs_mem fuse drm ipv6 [ 8.624154] CPU: 0 PID: 76 Comm: kworker/u16:2 Not tainted 5.18.0-rc5-next-20220506-00033-g6cee8cab6089-dirty #419 [ 8.624161] Hardware name: Qualcomm Technologies, Inc. SM8350 HDK (DT) [ 8.641496] Workqueue: events_unbound deferred_probe_work_func [ 8.647510] pstate: 604000c5 (nZCv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 8.654681] pc : free_irq+0x1e0/0x35c [ 8.658454] lr : free_irq+0x1e0/0x35c [ 8.662228] sp : ffff800008ab3950 [ 8.665642] x29: ffff800008ab3950 x28: 0000000000000000 x27: ffff16350f56a700 [ 8.672994] x26: ffff1635025df080 x25: ffff16350251badc x24: ffff16350251bb90 [ 8.680343] x23: 0000000000000000 x22: 00000000000000bb x21: ffff16350e8f9800 [ 8.687690] x20: ffff16350251ba00 x19: ffff16350cbd5880 x18: ffffffffffffffff [ 8.695039] x17: 0000000000000000 x16: ffffa2dd12179434 x15: ffffa2dd1431d02d [ 8.702391] x14: 0000000000000000 x13: ffffa2dd1431d028 x12: 662d79646165726c [ 8.709740] x11: ffffa2dd13fd2438 x10: 000000000000000a x9 : 00000000000000bb [ 8.717111] x8 : ffffa2dd13fd23f0 x7 : ffff800008ab3750 x6 : 00000000fffff202 [ 8.724487] x5 : ffff16377e870a18 x4 : 00000000fffff202 x3 : ffff735a6ae1b000 [ 8.731851] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff1635015f8000 [ 8.739217] Call trace: [ 8.741755] free_irq+0x1e0/0x35c [ 8.745198] msm_drm_uninit.isra.0+0x14c/0x294 [msm] [ 8.750548] msm_drm_bind+0x28c/0x5d0 [msm] [ 8.755081] try_to_bring_up_aggregate_device+0x164/0x1d0 [ 8.760657] __component_add+0xa0/0x170 [ 8.764626] component_add+0x14/0x20 [ 8.768337] dp_display_probe+0x2a4/0x464 [msm] [ 8.773242] platform_probe+0x68/0xe0 [ 8.777043] really_probe.part.0+0x9c/0x28c [ 8.781368] __driver_probe_device+0x98/0x144 [ 8.785871] driver_probe_device+0x40/0x140 [ 8.790191] __device_attach_driver+0xb4/0x120 [ 8.794788] bus_for_each_drv+0x78/0xd0 [ 8.798751] __device_attach+0xdc/0x184 [ 8.802713] device_initial_probe+0x14/0x20 [ 8.807031] bus_probe_device+0x9c/0xa4 [ 8.810991] deferred_probe_work_func+0x88/0xc0 [ 8.815667] process_one_work+0x1d0/0x320 [ 8.819809] worker_thread+0x14c/0x444 [ 8.823688] kthread+0x10c/0x110 [ 8.827036] ret_from_fork+0x10/0x20

Patchwork: https://patchwork.freedesktop.org/patch/485422/

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
17th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-25). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

February 26, 2025

Last Modified

October 22, 2025

References (4)

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 5.15.46 (fixes >=5.15.0)—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.18.5-1: fixed in 5.18.5-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.18.5-1: fixed in 5.18.5-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.18.5-1: fixed in 5.18.5-1
—

Data Freshness Timeline

(refreshed 7× in last 7d / 37× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 98 of 198 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 100 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-06 16:31 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  2. 2026-11-05 16:32 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  3. 2026-11-04 16:30 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  4. 2026-11-03 16:40 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  5. 2026-11-02 16:39 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  6. 2026-11-01 16:30 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  7. 2026-10-31 16:29 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  8. 2026-10-30 16:31 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  9. 2026-10-29 16:30 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  10. 2026-10-28 16:28 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  11. 2026-10-27 16:28 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  12. 2026-10-26 16:28 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  13. 2026-10-25 17:55 UTCEG score recompute
  14. 2026-10-25 16:29 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  15. 2026-10-24 17:52 UTCEG score recompute
  16. 2026-10-24 17:52 UTCGHSA enrichmentGHSA-c6q3-q7pq-58wm · GitHub CVSS 5.5
  17. 2026-10-24 16:29 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  18. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  19. 2026-10-22 16:30 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  20. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  21. 2026-10-20 16:29 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  22. 2026-10-19 16:28 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  23. 2026-10-18 16:29 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  24. 2026-10-18 08:20 UTCEG score recompute
  25. 2026-10-17 16:29 UTCEPSS rescoreEPSS 0.3% · 16th percentile
Show 73 more
  1. 2026-10-16 16:35 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  2. 2026-10-15 16:28 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  3. 2026-10-14 16:29 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  4. 2026-10-13 16:29 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  5. 2026-10-12 18:42 UTCEG score recompute
  6. 2026-10-12 16:30 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  7. 2026-10-11 22:05 UTCEG score recompute
  8. 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  9. 2026-10-10 19:57 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  10. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  11. 2026-10-08 17:05 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  12. 2026-10-07 23:45 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  13. 2026-10-06 15:14 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  14. 2026-10-05 17:40 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  15. 2026-10-04 23:19 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  16. 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  17. 2026-10-02 22:10 UTCOSV refresh
  18. 2026-09-30 16:12 UTCEG score recompute
  19. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  20. 2026-09-27 13:42 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  21. 2026-09-26 15:55 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  22. 2026-09-26 00:22 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  23. 2026-09-24 14:00 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  24. 2026-09-23 13:45 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  25. 2026-09-20 20:13 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  26. 2026-09-16 14:05 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  27. 2026-09-16 05:11 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  28. 2026-09-15 03:07 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  29. 2026-09-13 19:39 UTCOSV refresh
  30. 2026-09-13 16:44 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  31. 2026-09-11 14:50 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  32. 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  33. 2026-09-08 21:57 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  34. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  35. 2026-09-06 13:45 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  36. 2026-09-05 15:25 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  37. 2026-09-04 13:57 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  38. 2026-09-04 05:04 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  39. 2026-09-02 14:09 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  40. 2026-09-01 13:51 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  41. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  42. 2026-08-30 01:19 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  43. 2026-08-28 21:38 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  44. 2026-08-27 14:22 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  45. 2026-08-26 14:43 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  46. 2026-08-25 21:09 UTCOSV refresh
  47. 2026-08-25 13:46 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  48. 2026-08-23 00:17 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  49. 2026-08-21 23:46 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  50. 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  51. 2026-08-19 17:01 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  52. 2026-08-18 13:45 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  53. 2026-08-17 13:44 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  54. 2026-08-16 14:53 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  55. 2026-08-16 02:12 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  56. 2026-08-15 01:27 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  57. 2026-08-13 21:58 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  58. 2026-08-12 13:48 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  59. 2026-08-09 13:44 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  60. 2026-08-09 13:40 UTCOSV refresh
  61. 2026-08-08 16:34 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  62. 2026-08-07 16:24 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  63. 2026-08-06 13:44 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  64. 2026-08-05 19:15 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  65. 2026-08-04 15:07 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  66. 2026-08-04 10:35 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  67. 2026-08-03 10:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  68. 2026-08-02 02:24 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  69. 2026-08-01 04:13 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  70. 2026-07-30 16:25 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  71. 2026-07-30 01:28 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  72. 2026-07-28 15:34 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  73. 2026-07-26 14:52 UTCEPSS rescoreEPSS 0.3% · 17th percentile

Frequently asked(5)

What is CVE-2022-49458?
CVE-2022-49458 is a medium-severity vulnerability; its CVE record was published on February 26, 2025. In the Linux kernel, the following vulnerability has been resolved: drm/msm: don't free the IRQ if it was not requested As msm_drm_uninit() is called from the msm_drm_init() error path, additional care should be necessary as not to call the free_irq() for the IRQ that was not requested before…
When was the CVE record for CVE-2022-49458 published?
The CVE record for CVE-2022-49458 was published on February 26, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 22, 2025; the record at its source may have been updated since.
Is CVE-2022-49458 actively exploited?
CVE-2022-49458 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (17th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-49458?
CVE-2022-49458 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2022-49458?
A fix for CVE-2022-49458 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-49458

Explore →

Is Your Infrastructure Affected by CVE-2022-49458?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs