CVE-2026-74325 Affecting kernel-nvidia64kb-devel package, versions <6.12.0-160100.6.1


Severity

Recommended
0.0
medium
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.17% (6th 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-SLES1610-KERNELNVIDIA64KBDEVEL-22595083
  • published18 Nov 2026
  • disclosed29 Oct 2026

Introduced: 29 Oct 2026

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

How to fix?

Upgrade SLES:16.1.0 kernel-nvidia64kb-devel to version 6.12.0-160100.6.1 or higher.

NVD Description

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

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

wifi: mt76: use kfree_rcu for offchannel link in mt76_put_vif_phy_link

mt76_put_vif_phy_link() frees the offchannel mlink with plain kfree() after rcu_assign_pointer(NULL). However, rcu_assign_pointer only prevents future RCU readers from obtaining the pointer -- it does not wait for existing readers that already hold it via rcu_dereference.

The TX datapath (e.g. mt7996_mac_write_txwi) dereferences mlink->wcid and mlink->idx under rcu_read_lock. If a TX softirq obtained the pointer via rcu_dereference just before the NULL assignment, it will dereference freed memory after the kfree.

struct mt76_vif_link already contains an rcu_head field that is unused at this free site -- a developer oversight, since the adjacent kfree_rcu_mightsleep call for rx_sc in the same function shows the pattern was understood.

Replace kfree(mlink) with kfree_rcu(mlink, rcu_head).

CVSS Base Scores

version 3.1