CVE-2026-43408

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-08. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

ceph: add a bunch of missing ceph_path_info initializers

ceph_mdsc_build_path() must be called with a zero-initialized ceph_path_info parameter, or else the following ceph_mdsc_free_path_info() may crash.

Example crash (on Linux 6.18.12):

virt_to_cache: Object is not a Slab page! WARNING: CPU: 184 PID: 2871736 at mm/slub.c:6732 kmem_cache_free+0x316/0x400 [...] Call Trace: [...] ceph_open+0x13d/0x3e0 do_dentry_open+0x134/0x480 vfs_open+0x2a/0xe0 path_openat+0x9a3/0x1160 [...] cache_from_obj: Wrong slab cache. names_cache but object is from ceph_inode_info WARNING: CPU: 184 PID: 2871736 at mm/slub.c:6746 kmem_cache_free+0x2dd/0x400 [...] kernel BUG at mm/slub.c:634! Oops: invalid opcode: 0000 [#1] SMP NOPTI RIP: 0010:__slab_free+0x1a4/0x350

Some of the ceph_mdsc_build_path() callers had initializers, but others had not, even though they were all added by commit 15f519e9f883 ("ceph: fix race condition validating r_parent before applying state"). The ones without initializer are suspectible to random crashes. (I can imagine it could even be possible to exploit this bug to elevate privileges.)

Unfortunately, these Ceph functions are undocumented and its semantics can only be derived from the code. I see that ceph_mdsc_build_path() initializes the structure only on success, but not on error.

Calling ceph_mdsc_free_path_info() after a failed ceph_mdsc_build_path() call does not even make sense, but that's what all callers do, and for it to be safe, the structure must be zero-initialized. The least intrusive approach to fix this is therefore to add initializers everywhere.

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

Published

May 8, 2026

Last Modified

August 5, 2026

Advisory Details (4)

Auto-updated May 11, 2026
No patch confirmed yet.
generic

ceph: add a bunch of missing ceph_path_info initializers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8be8911f590813e6f90bc6407ced1b23e50bc5da
generic

ceph: add a bunch of missing ceph_path_info initializers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/644b47f0574fd82aeb9d00317eca8d1f2a525c8c
generic

ceph: add a bunch of missing ceph_path_info initializers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/453df1f4535842bf17ff1885a225e153d7ee3374
generic

ceph: add a bunch of missing ceph_path_info initializers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/43323a5934b660afae687e8e4e95ac328615a5c4

Vendor Advisories for CVE-2026-43408(1)

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

Patch Availability(15)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-6.8 (6.8.0-136.136) @ noble2026-08-23ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1064.72+fips1) @ noble2026-08-23ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1058.61) @ noble2026-08-23ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1059.62.1) @ noble2026-08-23ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-aws-fips-6.8 (6.8.0-1061.64+fips1) @ noble2026-08-23ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1033.34) @ noble2026-08-23ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2050.52) @ noble2026-08-23ubuntu
linuxKernel @ 6.12.78—osv

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

(2 across 2 ecosystems)
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 (119 versions)6.19.10-1—

Weakness Classification(1)

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

All Vendor Advisories

(14)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-43408?
CVE-2026-43408 is a high vulnerability published on May 8, 2026. In the Linux kernel, the following vulnerability has been resolved: ceph: add a bunch of missing cephpathinfo initializers cephmdscbuild_path() must be called with a zero-initialized cephpathinfo parameter, or else the following cephmdscfreepathinfo() may crash. Example crash (on Linux 6.18.12):…
When was CVE-2026-43408 disclosed?
CVE-2026-43408 was first published in the National Vulnerability Database on May 8, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43408 actively exploited?
CVE-2026-43408 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.1% of all scored CVEs.
What is the CVSS score of CVE-2026-43408?
CVE-2026-43408 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-43408?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43408, 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-43408

Explore →

Is Your Infrastructure Affected by CVE-2026-43408?

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

Start Free Scan →Browse All CVEs