CVE-2026-45930

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-05-27. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 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:

net: mctp: ensure our nlmsg responses are initialised

Syed Faraz Abrar (@farazsth98) from Zellic, and Pumpkin (@u1f383) from DEVCORE Research Team working with Trend Micro Zero Day Initiative report that a RTM_GETNEIGH will return uninitalised data in the pad bytes of the ndmsg data.

Ensure we're initialising the netlink data to zero, in the link, addr and neigh response messages.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

May 27, 2026

Last Modified

June 25, 2026

Advisory Details (7)

Auto-updated Jun 26, 2026
No patch confirmed yet.
generic

net: mctp: ensure our nlmsg responses are initialised - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: mctp: ensure our nlmsg responses are initialised - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: mctp: ensure our nlmsg responses are initialised - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: mctp: ensure our nlmsg responses are initialised - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/976612471a9e6ead6ceffc241e4d0a1aac90b36a
generic

net: mctp: ensure our nlmsg responses are initialised - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/963537a26fd892f7e414a091f807b44aeee97a7d
generic

net: mctp: ensure our nlmsg responses are initialised - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: mctp: ensure our nlmsg responses are initialised - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/54ed418de62a148a655262da682a050fa05f7924

Vendor Advisories for CVE-2026-45930(2)

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

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (113 versions)6.19.6-1—

Data Freshness Timeline

(refreshed 5× in last 7d / 64× 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 195 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-45930?
CVE-2026-45930 is a medium vulnerability published on May 27, 2026. In the Linux kernel, the following vulnerability has been resolved: net: mctp: ensure our nlmsg responses are initialised Syed Faraz Abrar (@farazsth98) from Zellic, and Pumpkin (@u1f383) from DEVCORE Research Team working with Trend Micro Zero Day Initiative report that a RTM_GETNEIGH will return…
When was CVE-2026-45930 disclosed?
CVE-2026-45930 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on June 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45930 actively exploited?
CVE-2026-45930 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.3% of all scored CVEs.
What is the CVSS score of CVE-2026-45930?
CVE-2026-45930 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-45930?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45930, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-45930

Explore →

Is Your Infrastructure Affected by CVE-2026-45930?

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

Start Free Scan →Browse All CVEs