CVE-2026-43407

CRITICALNVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

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

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

A fix is available — apply it.

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

libceph: Fix potential out-of-bounds access in ceph_handle_auth_reply()

This patch fixes an out-of-bounds access in ceph_handle_auth_reply() that can be triggered by a message of type CEPH_MSG_AUTH_REPLY. In ceph_handle_auth_reply(), the value of the payload_len field of such a message is stored in a variable of type int. A value greater than INT_MAX leads to an integer overflow and is interpreted as a negative value. This leads to decrementing the pointer address by this value and subsequently accessing it because ceph_decode_need() only checks that the memory access does not exceed the end address of the allocation.

This patch fixes the issue by changing the data type of payload_len to u32. Additionally, the data type of result_msg_len is changed to u32, as it is also a variable holding a non-negative length.

Also, an additional layer of sanity checks is introduced, ensuring that directly after reading it from the message, payload_len and result_msg_len are not greater than the overall segment length.

BUG: KASAN: slab-out-of-bounds in ceph_handle_auth_reply+0x642/0x7a0 [libceph] Read of size 4 at addr ffff88811404df14 by task kworker/20:1/262

CPU: 20 UID: 0 PID: 262 Comm: kworker/20:1 Not tainted 6.19.2 #5 PREEMPT(voluntary) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Workqueue: ceph-msgr ceph_con_workfn [libceph] Call Trace: dump_stack_lvl+0x76/0xa0 print_report+0xd1/0x620 ? __pfx__raw_spin_lock_irqsave+0x10/0x10 ? kasan_complete_mode_report_info+0x72/0x210 kasan_report+0xe7/0x130 ? ceph_handle_auth_reply+0x642/0x7a0 [libceph] ? ceph_handle_auth_reply+0x642/0x7a0 [libceph] __asan_report_load_n_noabort+0xf/0x20 ceph_handle_auth_reply+0x642/0x7a0 [libceph] mon_dispatch+0x973/0x23d0 [libceph] ? apparmor_socket_recvmsg+0x6b/0xa0 ? __pfx_mon_dispatch+0x10/0x10 [libceph] ? __kasan_check_write+0x14/0x30i ? mutex_unlock+0x7f/0xd0 ? __pfx_mutex_unlock+0x10/0x10 ? __pfx_do_recvmsg+0x10/0x10 [libceph] ceph_con_process_message+0x1f1/0x650 [libceph] process_message+0x1e/0x450 [libceph] ceph_con_v2_try_read+0x2e48/0x6c80 [libceph] ? __pfx_ceph_con_v2_try_read+0x10/0x10 [libceph] ? save_fpregs_to_fpstate+0xb0/0x230 ? raw_spin_rq_unlock+0x17/0xa0 ? finish_task_switch.isra.0+0x13b/0x760 ? __switch_to+0x385/0xda0 ? __kasan_check_write+0x14/0x30 ? mutex_lock+0x8d/0xe0 ? __pfx_mutex_lock+0x10/0x10 ceph_con_workfn+0x248/0x10c0 [libceph] process_one_work+0x629/0xf80 ? __kasan_check_write+0x14/0x30 worker_thread+0x87f/0x1570 ? __pfx__raw_spin_lock_irqsave+0x10/0x10 ? __pfx_try_to_wake_up+0x10/0x10 ? kasan_print_address_stack_frame+0x1f7/0x280 ? __pfx_worker_thread+0x10/0x10 kthread+0x396/0x830 ? __pfx__raw_spin_lock_irq+0x10/0x10 ? __pfx_kthread+0x10/0x10 ? __kasan_check_write+0x14/0x30 ? recalc_sigpending+0x180/0x210 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x3f7/0x610 ? __pfx_ret_from_fork+0x10/0x10 ? __switch_to+0x385/0xda0 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30

[ idryomov: replace if statements with ceph_decode_need() for payload_len and result_msg_len ]

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
46(Track)
EG Risk 46/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
Severity91% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
43%
KEV
Not listed

Published

May 8, 2026

Last Modified

August 5, 2026

Advisory Details (8)

Auto-updated Aug 29, 2026
No patch confirmed yet.
generic

