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


Severity

Recommended
0.0
high
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.21% (12th 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-22593067
  • published18 Nov 2026
  • disclosed9 Nov 2026

Introduced: 9 Nov 2026

NewCVE-2026-90319  (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:

rapidio: clear mport->net when rio_add_net() fails

rio_alloc_net() stores the newly allocated rio_net in mport->net before rio_scan_alloc_net() registers the device.

If rio_add_net() fails, rio_scan_alloc_net() drops the device reference with put_device(), which releases the rio_net through the device release callback. However, mport->net is left pointing at the freed object.

A later mport unregister path can then dereference the dangling mport->net pointer and may try to free the same rio_net again.

Clear mport->net in the rio_add_net() failure path, matching the cleanup done for the destID table allocation failure path.

CVSS Base Scores

version 3.1