CVE-2026-43409

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-05-08. 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

A fix is available — apply it.

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

kprobes: avoid crash when rmmod/insmod after ftrace killed

After we hit ftrace is killed by some errors, the kernel crash if we remove modules in which kprobe probes.

BUG: unable to handle page fault for address: fffffbfff805000d PGD 817fcc067 P4D 817fcc067 PUD 817fc8067 PMD 101555067 PTE 0 Oops: Oops: 0000 [#1] SMP KASAN PTI CPU: 4 UID: 0 PID: 2012 Comm: rmmod Tainted: G W OE Tainted: [W]=WARN, [O]=OOT_MODULE, [E]=UNSIGNED_MODULE RIP: 0010:kprobes_module_callback+0x89/0x790 RSP: 0018:ffff88812e157d30 EFLAGS: 00010a02 RAX: 1ffffffff805000d RBX: dffffc0000000000 RCX: ffffffff86a8de90 RDX: ffffed1025c2af9b RSI: 0000000000000008 RDI: ffffffffc0280068 RBP: 0000000000000000 R08: 0000000000000001 R09: ffffed1025c2af9a R10: ffff88812e157cd7 R11: 205d323130325420 R12: 0000000000000002 R13: ffffffffc0290488 R14: 0000000000000002 R15: ffffffffc0280040 FS: 00007fbc450dd740(0000) GS:ffff888420331000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: fffffbfff805000d CR3: 000000010f624000 CR4: 00000000000006f0 Call Trace: notifier_call_chain+0xc6/0x280 blocking_notifier_call_chain+0x60/0x90 __do_sys_delete_module.constprop.0+0x32a/0x4e0 do_syscall_64+0x5d/0xfa0 entry_SYSCALL_64_after_hwframe+0x76/0x7e

This is because the kprobe on ftrace does not correctly handles the kprobe_ftrace_disabled flag set by ftrace_kill().

To prevent this error, check kprobe_ftrace_disabled in __disarm_kprobe_ftrace() and skip all ftrace related operations.

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 21, 2026

Advisory Details (5)

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

kprobes: avoid crash when rmmod/insmod after ftrace killed - kernel/git/stable/linux.git - Linux kernel stable tree

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

kprobes: avoid crash when rmmod/insmod after ftrace killed - kernel/git/stable/linux.git - Linux kernel stable tree

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

kprobes: avoid crash when rmmod/insmod after ftrace killed - kernel/git/stable/linux.git - Linux kernel stable tree

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

kprobes: avoid crash when rmmod/insmod after ftrace killed - kernel/git/stable/linux.git - Linux kernel stable tree

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

kprobes: avoid crash when rmmod/insmod after ftrace killed - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8b6767e4141b2a42745b544d4555cf1614ba1a2d

Vendor Advisories for CVE-2026-43409(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)

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~rc5-1~exp1 (335 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 (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)

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-43409?
CVE-2026-43409 is a medium vulnerability published on May 8, 2026. In the Linux kernel, the following vulnerability has been resolved: kprobes: avoid crash when rmmod/insmod after ftrace killed After we hit ftrace is killed by some errors, the kernel crash if we remove modules in which kprobe probes. BUG: unable to handle page fault for address: fffffbfff805000d…
When was CVE-2026-43409 disclosed?
CVE-2026-43409 was first published in the National Vulnerability Database on May 8, 2026, with the most recent update on May 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43409 actively exploited?
CVE-2026-43409 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.8% of all scored CVEs.
What is the CVSS score of CVE-2026-43409?
CVE-2026-43409 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-43409?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43409, 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-43409

Explore →

Is Your Infrastructure Affected by CVE-2026-43409?

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