CVE-2022-49775

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2025-13006 (ENISA EUVD) · GHSA-52wf-qx53-m2m5 (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

tcp: cdg: allow tcp_cdg_release() to be called multiple times

Apparently, mptcp is able to call tcp_disconnect() on an already disconnected flow. This is generally fine, unless current congestion control is CDG, because it might trigger a double-free [1]

Instead of fixing MPTCP, and future bugs, we can make tcp_disconnect() more resilient.

[1] BUG: KASAN: double-free in slab_free mm/slub.c:3539 [inline] BUG: KASAN: double-free in kfree+0xe2/0x580 mm/slub.c:4567

CPU: 0 PID: 3645 Comm: kworker/0:7 Not tainted 6.0.0-syzkaller-02734-g0326074ff465 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022 Workqueue: events mptcp_worker Call Trace:

__dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106 print_address_description mm/kasan/report.c:317 [inline] print_report.cold+0x2ba/0x719 mm/kasan/report.c:433 kasan_report_invalid_free+0x81/0x190 mm/kasan/report.c:462 ____kasan_slab_free+0x18b/0x1c0 mm/kasan/common.c:356 kasan_slab_free include/linux/kasan.h:200 [inline] slab_free_hook mm/slub.c:1759 [inline] slab_free_freelist_hook+0x8b/0x1c0 mm/slub.c:1785 slab_free mm/slub.c:3539 [inline] kfree+0xe2/0x580 mm/slub.c:4567 tcp_disconnect+0x980/0x1e20 net/ipv4/tcp.c:3145 __mptcp_close_ssk+0x5ca/0x7e0 net/mptcp/protocol.c:2327 mptcp_do_fastclose net/mptcp/protocol.c:2592 [inline] mptcp_worker+0x78c/0xff0 net/mptcp/protocol.c:2627 process_one_work+0x991/0x1610 kernel/workqueue.c:2289 worker_thread+0x665/0x1080 kernel/workqueue.c:2436 kthread+0x2e4/0x3a0 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306

Allocated by task 3671: kasan_save_stack+0x1e/0x40 mm/kasan/common.c:38 kasan_set_track mm/kasan/common.c:45 [inline] set_alloc_info mm/kasan/common.c:437 [inline] ____kasan_kmalloc mm/kasan/common.c:516 [inline] ____kasan_kmalloc mm/kasan/common.c:475 [inline] __kasan_kmalloc+0xa9/0xd0 mm/kasan/common.c:525 kmalloc_array include/linux/slab.h:640 [inline] kcalloc include/linux/slab.h:671 [inline] tcp_cdg_init+0x10d/0x170 net/ipv4/tcp_cdg.c:380 tcp_init_congestion_control+0xab/0x550 net/ipv4/tcp_cong.c:193 tcp_reinit_congestion_control net/ipv4/tcp_cong.c:217 [inline] tcp_set_congestion_control+0x96c/0xaa0 net/ipv4/tcp_cong.c:391 do_tcp_setsockopt+0x505/0x2320 net/ipv4/tcp.c:3513 tcp_setsockopt+0xd4/0x100 net/ipv4/tcp.c:3801 mptcp_setsockopt+0x35f/0x2570 net/mptcp/sockopt.c:844 __sys_setsockopt+0x2d6/0x690 net/socket.c:2252 __do_sys_setsockopt net/socket.c:2263 [inline] __se_sys_setsockopt net/socket.c:2260 [inline] __x64_sys_setsockopt+0xba/0x150 net/socket.c:2260 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+0x63/0xcd

Freed by task 16: kasan_save_stack+0x1e/0x40 mm/kasan/common.c:38 kasan_set_track+0x21/0x30 mm/kasan/common.c:45 kasan_set_free_info+0x20/0x30 mm/kasan/generic.c:370 ____kasan_slab_free mm/kasan/common.c:367 [inline] ____kasan_slab_free+0x166/0x1c0 mm/kasan/common.c:329 kasan_slab_free include/linux/kasan.h:200 [inline] slab_free_hook mm/slub.c:1759 [inline] slab_free_freelist_hook+0x8b/0x1c0 mm/slub.c:1785 slab_free mm/slub.c:3539 [inline] kfree+0xe2/0x580 mm/slub.c:4567 tcp_cleanup_congestion_control+0x70/0x120 net/ipv4/tcp_cong.c:226 tcp_v4_destroy_sock+0xdd/0x750 net/ipv4/tcp_ipv4.c:2254 tcp_v6_destroy_sock+0x11/0x20 net/ipv6/tcp_ipv6.c:1969 inet_csk_destroy_sock+0x196/0x440 net/ipv4/inet_connection_sock.c:1157 tcp_done+0x23b/0x340 net/ipv4/tcp.c:4649 tcp_rcv_state_process+0x40e7/0x4990 net/ipv4/tcp_input.c:6624 tcp_v6_do_rcv+0x3fc/0x13c0 net/ipv6/tcp_ipv6.c:1525 tcp_v6_rcv+0x2e8e/0x3830 net/ipv6/tcp_ipv6.c:1759 ip6_protocol_deliver_rcu+0x2db/0x1950 net/ipv6/ip6_input.c:439 ip6_input_finish+0x14c/0x2c0 net/ipv6/ip6_input.c:484 NF_HOOK include/linux/netfilter.h:302 [inline] NF_HOOK include/linux/netfilter.h:296 [inline] ip6_input+0x9c/0xd ---truncated---

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/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)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 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.2%
EPSS %ILE
11th
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 (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). 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

