CVE-2026-74534 Affecting kernel-azure-vdso package, versions <6.12.0-160000.38.1


Severity

Recommended
0.0
medium
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.38% (29th 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-SLES1600-KERNELAZUREVDSO-20331663
  • published30 Sept 2026
  • disclosed22 Sept 2026

Introduced: 22 Sep 2026

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

How to fix?

Upgrade SLES:16.0.0 kernel-azure-vdso to version 6.12.0-160000.38.1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kernel-azure-vdso package and not the kernel-azure-vdso package as distributed by SLES. See How to fix? for SLES:16.0.0 relevant fixed versions and status.

In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: ISO: fix refcounting of iso_conn

iso_conn_del() and iso_chan_del() have a race that results to double-put of iso_conn:

[Task hdev-&gt;workqueue]         [Task 2]
iso_conn_del                   iso_chan_del
  iso_conn_hold_unless_zero      iso_conn_lock
  iso_conn_lock                  conn-&gt;sk = NULL
                                 iso_conn_unlock
  sk = iso_sock_hold(conn)  &lt;---------´
  if (!sk) iso_conn_put          iso_conn_put
  iso_conn_put /* UAF */

The extra put for !sk in iso_conn_del() is currently required since failing iso_chan_add() may leave iso_conn not associated with any sk.

Fix by having iso_pi(sk)->conn own refcount when non-NULL, so iso_conn_del does not need to put it. Adjust the iso_conn_add() refcounting so that conn is put if it does not get associated with an sk.

CVSS Base Scores

version 3.1