CVE-2026-43499

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-21. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Elevated
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: 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:

rtmutex: Use waiter::task instead of current in remove_waiter()

remove_waiter() is used by the slowlock paths, but it is also used for proxy-lock rollback in rt_mutex_start_proxy_lock() when invoked from futex_requeue().

In the latter case waiter::task is not current, but remove_waiter() operates on current for the dequeue operation. That results in several problems:

1) the rbtree dequeue happens without waiter::task::pi_lock being held

2) the waiter task's pi_blocked_on state is not cleared, which leaves a dangling pointer primed for UAF around.

3) rt_mutex_adjust_prio_chain() operates on the wrong top priority waiter task

Use waiter::task instead of current in all related operations in remove_waiter() to cure those problems.

[ tglx: Fixup rt_mutex_adjust_prio_chain(), add a comment and amend the changelog ]

CVSS v3
7.8
EG Score
7.8(medium)
EPSS
2.6%
KEV
Not listed

Published

May 21, 2026

Last Modified

July 8, 2026

Advisory Details (6)

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

rtmutex: Use waiter::task instead of current in remove_waiter() - kernel/git/stable/linux.git - Linux kernel stable tree

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

rtmutex: Use waiter::task instead of current in remove_waiter() - kernel/git/stable/linux.git - Linux kernel stable tree

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

rtmutex: Use waiter::task instead of current in remove_waiter() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/88614876370aac8ad1050ad785a4c095ba17ac11
generic

rtmutex: Use waiter::task instead of current in remove_waiter() - kernel/git/stable/linux.git - Linux kernel stable tree

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

rtmutex: Use waiter::task instead of current in remove_waiter() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3fb7394a837740770f0d6b4b30567e60786a63f2
generic

rtmutex: Use waiter::task instead of current in remove_waiter() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3bfdc63936dd4773109b7b8c280c0f3b5ae7d349

Vendor Advisories for CVE-2026-43499(17)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.1.175—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.

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Publicly available exploits

(10 references)

Working exploit code is in the public domain (10 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCBuSung-dev/Root-My-Galaxy
    First seen Jul 17, 2026

    KSU installer for supported Samsung Galaxy firmware with CVE-2026-43499

    Open source ↗
  • GitHub PoCBuSung-dev/CVE-2026-43499-S25U
    First seen Jul 16, 2026

    Galaxy S25 Ultra SM-S938N S938NKSUACZF1 port of CVE-2026-43499

    Open source ↗
  • GitHub PoCColorful-glassblock/duchamp-root
    First seen Jul 15, 2026

    Xiaomi K70e (duchamp) one-click root via CVE-2026-43499 (IonStack) + KernelSU integration

    Open source ↗
  • GitHub PoCLinuxoid-cn/CVE-2026-43499-Poc-Analysis
    First seen Jul 14, 2026

    Vulnerability analysis and Proof of Concept (PoC) for CVE-2026-43499 affecting Xiaomi devices. For educational and research purposes only.

    Open source ↗
  • GitHub PoCjoehquak/Mi8E5-Unlocker-by-CVE-2026-43499
    First seen Jul 13, 2026

    Multi OS Support: Version for MacOS/Linux and Windows, Fully translated to English

    Open source ↗
  • GitHub PoCCakesTwix/Android-CVE-2026-43499
    First seen Jul 13, 2026

    Android version CVE-2026-43499 tester

    Open source ↗
  • GitHub PoCYakayna/SpringPeace
    First seen Jul 13, 2026

    (Hopefully) A tool to root for (most) Android devices through CVE-2026-43499

    Open source ↗
  • GitHub PoCLinuxoid-cn/Mi8E5-Unlocker-by-CVE-2026-43499
    First seen Jul 12, 2026

    基于 CVE-2026-43499 的 8E5 机型自动化解锁辅助工具，仅限授权安全研究与自有设备使用。

    Open source ↗
  • GitHub PoCJoinChang/ghostlock-oneplus
    First seen Jul 12, 2026

    GhostLock (CVE-2026-43499) kernel exploit for OnePlus devices with locked bootloader

    Open source ↗
  • GitHub PoCx-spy/CVE-2026-43499-popsicle
    First seen Jul 12, 2026

    CVE-2026-43499 Implementation for 6.12.23-android16-5-g75e9b1c7ae7c-abogki463945075-4k

    Open source ↗

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-43499?
CVE-2026-43499 is a high vulnerability published on May 21, 2026. In the Linux kernel, the following vulnerability has been resolved: rtmutex: Use waiter::task instead of current in remove_waiter() remove_waiter() is used by the slowlock paths, but it is also used for proxy-lock rollback in rtmutexstartproxylock() when invoked from futex_requeue(). In the latter…
When was CVE-2026-43499 disclosed?
CVE-2026-43499 was first published in the National Vulnerability Database on May 21, 2026, with the most recent update on July 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43499 actively exploited?
CVE-2026-43499 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-43499?
CVE-2026-43499 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-43499?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43499, 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-43499

Explore →

Is Your Infrastructure Affected by CVE-2026-43499?

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

Start Free Scan →Browse All CVEs