CVE-2026-46137

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-05-28. a secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.8Exploit: NoneExposed: 0

A fix is available — apply it.

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

mptcp: pm: ADD_ADDR rtx: fix potential data-race

This mptcp_pm_add_timer() helper is executed as a timer callback in softirq context. To avoid any data races, the socket lock needs to be held with bh_lock_sock().

If the socket is in use, retry again soon after, similar to what is done with the keepalive timer.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

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
Severity98% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
34.9%
KEV
Not listed

Published

May 28, 2026

Last Modified

June 24, 2026

Advisory Details (8)

Auto-updated Jul 12, 2026
No patch confirmed yet.
generic

mptcp: pm: ADD_ADDR rtx: fix potential data-race - kernel/git/stable/linux.git - Linux kernel stable tree

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

mptcp: pm: ADD_ADDR rtx: fix potential data-race - kernel/git/stable/linux.git - Linux kernel stable tree

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

mptcp: pm: ADD_ADDR rtx: fix potential data-race - kernel/git/stable/linux.git - Linux kernel stable tree

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

mptcp: pm: ADD_ADDR rtx: fix potential data-race - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6e4710d7d8782cb61af29a7e7111ddfc38b9e1a3
generic

mptcp: pm: ADD_ADDR rtx: fix potential data-race - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5cd6e0ad79d2615264f63929f8b457ad97ae550d
generic

mptcp: pm: ADD_ADDR rtx: fix potential data-race - kernel/git/stable/linux.git - Linux kernel stable tree

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

mptcp: pm: ADD_ADDR rtx: fix potential data-race - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/23079e0b7742ec114d3507c3e3aad01b7b69e4af
generic

mptcp: pm: ADD_ADDR rtx: fix potential data-race - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/013dcdc1961543b9a3433466bc8c79a2f4ca75b5

Vendor Advisories for CVE-2026-46137(2)

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

Patch Availability(4)

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.

Weakness Classification(1)

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

Additional Vendor Advisories

(4)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 8× in last 7d / 101× 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 306 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-46137?
CVE-2026-46137 is a critical vulnerability published on May 28, 2026. In the Linux kernel, the following vulnerability has been resolved: mptcp: pm: ADD_ADDR rtx: fix potential data-race This mptcppmadd_timer() helper is executed as a timer callback in softirq context. To avoid any data races, the socket lock needs to be held with bhlocksock(). If the socket is in…
When was CVE-2026-46137 disclosed?
CVE-2026-46137 was first published in the National Vulnerability Database on May 28, 2026, with the most recent update on June 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46137 actively exploited?
CVE-2026-46137 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 34.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-46137?
CVE-2026-46137 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-46137?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46137, 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-46137

Explore →

Is Your Infrastructure Affected by CVE-2026-46137?

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