iommu/tegra241-cmdqv: Reject a vSID wider than the SID_MATCH field
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.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.18.50, 7.2.4
- CVEs
- CVE-2026-89450
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 8 Nov 2026, 00:21 UTC · Revision 1
Source evidence
iommu/tegra241-cmdqv: Reject a vSID wider than the SID_MATCH field
core-osv · Original sourcePublished 11 Sept 2026, 19:43 UTC
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.
osv:CVE-2026-89450
Kernel
Fixed versions: 6.18.50, 7.2.4
Complete source record
{
"id": "40d19c53a350838d851bc110ee1f80294d71186ed7958abf61c0d48eed159d78",
"url": "https://osv.dev/vulnerability/CVE-2026-89450",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "iommu/tegra241-cmdqv: Reject a vSID wider than the SID_MATCH field",
"summary": "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.",
"evidence": "osv:CVE-2026-89450",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.18.50",
"evidence": "/affected/1/ranges"
},
{
"value": "7.2.4",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "high",
"structured": {
"id": "CVE-2026-89450",
"aliases": [
"CVE-2026-89450"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "4dc0d12474f9d4833c3dd96b73d61e406d3f5dc7"
},
{
"fixed": "d903d99ffd22b0180bd745a43f221c21bcdd8d7c"
},
{
"fixed": "445204550f894ca325ac80a21e3df177ad073798"
},
{
"fixed": "4379610c79bd88ddbea10e7f6c21e16d4b338c6b"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-89450.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.17.0"
},
{
"fixed": "6.18.50"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "7.2.4"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-89450.json"
}
}
],
"modified": "2026-10-28T02:30:52.042880897Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/4379610c79bd88ddbea10e7f6c21e16d4b338c6b",
"https://git.kernel.org/stable/c/445204550f894ca325ac80a21e3df177ad073798",
"https://git.kernel.org/stable/c/d903d99ffd22b0180bd745a43f221c21bcdd8d7c",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/89xxx/CVE-2026-89450.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-89450",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/89xxx/CVE-2026-89450.json"
}
},
"related_cves": [
{
"value": "CVE-2026-89450",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 520927,
"published_at": "2026-09-11T19:43:16.06+00:00"
}