CVE-2026-43499 Affecting gfs2-kmp-default package, versions <5.14.21-150400.24.222.1


Severity

Recommended
0.0
high
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.13% (3rd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-SLES154-GFS2KMPDEFAULT-17333661
  • published13 Jun 2026
  • disclosed12 Jun 2026

Introduced: 12 Jun 2026

NewCVE-2026-43499  (opens in a new tab)

How to fix?

Upgrade SLES:15.4 gfs2-kmp-default to version 5.14.21-150400.24.222.1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream gfs2-kmp-default package and not the gfs2-kmp-default package as distributed by SLES. See How to fix? for SLES:15.4 relevant fixed versions and status.

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 Base Scores

version 3.1