CVE-2026-43419

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.5 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 98% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, 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

A fix is available — apply it.

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

ceph: fix memory leaks in ceph_mdsc_build_path()

Add __putname() calls to error code paths that did not free the "path" pointer obtained by __getname(). If ownership of this pointer is not passed to the caller via path_info.path, the function must free it before returning.

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
2%
KEV
Not listed

Published

May 8, 2026

Last Modified

May 22, 2026

Advisory Details (5)

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

ceph: fix memory leaks in ceph_mdsc_build_path() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/657dc653b06a3cc0282aea447a3f137fa94066a4
generic

ceph: fix memory leaks in ceph_mdsc_build_path() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5895d0164c84d7fec6abc198920c257f55c51899
generic

ceph: fix memory leaks in ceph_mdsc_build_path() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/13b8b9d6f59ef17fb96c298c3a0d62a8306950cc
generic

ceph: fix memory leaks in ceph_mdsc_build_path() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/097cd68f46686391a98f2618188f0cb7b7570de2
generic

ceph: fix memory leaks in ceph_mdsc_build_path() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/040d159a45ded7f33201421a81df0aa2a86e5a0b

Patch Availability(15)

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 rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (350 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (122 versions)6.19.10-1

Weakness Classification(1)

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

All Vendor Advisories

(14)

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-43419?
CVE-2026-43419 is a medium vulnerability published on May 8, 2026. In the Linux kernel, the following vulnerability has been resolved: ceph: fix memory leaks in cephmdscbuild_path() Add putname() calls to error code paths that did not free the "path" pointer obtained by getname(). If ownership of this pointer is not passed to the caller via path_info.path, the…
When was CVE-2026-43419 disclosed?
CVE-2026-43419 was first published in the National Vulnerability Database on May 8, 2026, with the most recent update on May 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43419 actively exploited?
CVE-2026-43419 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.7% of all scored CVEs.
What is the CVSS score of CVE-2026-43419?
CVE-2026-43419 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-43419?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43419, 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-43419

Explore →

Is Your Infrastructure Affected by CVE-2026-43419?

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