CVE-2022-49663

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-24. 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-54570 (ENISA EUVD) · GHSA-vrmp-g995-qwm3 (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:

tunnels: do not assume mac header is set in skb_tunnel_check_pmtu()

Recently added debug in commit f9aefd6b2aa3 ("net: warn if mac header was not set") caught a bug in skb_tunnel_check_pmtu(), as shown in this syzbot report [1].

In ndo_start_xmit() paths, there is really no need to use skb->mac_header, because skb->data is supposed to point at it.

[1] WARNING: CPU: 1 PID: 8604 at include/linux/skbuff.h:2784 skb_mac_header_len include/linux/skbuff.h:2784 [inline] WARNING: CPU: 1 PID: 8604 at include/linux/skbuff.h:2784 skb_tunnel_check_pmtu+0x5de/0x2f90 net/ipv4/ip_tunnel_core.c:413 Modules linked in: CPU: 1 PID: 8604 Comm: syz-executor.3 Not tainted 5.19.0-rc2-syzkaller-00443-g8720bd951b8e #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 RIP: 0010:skb_mac_header_len include/linux/skbuff.h:2784 [inline] RIP: 0010:skb_tunnel_check_pmtu+0x5de/0x2f90 net/ipv4/ip_tunnel_core.c:413 Code: 00 00 00 00 fc ff df 4c 89 fa 48 c1 ea 03 80 3c 02 00 0f 84 b9 fe ff ff 4c 89 ff e8 7c 0f d7 f9 e9 ac fe ff ff e8 c2 13 8a f9 <0f> 0b e9 28 fc ff ff e8 b6 13 8a f9 48 8b 54 24 70 48 b8 00 00 00 RSP: 0018:ffffc90002e4f520 EFLAGS: 00010212 RAX: 0000000000000324 RBX: ffff88804d5fd500 RCX: ffffc90005b52000 RDX: 0000000000040000 RSI: ffffffff87f05e3e RDI: 0000000000000003 RBP: ffffc90002e4f650 R08: 0000000000000003 R09: 000000000000ffff R10: 000000000000ffff R11: 0000000000000000 R12: 000000000000ffff R13: 0000000000000000 R14: 000000000000ffcd R15: 000000000000001f FS: 00007f3babba9700(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000020000080 CR3: 0000000075319000 CR4: 00000000003506e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace:

geneve_xmit_skb drivers/net/geneve.c:927 [inline] geneve_xmit+0xcf8/0x35d0 drivers/net/geneve.c:1107 __netdev_start_xmit include/linux/netdevice.h:4805 [inline] netdev_start_xmit include/linux/netdevice.h:4819 [inline] __dev_direct_xmit+0x500/0x730 net/core/dev.c:4309 dev_direct_xmit include/linux/netdevice.h:3007 [inline] packet_direct_xmit+0x1b8/0x2c0 net/packet/af_packet.c:282 packet_snd net/packet/af_packet.c:3073 [inline] packet_sendmsg+0x21f4/0x55d0 net/packet/af_packet.c:3104 sock_sendmsg_nosec net/socket.c:714 [inline] sock_sendmsg+0xcf/0x120 net/socket.c:734 ____sys_sendmsg+0x6eb/0x810 net/socket.c:2489 ___sys_sendmsg+0xf3/0x170 net/socket.c:2543 __sys_sendmsg net/socket.c:2572 [inline] __do_sys_sendmsg net/socket.c:2581 [inline] __se_sys_sendmsg net/socket.c:2579 [inline] __x64_sys_sendmsg+0x132/0x220 net/socket.c:2579 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x46/0xb0 RIP: 0033:0x7f3baaa89109 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f3babba9168 EFLAGS: 00000246 ORIG_RAX: 000000000000002e RAX: ffffffffffffffda RBX: 00007f3baab9bf60 RCX: 00007f3baaa89109 RDX: 0000000000000000 RSI: 0000000020000a00 RDI: 0000000000000003 RBP: 00007f3baaae305d R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffe74f2543f R14: 00007f3babba9300 R15: 0000000000022000

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
19th
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 24, 2025

References (4)

Vendor Advisories for CVE-2022-49663(2)

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-0:4.18.0-477.10.1.el8_82023-05-16redhat
redhatkernel-0:5.14.0-162.6.1.el9_12022-11-15redhat
linuxKernel @ 5.10.129 (fixes >=5.9.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 (17 versions)
  • every version up to 5.10.136-1: fixed in 5.10.136-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.18.14-1: fixed in 5.18.14-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.18.14-1: fixed in 5.18.14-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.18.14-1: fixed in 5.18.14-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 97 of 193 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. 3 repeat rows among the latest 100 are merged into the row they repeat. The 96 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2022-49663?
CVE-2022-49663 is a medium-severity vulnerability; its CVE record was published on February 26, 2025. In the Linux kernel, the following vulnerability has been resolved: tunnels: do not assume mac header is set in skb_tunnel_check_pmtu() Recently added debug in commit f9aefd6b2aa3 ("net: warn if mac header was not set") caught a bug in skb_tunnel_check_pmtu(), as shown in this syzbot report [1]. In…
When was the CVE record for CVE-2022-49663 published?
The CVE record for CVE-2022-49663 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 24, 2025; the record at its source may have been updated since.
Is CVE-2022-49663 actively exploited?
CVE-2022-49663 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (19th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-49663?
CVE-2022-49663 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2022-49663?
A fix for CVE-2022-49663 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-49663 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-49663

Explore →

Is Your Infrastructure Affected by CVE-2022-49663?

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

Book a Demo →Browse All CVEs