CVE-2026-43416

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.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.5Exploit: NoneExposed: 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:

powerpc, perf: Check that current->mm is alive before getting user callchain

It may happen that mm is already released, which leads to kernel panic. This adds the NULL check for current->mm, similarly to commit 20afc60f892d ("x86, perf: Check that current->mm is alive before getting user callchain").

I was getting this panic when running a profiling BPF program (profile.py from bcc-tools):

[26215.051935] Kernel attempted to read user page (588) - exploit attempt? (uid: 0) [26215.051950] BUG: Kernel NULL pointer dereference on read at 0x00000588 [26215.051952] Faulting instruction address: 0xc00000000020fac0 [26215.051957] Oops: Kernel access of bad area, sig: 11 [#1] [...] [26215.052049] Call Trace: [26215.052050] [c000000061da6d30] [c00000000020fc10] perf_callchain_user_64+0x2d0/0x490 (unreliable) [26215.052054] [c000000061da6dc0] [c00000000020f92c] perf_callchain_user+0x1c/0x30 [26215.052057] [c000000061da6de0] [c0000000005ab2a0] get_perf_callchain+0x100/0x360 [26215.052063] [c000000061da6e70] [c000000000573bc8] bpf_get_stackid+0x88/0xf0 [26215.052067] [c000000061da6ea0] [c008000000042258] bpf_prog_16d4ab9ab662f669_do_perf_event+0xf8/0x274 [...]

In addition, move storing the top-level stack entry to generic perf_callchain_user to make sure the top-evel entry is always captured, even if current->mm is NULL.

[Maddy: fixed message to avoid checkpatch format style error]

CVSS v3
5.5
EG Score
5.5(medium)
EPSS
2.2%
KEV
Not listed

Published

May 8, 2026

Last Modified

May 26, 2026

Advisory Details (3)

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

powerpc, perf: Check that current->mm is alive before getting user callchain - kernel/git/stable/linux.git - Linux kernel stable tree

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

powerpc, perf: Check that current->mm is alive before getting user callchain - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/98074e16742ae87fb82e234b419783c5ffc9baea
generic

powerpc, perf: Check that current->mm is alive before getting user callchain - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7e5f60b8cfc02a2b23a40a5f5fd2fa81d010e737

Vendor Advisories for CVE-2026-43416(2)

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

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-43416?
CVE-2026-43416 is a medium vulnerability published on May 8, 2026. In the Linux kernel, the following vulnerability has been resolved: powerpc, perf: Check that current->mm is alive before getting user callchain It may happen that mm is already released, which leads to kernel panic. This adds the NULL check for current->mm, similarly to commit 20afc60f892d ("x86,…
When was CVE-2026-43416 disclosed?
CVE-2026-43416 was first published in the National Vulnerability Database on May 8, 2026, with the most recent update on May 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43416 actively exploited?
CVE-2026-43416 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-43416?
CVE-2026-43416 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-43416?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43416, 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

Explore the affected products and dependency analysis for CVE-2026-43416

Explore →

Is Your Infrastructure Affected by CVE-2026-43416?

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

Start Free Scan →Browse All CVEs