May 1, 2025

Last Modified

August 5, 2026

Advisory Details (8)

Auto-updated Aug 4, 2026
Patch available.
Web page

tcp: cdg: allow tcp_cdg_release() to be called multiple times - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/72e560cb8c6f80fc2b4afc5d3634a32465e13a51
Web page

tcp: cdg: allow tcp_cdg_release() to be called multiple times - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1b639be27cbf428a5ca01dcf8b5d654194c956f8
Web page

tcp: cdg: allow tcp_cdg_release() to be called multiple times - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b49026d9c86f35a4c5bfb8d7345c9c4379828c6b
Web page

tcp: cdg: allow tcp_cdg_release() to be called multiple times - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/35309be06b6feded2ab2cafbc2bca8534c2fa41e
Web page

tcp: cdg: allow tcp_cdg_release() to be called multiple times - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/78be2ee0112409ae4e9ee9e326151e0559b3d239
Web page

tcp: cdg: allow tcp_cdg_release() to be called multiple times - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9e481d87349d2282f400ee1d010a169c99f766b8
Web page

tcp: cdg: allow tcp_cdg_release() to be called multiple times - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4026033907cc6186d86b48daa4a252c860db2536
Web page

tcp: cdg: allow tcp_cdg_release() to be called multiple times - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0b19171439016a8e4c97eafe543670ac86e2b8fe

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 4.9.334 (fixes >=4.2.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 (22 versions)
  • every version up to 5.10.158-1: fixed in 5.10.158-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.0.10-1: fixed in 6.0.10-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.0.10-1: fixed in 6.0.10-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.0.10-1: fixed in 6.0.10-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 39× 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 200 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 102 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.2% · 11th percentile
  2. 2026-11-01 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  3. 2026-10-31 16:29 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  4. 2026-10-30 16:31 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  5. 2026-10-29 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  6. 2026-10-28 16:28 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  7. 2026-10-28 04:52 UTCEG score recompute
  8. 2026-10-28 04:52 UTCGHSA enrichmentGHSA-52wf-qx53-m2m5 · GitHub severity HIGH · GitHub CVSS 7.8
  9. 2026-10-27 16:28 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  10. 2026-10-26 16:28 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  11. 2026-10-25 17:54 UTCEG score recompute
  12. 2026-10-25 16:29 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  13. 2026-10-24 16:29 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  14. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  15. 2026-10-22 16:30 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  16. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  17. 2026-10-21 05:35 UTCEG score recompute
  18. 2026-10-21 05:35 UTCGHSA enrichmentGHSA-52wf-qx53-m2m5 · GitHub severity HIGH · GitHub CVSS 7.8
  19. 2026-10-20 16:29 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  20. 2026-10-19 16:28 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  21. 2026-10-19 11:55 UTCOSV refresh
  22. 2026-10-18 16:29 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  23. 2026-10-18 08:19 UTCEG score recompute
  24. 2026-10-17 16:29 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  25. 2026-10-16 16:35 UTCEPSS rescoreEPSS 0.2% · 10th percentile
Show 73 more
  1. 2026-10-15 16:28 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  2. 2026-10-14 16:29 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  3. 2026-10-13 16:29 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  4. 2026-10-12 18:41 UTCEG score recompute
  5. 2026-10-12 16:30 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  6. 2026-10-11 22:05 UTCEG score recompute
  7. 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  8. 2026-10-10 19:57 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  9. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  10. 2026-10-08 17:05 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  11. 2026-10-07 23:45 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  12. 2026-10-06 15:14 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  13. 2026-10-05 17:40 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  14. 2026-10-04 23:19 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  15. 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  16. 2026-09-30 16:12 UTCEG score recompute
  17. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  18. 2026-09-27 13:42 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  19. 2026-09-26 19:03 UTCOSV refresh
  20. 2026-09-26 15:55 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  21. 2026-09-26 00:22 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  22. 2026-09-24 14:00 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  23. 2026-09-23 13:45 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  24. 2026-09-20 20:13 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  25. 2026-09-16 14:05 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  26. 2026-09-16 05:11 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  27. 2026-09-15 03:07 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  28. 2026-09-13 16:44 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  29. 2026-09-11 14:50 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  30. 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  31. 2026-09-08 21:57 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  32. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  33. 2026-09-07 04:18 UTCOSV refresh
  34. 2026-09-06 13:45 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  35. 2026-09-05 15:25 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  36. 2026-09-04 13:57 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  37. 2026-09-04 05:04 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  38. 2026-09-02 14:09 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  39. 2026-09-01 13:51 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  40. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  41. 2026-08-30 01:19 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  42. 2026-08-28 21:38 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  43. 2026-08-27 14:22 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  44. 2026-08-26 14:43 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  45. 2026-08-23 00:17 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  46. 2026-08-21 23:46 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  47. 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  48. 2026-08-20 14:01 UTCOSV refresh
  49. 2026-08-19 17:01 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  50. 2026-08-18 13:45 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  51. 2026-08-17 13:44 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  52. 2026-08-16 14:53 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  53. 2026-08-16 02:12 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  54. 2026-08-15 01:27 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  55. 2026-08-13 21:58 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  56. 2026-08-12 13:48 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  57. 2026-08-09 13:44 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  58. 2026-08-08 16:34 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  59. 2026-08-07 16:24 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  60. 2026-08-06 13:44 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  61. 2026-08-05 19:15 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  62. 2026-08-05 09:29 UTCEG score recompute
  63. 2026-08-05 09:29 UTCGHSA enrichmentGHSA-52wf-qx53-m2m5 · GitHub severity HIGH · GitHub CVSS 7.8
  64. 2026-08-04 15:07 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  65. 2026-08-04 11:05 UTCEG score recompute
  66. 2026-08-04 11:05 UTCGHSA enrichmentGHSA-52wf-qx53-m2m5 · GitHub severity HIGH · GitHub CVSS 7.8
  67. 2026-08-04 10:35 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  68. 2026-08-04 09:44 UTCEG score recompute
  69. 2026-08-04 09:44 UTCGHSA enrichmentGHSA-52wf-qx53-m2m5 · GitHub severity HIGH · GitHub CVSS 7.8
  70. 2026-08-03 10:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  71. 2026-08-02 02:24 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  72. 2026-08-01 04:13 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  73. 2026-07-30 16:25 UTCEPSS rescoreEPSS 0.2% · 8th percentile

Frequently asked(5)

What is CVE-2022-49775?
CVE-2022-49775 is a high-severity vulnerability; its CVE record was published on May 1, 2025. In the Linux kernel, the following vulnerability has been resolved: tcp: cdg: allow tcp_cdg_release() to be called multiple times Apparently, mptcp is able to call tcp_disconnect() on an already disconnected flow. This is generally fine, unless current congestion control is CDG, because it might…
When was the CVE record for CVE-2022-49775 published?
The CVE record for CVE-2022-49775 was published on May 1, 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-49775 actively exploited?
CVE-2022-49775 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (11th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-49775?
CVE-2022-49775 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2022-49775?
A fix for CVE-2022-49775 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-49775

Explore →

Is Your Infrastructure Affected by CVE-2022-49775?

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