libceph: Fix potential out-of-bounds access in ceph_handle_auth_reply() - kernel/git/stable/linux.git - Linux kernel stable tree

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

libceph: Fix potential out-of-bounds access in ceph_handle_auth_reply() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9f9e2297f45fc2d2524eb104c289d69ddef95665
generic

libceph: Fix potential out-of-bounds access in ceph_handle_auth_reply() - kernel/git/stable/linux.git - Linux kernel stable tree

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

libceph: Fix potential out-of-bounds access in ceph_handle_auth_reply() - kernel/git/stable/linux.git - Linux kernel stable tree

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

libceph: Fix potential out-of-bounds access in ceph_handle_auth_reply() - kernel/git/stable/linux.git - Linux kernel stable tree

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

libceph: Fix potential out-of-bounds access in ceph_handle_auth_reply() - kernel/git/stable/linux.git - Linux kernel stable tree

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

libceph: Fix potential out-of-bounds access in ceph_handle_auth_reply() - kernel/git/stable/linux.git - Linux kernel stable tree

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

libceph: Fix potential out-of-bounds access in ceph_handle_auth_reply() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ea080b21092590122c3f971cf588932cdbf47847

Vendor Advisories for CVE-2026-43407(1)

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

Patch Availability(31)

Vendor / EcosystemFixed in / PatchReleasedSource
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-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1116.101) @ jammy2026-08-23ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.4.0-1079 (5.4.0-1079.83) @ focal2026-08-23ubuntu
ubuntulinux-tools-ibm-lts-20.04 (5.4.0.1107.136) @ focal2026-08-23ubuntu
ubuntulinux-tools-kvm-5.4 (5.4.0.1148.144) @ focal2026-08-23ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-raspi2-hwe-18.04-edge (5.4.0.1144.175) @ focal2026-08-23ubuntu
ubuntulinux-tools-azure (4.15.0.1205.220~14.04.1) @ trusty2026-08-23ubuntu
ubuntulinux-virtual-hwe-16.04-edge (4.15.0.254.266~16.04.1) @ xenial2026-08-23ubuntu
ubuntulinux-tools-aws-hwe (4.15.0.1195.208~16.04.1) @ xenial2026-08-23ubuntu
ubuntulinux-virtual-lts-xenial (4.4.0.283.289) @ xenial2026-08-23ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.17.0-40.40) @ questing2026-08-23ubuntu
ubuntulinux-tools-oem-6.17 (6.17.0-1028.28) @ noble2026-08-23ubuntu
ubuntulinux-virtual-6.8 (6.8.0-134.134) @ noble2026-08-23ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.185.166) @ jammy2026-08-23ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1058.61.1) @ noble2026-08-23ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1029.30) @ noble2026-08-23ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-134.134.1) @ noble2026-08-23ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1032.33) @ noble2026-08-23ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1108.114~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-virtual (3.13.0.214.224) @ trusty2026-08-23ubuntu
ubuntulinux-tools-nvidia-hwe-24.04 (6.17.0-1026.26) @ noble2026-08-23ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2049.50) @ noble2026-08-23ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.17.0-1017.19) @ questing2026-08-23ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1060.64) @ noble2026-08-23ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-134.134+fips1) @ noble2026-08-23ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1105.103) @ jammy2026-08-23ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1074 (5.15.0-1074.78) @ jammy2026-08-23ubuntu
linuxKernel @ 5.10.253—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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (53 versions)5.10.257-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1—
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

(25)

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

Frequently asked(5)

What is CVE-2026-43407?
CVE-2026-43407 is a critical vulnerability published on May 8, 2026. In the Linux kernel, the following vulnerability has been resolved: libceph: Fix potential out-of-bounds access in cephhandleauth_reply() This patch fixes an out-of-bounds access in cephhandleauth_reply() that can be triggered by a message of type CEPHMSGAUTH_REPLY. In cephhandleauthreply(), the…
When was CVE-2026-43407 disclosed?
CVE-2026-43407 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-43407 actively exploited?
CVE-2026-43407 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 56.7% of all scored CVEs.
What is the CVSS score of CVE-2026-43407?
CVE-2026-43407 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-43407?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43407, 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-43407

Explore →

Is Your Infrastructure Affected by CVE-2026-43407?

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

Start Free Scan →Browse All CVEs