Bug 2480453 (CVE-2026-43499)
| Summary: | CVE-2026-43499 kernel: rtmutex: Use waiter::task instead of current in remove_waiter() | ||
|---|---|---|---|
| Product: | [Other] Security Response | Reporter: | OSIDB Bzimport <bzimport> |
| Component: | vulnerability | Assignee: | Product Security <prodsec-ir-bot> |
| Status: | NEW --- | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | unspecified | CC: | kevinxue, rhel-process-autobot, watson-tool-maintainers |
| Target Milestone: | --- | Keywords: | Security |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | --- | |
| Doc Text: |
A flaw was found in the Linux kernel. When the kernel's real-time mutex (rtmutex) component performs a specific operation called 'proxy-lock rollback' during futex requeue, it incorrectly handles task pointers. This can lead to a 'Use-After-Free' (UAF) vulnerability, where the system attempts to use memory that has already been released. A local attacker could potentially exploit this to gain elevated privileges or execute unauthorized code.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | --- | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Upstream advisory: https://lore.kernel.org/linux-cve-announce/2026052158-CVE-2026-43499-1294@gregkh/T This issue has been addressed in the following products: NVIDIA for RHEL 10 Via RHSA-2026:37728 https://access.redhat.com/errata/RHSA-2026:37728 This issue has been addressed in the following products: Red Hat Enterprise Linux 10 Via RHSA-2026:38492 https://access.redhat.com/errata/RHSA-2026:38492 This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2026:38491 https://access.redhat.com/errata/RHSA-2026:38491 This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2026:39082 https://access.redhat.com/errata/RHSA-2026:39082 This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2026:39083 https://access.redhat.com/errata/RHSA-2026:39083 This issue has been addressed in the following products: Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions Via RHSA-2026:39983 https://access.redhat.com/errata/RHSA-2026:39983 This issue has been addressed in the following products: Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support Red Hat Enterprise Linux 8.4 Extended Update Support Long-Life Add-On Via RHSA-2026:39984 https://access.redhat.com/errata/RHSA-2026:39984 This issue has been addressed in the following products: Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support Red Hat Enterprise Linux 8.6 Extended Update Support Long-Life Add-On Via RHSA-2026:40068 https://access.redhat.com/errata/RHSA-2026:40068 This issue has been addressed in the following products: Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions Via RHSA-2026:40082 https://access.redhat.com/errata/RHSA-2026:40082 This issue has been addressed in the following products: Red Hat Enterprise Linux 9.6 Extended Update Support Via RHSA-2026:40425 https://access.redhat.com/errata/RHSA-2026:40425 This issue has been addressed in the following products: Red Hat Enterprise Linux 8.8 Update Services for SAP Solutions Red Hat Enterprise Linux 8.8 Telecommunications Update Service Via RHSA-2026:40760 https://access.redhat.com/errata/RHSA-2026:40760 This issue has been addressed in the following products: Red Hat Enterprise Linux 10.0 Extended Update Support Via RHSA-2026:41062 https://access.redhat.com/errata/RHSA-2026:41062 This issue has been addressed in the following products: Red Hat Enterprise Linux 9.4 Update Services for SAP Solutions Via RHSA-2026:41063 https://access.redhat.com/errata/RHSA-2026:41063 This issue has been addressed in the following products: Red Hat Enterprise Linux 7 Extended Lifecycle Support Via RHSA-2026:41234 https://access.redhat.com/errata/RHSA-2026:41234 This issue has been addressed in the following products: Red Hat Enterprise Linux 7 Extended Lifecycle Support Via RHSA-2026:41235 https://access.redhat.com/errata/RHSA-2026:41235 This issue has been addressed in the following products: Red Hat Enterprise Linux 6 Extended Lifecycle Support - EXTENSION Via RHSA-2026:41920 https://access.redhat.com/errata/RHSA-2026:41920 This issue has been addressed in the following products: Red Hat Enterprise Linux 10 Via RHSA-2026:59143 https://access.redhat.com/errata/RHSA-2026:59143 This issue has been addressed in the following products: Red Hat Enterprise Linux 8.8 Update Services for SAP Solutions Via RHSA-2026:59142 https://access.redhat.com/errata/RHSA-2026:59142 This issue has been addressed in the following products: Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions Via RHSA-2026:59147 https://access.redhat.com/errata/RHSA-2026:59147 This issue has been addressed in the following products: Red Hat Enterprise Linux 9.4 Update Services for SAP Solutions Via RHSA-2026:59145 https://access.redhat.com/errata/RHSA-2026:59145 This issue has been addressed in the following products: Red Hat Enterprise Linux 9.6 Extended Update Support Via RHSA-2026:59148 https://access.redhat.com/errata/RHSA-2026:59148 This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2026:59149 https://access.redhat.com/errata/RHSA-2026:59149 This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2026:59146 https://access.redhat.com/errata/RHSA-2026:59146 This issue has been addressed in the following products: NVIDIA for RHEL 10 Via RHSA-2026:73187 https://access.redhat.com/errata/RHSA-2026:73187 |
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 ]