CVSS 3.1
7.8 highCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HHigh (7.8) in linux linux. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExplain CVE-2026-74670 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-74670?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-74670?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-74670 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.2 and later |
| Product | Release line | Fixed in |
|---|---|---|
| Linux | 6.6 | 6.6.152 |
| Linux | 6.12 | 6.12.104 |
| Linux | 6.18 | 6.18.45 |
| Linux | 7.1 | 7.1.9 |
| Linux | later releases | 7.2 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12 | linux-6.12 | 6.12.107-1~deb12u1 | DEBIAN-CVE-2026-74670 |
| Debian | 13 | linux | 6.12.105-1 | DEBIAN-CVE-2026-74670 |
| Debian | 14 | linux | 7.1.9-1 | DEBIAN-CVE-2026-74670 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2026-74670 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-hwe, linux-oem and 12 more | no fix listed | UBUNTU-CVE-2026-74670 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-riscv and 26 more | no fix listed | UBUNTU-CVE-2026-74670 |
| Ubuntu | 22.04:LTS | linux-aws-6.8 | 6.8.0-1069.74~22.04.1 | UBUNTU-CVE-2026-74670 USN-9024-1 |
| Ubuntu | 22.04:LTS | linux-azure-6.8 | 6.8.0-1073.82~22.04.1 | UBUNTU-CVE-2026-74670 USN-9026-1 |
| Ubuntu | 22.04:LTS | linux-azure-fde-6.8 | 6.8.0-1071.78~22.04.1 | UBUNTU-CVE-2026-74670 USN-9026-1 |
| Ubuntu | 22.04:LTS | linux-gcp-6.8 | 6.8.0-1073.81~22.04.1 | UBUNTU-CVE-2026-74670 USN-9024-1 |
| Ubuntu | 22.04:LTS | linux-hwe-6.8 | 6.8.0-149.149~22.04.1 | UBUNTU-CVE-2026-74670 USN-9066-1 |
| Ubuntu | 22.04:LTS | linux-ibm-6.8 | 6.8.0-1069.70~22.04.1 | UBUNTU-CVE-2026-74670 USN-9024-1 |
| Ubuntu | 22.04:LTS | linux-lowlatency-hwe-6.8 | 6.8.0-149.149.1~22.04.1 | UBUNTU-CVE-2026-74670 USN-9024-1 |
| Ubuntu | 22.04:LTS | linux-oracle-6.8 | 6.8.0-1067.71~22.04.1 | UBUNTU-CVE-2026-74670 USN-9025-1 |
| Ubuntu | 22.04:LTS | linux-riscv, linux-aws-6.2, linux-aws-6.5 and 31 more | no fix listed | UBUNTU-CVE-2026-74670 |
| 43 more for Ubuntu in the JSON and on Ubuntu's page. | ||||
| Azure Linux | 3 | kernel | 6.6.152.1-1 | AZL-97365 |
| Alpaquita | 25 | linux-lts | 6.12.111-r0 | BELL-CVE-2026-74670 |
| Alpaquita | stream | linux-lts | 6.18.46-r0 | BELL-CVE-2026-74670 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT; 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.
IPVS estimator kthread 0 can continue after the initial calculation phase even when IPVS has been disabled during network namespace teardown. In that state the estimator limits may remain zero, and draining est_temp_list can make ip_vs_enqueue_estimator write past the ticks and tick_len arrays. This is a local control plane trigger rather than a packet processing network trigger. For the CVSS the PR:L is used because a local user with access to an IPVS capable network namespace or delegated CAP_NET_ADMIN may be able to reach the vulnerable path. AC:H is used because the condition depends on a teardown timing window during the estimator calculation phase. Impact is at least local denial of service via kernel crash. In the paranoid score, the out of bounds write is treated as a plausible kernel memory corruption path with possible confidentiality, integrity, and availability impact.
Mitigation for this issue is either not available or the currently available options don't 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 | Affected | |
| Red Hat Enterprise Linux 6 | kernel | Out of support scope | |
| 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 | Not affected | |
| 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-74670.