CVE-2022-49330

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-09-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-54898 (ENISA EUVD) · GHSA-ff7q-8m86-737m (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.8%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

tcp: fix tcp_mtup_probe_success vs wrong snd_cwnd

syzbot got a new report [1] finally pointing to a very old bug, added in initial support for MTU probing.

tcp_mtu_probe() has checks about starting an MTU probe if tcp_snd_cwnd(tp) >= 11.

But nothing prevents tcp_snd_cwnd(tp) to be reduced later and before the MTU probe succeeds.

This bug would lead to potential zero-divides.

Debugging added in commit 40570375356c ("tcp: add accessors to read/set tp->snd_cwnd") has paid off :)

While we are at it, address potential overflows in this code.

[1] WARNING: CPU: 1 PID: 14132 at include/net/tcp.h:1219 tcp_mtup_probe_success+0x366/0x570 net/ipv4/tcp_input.c:2712 Modules linked in: CPU: 1 PID: 14132 Comm: syz-executor.2 Not tainted 5.18.0-syzkaller-07857-gbabf0bb978e3 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 RIP: 0010:tcp_snd_cwnd_set include/net/tcp.h:1219 [inline] RIP: 0010:tcp_mtup_probe_success+0x366/0x570 net/ipv4/tcp_input.c:2712 Code: 74 08 48 89 ef e8 da 80 17 f9 48 8b 45 00 65 48 ff 80 80 03 00 00 48 83 c4 30 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 aa b0 c5 f8 <0f> 0b e9 16 fe ff ff 48 8b 4c 24 08 80 e1 07 38 c1 0f 8c c7 fc ff RSP: 0018:ffffc900079e70f8 EFLAGS: 00010287 RAX: ffffffff88c0f7f6 RBX: ffff8880756e7a80 RCX: 0000000000040000 RDX: ffffc9000c6c4000 RSI: 0000000000031f9e RDI: 0000000000031f9f RBP: 0000000000000000 R08: ffffffff88c0f606 R09: ffffc900079e7520 R10: ffffed101011226d R11: 1ffff1101011226c R12: 1ffff1100eadcf50 R13: ffff8880756e72c0 R14: 1ffff1100eadcf89 R15: dffffc0000000000 FS: 00007f643236e700(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f1ab3f1e2a0 CR3: 0000000064fe7000 CR4: 00000000003506e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: tcp_clean_rtx_queue+0x223a/0x2da0 net/ipv4/tcp_input.c:3356 tcp_ack+0x1962/0x3c90 net/ipv4/tcp_input.c:3861 tcp_rcv_established+0x7c8/0x1ac0 net/ipv4/tcp_input.c:5973 tcp_v6_do_rcv+0x57b/0x1210 net/ipv6/tcp_ipv6.c:1476 sk_backlog_rcv include/net/sock.h:1061 [inline] __release_sock+0x1d8/0x4c0 net/core/sock.c:2849 release_sock+0x5d/0x1c0 net/core/sock.c:3404 sk_stream_wait_memory+0x700/0xdc0 net/core/stream.c:145 tcp_sendmsg_locked+0x111d/0x3fc0 net/ipv4/tcp.c:1410 tcp_sendmsg+0x2c/0x40 net/ipv4/tcp.c:1448 sock_sendmsg_nosec net/socket.c:714 [inline] sock_sendmsg net/socket.c:734 [inline] __sys_sendto+0x439/0x5c0 net/socket.c:2119 __do_sys_sendto net/socket.c:2131 [inline] __se_sys_sendto net/socket.c:2127 [inline] __x64_sys_sendto+0xda/0xf0 net/socket.c:2127 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x2b/0x70 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x46/0xb0 RIP: 0033:0x7f6431289109 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:00007f643236e168 EFLAGS: 00000246 ORIG_RAX: 000000000000002c RAX: ffffffffffffffda RBX: 00007f643139c100 RCX: 00007f6431289109 RDX: 00000000d0d0c2ac RSI: 0000000020000080 RDI: 000000000000000a RBP: 00007f64312e308d R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000001 R11: 0000000000000246 R12: 0000000000000000 R13: 00007fff372533af R14: 00007f643236e300 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.8% × 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.8%
EPSS %ILE
57th
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.8% 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

August 5, 2026

References (9)

Vendor Advisories for CVE-2022-49330(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 @ 4.9.318 (fixes >=2.6.17)—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 (14 versions)
  • every version up to 5.10.127-1: fixed in 5.10.127-1
—
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
—

Weakness Classification(1)

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

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 195 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 97 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2022-49330?
CVE-2022-49330 is a medium-severity vulnerability; its CVE record was published on February 26, 2025. In the Linux kernel, the following vulnerability has been resolved: tcp: fix tcp_mtup_probe_success vs wrong snd_cwnd syzbot got a new report [1] finally pointing to a very old bug, added in initial support for MTU probing. tcp_mtu_probe() has checks about starting an MTU probe if tcp_snd_cwnd(tp)…
When was the CVE record for CVE-2022-49330 published?
The CVE record for CVE-2022-49330 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 August 5, 2026; the record at its source may have been updated since.
Is CVE-2022-49330 actively exploited?
CVE-2022-49330 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (57th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-49330?
CVE-2022-49330 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2022-49330?
A fix for CVE-2022-49330 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-49330 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-49330

Explore →

Is Your Infrastructure Affected by CVE-2022-49330?

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

Book a Demo →Browse All CVEs