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
Trending — 4 sources updated this week
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)
EPSS
34.5%
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)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-27.27) @ resolute2026-07-16ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1013.13) @ resolute2026-07-16ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1008.8) @ resolute2026-07-16ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1014.14) @ resolute2026-07-16ubuntu

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 16× in last 7d / 175× 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 443 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

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.5% 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.

Start Free Scan →Browse All CVEs