CVE-2026-46170

NVD 0.05.5▲
EchelonGraph scoreLOW confidence

Score 5.5 from GitHub Security Advisory published 2026-05-28.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa
Trending — 4 sources updated this week
0.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No confirmed exploitation signals yet
CISA-KEV: Not listedEPSS: 0%CVSS: —Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

mptcp: pm: ADD_ADDR rtx: free sk if last

When an ADD_ADDR is retransmitted, the sk is held in sk_reset_timer(), and released at the end.

If at that moment, it was the last reference being held, the sk would not be freed. sock_put() should then be called instead of __sock_put().

But that's not enough: if it is the last reference, sock_put() will call sk_free(), which will end up calling sk_stop_timer_sync() on the same timer, and waiting indefinitely to finish. So it is needed to mark that the timer is done at the end of the timer handler when it has not been rescheduled, not to call sk_stop_timer_sync() on "itself".

CVSS v3
—
EG Score
5.5(low)
EPSS
2.8%
KEV
Not listed

Published

May 28, 2026

Last Modified

June 14, 2026

References (5)

Vendor Advisories for CVE-2026-46170(2)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 71× 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 119 total refreshes for this CVE.

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

Frequently asked(4)

What is CVE-2026-46170?
CVE-2026-46170 is a publicly disclosed vulnerability published on May 28, 2026. In the Linux kernel, the following vulnerability has been resolved: mptcp: pm: ADD_ADDR rtx: free sk if last When an ADDADDR is retransmitted, the sk is held in skreset_timer(), and released at the end. If at that moment, it was the last reference being held, the sk would not be freed. sockput()…
When was CVE-2026-46170 disclosed?
CVE-2026-46170 was first published in the National Vulnerability Database on May 28, 2026, with the most recent update on June 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46170 actively exploited?
CVE-2026-46170 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2026-46170?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46170, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-46170

Explore →

Is Your Infrastructure Affected by CVE-2026-46170?

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

Start Free Scan →Browse All CVEs