CVE-2026-74658 linux linux
linux linux: no CVSS score yet. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.
On this page
- EPSS
- 0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 7th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
- CISA's assessment (SSVC)
- Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-06. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
- Published
- Modified
- NVD analysis
- Awaiting analysis
- Record from
- the NVD, synced
Fix and patched versions
- Linux Linux: fixed in 5.10.265
- Linux Linux: fixed in 5.15.216
- Linux Linux: fixed in 6.1.183
- Linux Linux: fixed in 6.6.152
- Linux Linux: fixed in 6.12.104
- Linux Linux: fixed in 6.18.45
- Linux Linux: fixed in 7.1.9
- Linux Linux: fixed in 7.2
- Debian, Ubuntu, Azure Linux, Alpaquita: fixed package versions per release
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-74658 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-74658?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-74658?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-74658 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.
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Linux | from 3.16.82 before 3.17 |
| Linux | from 4.9.264 before 4.10 |
| Linux | from 4.14.158 before 4.15 |
| Linux | from 4.19.87 before 4.20 |
| Linux | from 5.3.14 before 5.4 |
| Linux | from 5.4.1 before 5.5 |
| Linux | 5.5 and later |
Fixed in
| Product | Release line | Fixed in |
|---|---|---|
| Linux | 5.10 | 5.10.265 |
| Linux | 5.15 | 5.15.216 |
| Linux | 6.1 | 6.1.183 |
| 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 |
Linux distributions
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12 | linux | 6.1.187-1 | DEBIAN-CVE-2026-74658 |
| Debian | 12 | linux-6.12 | 6.12.107-1~deb12u1 | DEBIAN-CVE-2026-74658 |
| Debian | 13 | linux | 6.12.105-1 | DEBIAN-CVE-2026-74658 |
| Debian | 14 | linux | 7.1.9-1 | DEBIAN-CVE-2026-74658 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2026-74658 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-hwe, linux-oem and 12 more | no fix listed | UBUNTU-CVE-2026-74658 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-riscv and 26 more | no fix listed | UBUNTU-CVE-2026-74658 |
| Ubuntu | 22.04:LTS | linux | 5.15.0-198.208 | UBUNTU-CVE-2026-74658 USN-8875-1 |
| Ubuntu | 22.04:LTS | linux-aws | 5.15.0-1117.124 | UBUNTU-CVE-2026-74658 USN-8875-1 |
| Ubuntu | 22.04:LTS | linux-aws-6.8 | 6.8.0-1069.74~22.04.1 | UBUNTU-CVE-2026-74658 USN-9024-1 |
| Ubuntu | 22.04:LTS | linux-azure | 5.15.0-1123.132 | UBUNTU-CVE-2026-74658 USN-8875-1 |
| Ubuntu | 22.04:LTS | linux-azure-6.8 | 6.8.0-1073.82~22.04.1 | UBUNTU-CVE-2026-74658 USN-9026-1 |
| Ubuntu | 22.04:LTS | linux-azure-fde | 5.15.0-1122.131 | UBUNTU-CVE-2026-74658 |
| Ubuntu | 22.04:LTS | linux-azure-fde-6.8 | 6.8.0-1071.78~22.04.1 | UBUNTU-CVE-2026-74658 USN-9026-1 |
| Ubuntu | 22.04:LTS | linux-gcp | 5.15.0-1118.128 | UBUNTU-CVE-2026-74658 USN-8877-1 |
| Ubuntu | 22.04:LTS | linux-gcp-6.8 | 6.8.0-1073.81~22.04.1 | UBUNTU-CVE-2026-74658 USN-9024-1 |
| 82 more for Ubuntu in the JSON and on Ubuntu's page. | ||||
| Azure Linux | 3 | kernel | 6.6.152.1-1 | AZL-97287 |
| Alpaquita | 23 | linux-lts | 6.1.189-r0 | BELL-CVE-2026-74658 |
| Alpaquita | 25 | linux-lts | 6.12.111-r0 | BELL-CVE-2026-74658 |
| Alpaquita | stream | linux-lts | 6.18.46-r0 | BELL-CVE-2026-74658 |
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
Red Hat rates this Moderate.
A moderate-impact flaw was found in the Linux kernel's futex subsystem on Red Hat Enterprise Linux and Red Hat In-Vehicle OS. A race condition in robust futex exit handling can lose a one-shot wakeup: when a robust futex unlock wakes a single waiter and that waiter is killed before it can either acquire the futex or re-arm FUTEX_WAITERS, and a third task re-acquires the futex through the uncontended fast path in the meantime, the wakeup notification is lost. The new owner later unlocks without seeing FUTEX_WAITERS and wakes nobody, so the remaining waiters sleep forever behind a free futex. A local attacker with low privileges who can run code participating in the affected futex synchronization could trigger this race, which requires precise timing to exploit, to cause a denial of service by leaving processes in an indefinite sleep; there is no impact on confidentiality or integrity. Red Hat Enterprise Linux 6, 7, and 8 are not affected because the vulnerable code is not present in those releases. For the affected Red Hat Enterprise Linux 9 (kernel and kernel-rt) and Red Hat Enterprise Linux 10 (kernel) streams and the Red Hat In-Vehicle OS kernel streams, the fix is deferred because the issue has availability-only impact and requires local code execution and a difficult-to-trigger timing race to exploit; it will be addressed in a future update. The residual risk of deferring is a local denial of service in which threads using robust futexes hang permanently.
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 | Fix deferred |
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-74658.
References
- https://git.kernel.org/stable/c/33bfa85458105d6169ebdb697f692b8bb8025bae
- https://git.kernel.org/stable/c/6d4514ca9cdf61fec4ec634cf50386f6f7e69748
- https://git.kernel.org/stable/c/7b8c53263f8878bdd12c87e147ac6feca5c05211
- https://git.kernel.org/stable/c/7cf710e70f9bb8ea75f759ebed09871801315992
- https://git.kernel.org/stable/c/83b0f71d5a313a765754acab51d2ecc5de76e0b9
- https://git.kernel.org/stable/c/925628656b73b70930972ccde421de4f758d8650
- https://git.kernel.org/stable/c/a1c2b7b86a946b6b172bce44d74553da2323a36c
- https://git.kernel.org/stable/c/aa5c571901c6b22b58373693a4bf889ecab11ff5