CVE-2026-74678 Affecting kernel-nvidia64kb package, versions <6.12.0-160100.7.1


Severity

Recommended
0.0
medium
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.48% (40th 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-KERNELNVIDIA64KB-22591369
  • published18 Nov 2026
  • disclosed9 Nov 2026

Introduced: 9 Nov 2026

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

How to fix?

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

NVD Description

Note: Versions mentioned in the description apply only to the upstream kernel-nvidia64kb package and not the kernel-nvidia64kb 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:

net: usb: ax88179_178a: fix skb leak in ax88179_tx_fixup()

When the interface has NETIF_F_SG enabled and skb_linearize() fails in ax88179_tx_fixup(), the function returns NULL without freeing the skb.

usbnet_start_xmit() treats a NULL return from tx_fixup() as a drop (info->flags does not set FLAG_MULTI_PACKET for this driver), jumping to the "drop" label where it does if (skb) dev_kfree_skb_any(skb). Because tx_fixup() returned NULL, the local skb variable in usbnet_start_xmit() is NULL, so the original skb is never freed — a memory leak on every TX frame whose linearization fails (i.e. under memory pressure).

Free the skb before returning, matching the error handling already used for the pskb_expand_head() failure path in the same function.

CVSS Base Scores

version 3.1