CVSS 3.1
8.2 highCVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:HHigh (8.2) in linux linux. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:HExplain CVE-2026-74355 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-74355?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-74355?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-74355 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Linux | 6.15 and later |
| Product | Release line | Fixed in |
|---|---|---|
| Linux | 6.18 | 6.18.40 |
| Linux | 7.1 | 7.1.5 |
| Linux | later releases | 7.2 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 14 | linux | 7.1.5-1 | DEBIAN-CVE-2026-74355 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2026-74355 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-hwe, linux-oem and 12 more | no fix listed | UBUNTU-CVE-2026-74355 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-riscv and 26 more | no fix listed | UBUNTU-CVE-2026-74355 |
| Ubuntu | 22.04:LTS | linux-riscv, linux-aws-6.2, linux-aws-6.5 and 30 more | no fix listed | UBUNTU-CVE-2026-74355 |
| Ubuntu | 24.04:LTS | linux-aws-7.0, linux-gcp-7.0 | 7.0.0-1014.14~24.04.1 | UBUNTU-CVE-2026-74355 USN-8887-2 USN-8887-3 |
| Ubuntu | 24.04:LTS | linux-azure-7.0 | 7.0.0-1017.17~24.04.1 | UBUNTU-CVE-2026-74355 USN-8888-2 |
| Ubuntu | 24.04:LTS | linux-azure-fde-7.0 | 7.0.0-1016.16~24.04.1 | UBUNTU-CVE-2026-74355 USN-8888-2 |
| Ubuntu | 24.04:LTS | linux-hwe-7.0 | 7.0.0-38.38~24.04.4 | UBUNTU-CVE-2026-74355 USN-8887-3 |
| Ubuntu | 24.04:LTS | linux-nvidia-7.0 | 7.0.0-1024.25~24.04.1 | UBUNTU-CVE-2026-74355 USN-9003-1 |
| Ubuntu | 24.04:LTS | linux-oracle-7.0 | 7.0.0-1013.13~24.04.1 | UBUNTU-CVE-2026-74355 USN-8887-3 |
| Ubuntu | 24.04:LTS | linux-riscv, linux-oem-6.8, linux-aws-6.14 and 25 more | no fix listed | UBUNTU-CVE-2026-74355 |
| Ubuntu | 24.04:LTS | linux-riscv-7.0 | 7.0.0-38.38.1~24.04.1 | UBUNTU-CVE-2026-74355 |
| 12 more for Ubuntu in the JSON and on Ubuntu's page. | ||||
| Alpaquita | stream | linux-lts | 6.18.43-r0 | BELL-CVE-2026-74355 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Alpaquita.
Red Hat rates this Moderate.
A moderate severity flaw was found in the Linux kernel's Intel VT-d IOMMU driver (iommu/vt-d). The info->node RB-tree member is zero-initialized via kzalloc; when a device does not support Address Translation Services (ATS), device_rbtree_insert() is skipped, and if a subsequent device probe step fails, the error path calls device_rbtree_remove(), which misinterprets the zeroed node as a tree root and corrupts the IOMMU device RB-tree. Exploitation requires local privileged access on an Intel VT-d platform together with specific conditions (a device without ATS whose probe fails), and the verified consequence is corruption of kernel data structures leading to system instability or a denial of service. Red Hat rated this flaw Moderate (CVSS 3.1 score 5.5, AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H), which is lower than the upstream CVE.org Important rating of 8.2, because the issue is local, requires privileges, and primarily affects system availability rather than confidentiality or integrity. Red Hat Enterprise Linux 9 and 10 streams that contain the vulnerable code (RHEL 9.8.z, RHEL 9.9, RHEL 10.2.z, and RHEL 10.3 kernel and kernel-rt, and Red Hat In-Vehicle OS 2.0 and 2.1 kernels) are affected; the fix for these streams is currently deferred to a future update, so the residual risk remains a local denial of service on affected systems. Earlier RHEL 6, 7, 8, and earlier RHEL 9 and 10 update streams do not contain the vulnerable code and are therefore not affected.
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | kernel | Fix deferred | |
| Red Hat Enterprise Linux 6 | kernel | Not affected | |
| Red Hat Enterprise Linux 7 | kernel | Not affected | |
| Red Hat Enterprise Linux 7 | kernel-rt | Not affected | |
| Red Hat Enterprise Linux 8 | kernel | Not affected | |
| Red Hat Enterprise Linux 8 | kernel-rt | Not affected | |
| Red Hat Enterprise Linux 9 | kernel | Fix deferred | |
| Red Hat Enterprise Linux 9 | kernel-rt | Not affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-74355.