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
Trending — Patch released this weekElevated
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.8Exploit: Elevated riskExposed: 0

A fix is available — apply it.

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)
EG Risk
51(Track*)
EG Risk 51/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%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
1%
EPSS %ILE
53%
KEV
Not listed

Published

May 21, 2026

Last Modified

August 26, 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(20)

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

Patch Availability(25)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-08-26ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-08-26ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-08-26ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-08-26ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-08-26ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-26ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1059.62.1) @ noble2026-08-26ubuntu
redhatkpatch-patch2026-08-24redhat
redhatkernel-0:2.6.32-754.62.1.el62026-07-20redhat
redhatkernel-rt-0:3.10.0-1160.156.1.rt56.1308.el72026-07-17redhat
redhatkernel-0:3.10.0-1160.156.1.el72026-07-17redhat
redhatkernel-0:6.12.0-55.89.1.el10_02026-07-16redhat
redhatkernel-0:5.14.0-427.138.1.el9_42026-07-16redhat
redhatkernel-0:4.18.0-477.152.1.el8_82026-07-16redhat
redhatkernel-0:5.14.0-570.128.1.el9_62026-07-16redhat
redhatkernel-0:4.18.0-305.198.1.el8_42026-07-15redhat
redhatkernel-0:4.18.0-372.201.1.el8_62026-07-15redhat
redhatkernel-0:5.14.0-284.181.1.el9_22026-07-15redhat
redhatkernel-rt-0:5.14.0-284.181.1.rt14.466.el9_22026-07-15redhat
redhatkernel-0:4.18.0-553.143.1.el8_102026-07-14redhat
redhatkernel-rt-0:4.18.0-553.143.1.rt7.484.el8_102026-07-14redhat
redhatkernel-0:6.12.0-211.33.1.el10_22026-07-13redhat
redhatkernel-0:5.14.0-687.25.1.el9_82026-07-13redhat
redhatkernel-0:6.12.0-231.16.el10nv2026-07-10redhat
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.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (55 versions)5.10.262-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.86-1~bpo12+1 (19 versions)6.12.86-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.4-1~bpo13+1 (131 versions)7.0.4-1—

Weakness Classification(1)

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

Additional Vendor Advisories

(5)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

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

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

    CVE-2026-43499 full exploit chain for Samsung Galaxy S22 Ultra (Android 5.10 kernel)

    Open source ↗
  • GitHub PoCalex193a/Root-My-Pixel
    First seen Aug 2, 2026

    Jailbreak supported Google Pixel phones with CVE-2026-43499

    Open source ↗
  • GitHub PoCYuKongA/ghostlock-app
    First seen Jul 29, 2026

    GhostLock One-Tap Execution App (CVE-2026-43499)

    Open source ↗
  • GitHub PoCgagaltotal/CVE-2026-43499-PoC-Scanner
    First seen Jul 22, 2026

    CVE-2026-43499 PoC Scanner

    Open source ↗
  • GitHub PoCp2p3p/GhostLock-for-OnePlus
    First seen Jul 18, 2026

    （CVE-2026-43499）内核漏洞利用程序，适用于未解锁 Bootloader 的一加设备。

    Open source ↗
  • 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 ↗

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 August 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-43499 actively exploited?
CVE-2026-43499 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 47.0% of all scored CVEs.
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

See which npm, PyPI, Go, and Maven packages are affected by 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