CVE-2026-89450 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.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-SLES1610-KERNELNVIDIA64KB-22591559
  • published18 Nov 2026
  • disclosed9 Nov 2026

Introduced: 9 Nov 2026

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

iommu/tegra241-cmdqv: Reject a vSID wider than the SID_MATCH field

tegra241_vintf_init_vsid() programs the guest-provided vSID into SID_MATCH, whose VIRT_SID field spans bits [20:1] with bit 0 as the match-enable flag. The HW therefore matches only a 20-bit Stream ID.

The bound check rejects only virt_sid > UINT_MAX, which admits a value far wider than the field. The write "virt_sid << 1 | 0x1" then drops every bit above 20: a virt_sid of 0x80000000 lands as SID_MATCH = 0x1, a valid match on vSID 0, so the entry aliases the wrong Stream ID. Because vdev->virt_id is guest-controlled, a VMM can trigger it.

Validate virt_sid against the field width with FIELD_MAX(), and program the register with FIELD_PREP() so the value and the field stay consistent.

CVSS Base Scores

version 3.1