CVE-2022-49275

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-03-04. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

can: m_can: m_can_tx_handler(): fix use after free of skb

can_put_echo_skb() will clone skb then free the skb. Move the can_put_echo_skb() for the m_can version 3.0.x directly before the start of the xmit in hardware, similar to the 3.1.x branch.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
18th
KEV
Not listed

CISA SSVCTrack 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 (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

February 26, 2025

Last Modified

August 5, 2026

Advisory Details (9)

Auto-updated Aug 5, 2026
Patch available.
generic

can: m_can: m_can_tx_handler(): fix use after free of skb - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2e8e79c416aae1de224c0f1860f2e3350fa171f8
generic

can: m_can: m_can_tx_handler(): fix use after free of skb - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/31417073493f302d26ab66b3abc098d43227b835
generic

can: m_can: m_can_tx_handler(): fix use after free of skb - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4db7d6f481990dd179a9ee7126dc7aa31ea4fff3
generic

can: m_can: m_can_tx_handler(): fix use after free of skb - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f43e64076ff1b1dcb893fb77ad1204105f710a29
generic

can: m_can: m_can_tx_handler(): fix use after free of skb - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/869016a2938ac44f7b2fb7fc22c89edad99eb9b3
generic

can: m_can: m_can_tx_handler(): fix use after free of skb - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/08d90846e438ac22dc56fc49ec0b0d195831c5ed
generic

can: m_can: m_can_tx_handler(): fix use after free of skb - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7728d937ec403a1ceff9483023252d2cb8777f81
generic

can: m_can: m_can_tx_handler(): fix use after free of skb - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d3892a747ab16b1eb6593a19d29f62c3b3f020ac
generic

can: m_can: m_can_tx_handler(): fix use after free of skb - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d93ed9aff64968f4cdad690712eb4f48ae537bde

Vendor Advisories for CVE-2022-49275(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-0:5.14.0-284.11.1.el9_22023-05-09redhat
linuxKernel @ 4.9.324 (fixes >=3.18.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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (11 versions)
  • every version up to 5.10.113-1: fixed in 5.10.113-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.17.3-1: fixed in 5.17.3-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.17.3-1: fixed in 5.17.3-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.17.3-1: fixed in 5.17.3-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

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

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 168 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2022-49275?
CVE-2022-49275 is a high vulnerability published on February 26, 2025. In the Linux kernel, the following vulnerability has been resolved: can: mcan: mcantxhandler(): fix use after free of skb canputecho_skb() will clone skb then free the skb. Move the canputechoskb() for the mcan version 3.0.x directly before the start of the xmit in hardware, similar to the 3.1.x…
When was CVE-2022-49275 disclosed?
CVE-2022-49275 was first published on February 26, 2025, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-49275 actively exploited?
CVE-2022-49275 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (18th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-49275?
CVE-2022-49275 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2022-49275?
A fix for CVE-2022-49275 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-49275 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2022-49275?

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