CVSS 3.1
8.2 highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:HHigh (8.2) in linux linux. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:HExplain CVE-2025-68250 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-68250?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-68250?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-2025-68250 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.16 and later |
| Product | Release line | Fixed in |
|---|---|---|
| Linux | 6.17 | 6.17.6 |
| Linux | later releases | 6.18 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 14 | linux | 6.17.6-1 | DEBIAN-CVE-2025-68250 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2025-68250 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-hwe, linux-oem and 12 more | no fix listed | UBUNTU-CVE-2025-68250 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-riscv and 26 more | no fix listed | UBUNTU-CVE-2025-68250 |
| Ubuntu | 22.04:LTS | linux-riscv, linux-aws-6.2, linux-aws-6.5 and 30 more | no fix listed | UBUNTU-CVE-2025-68250 |
| Ubuntu | 24.04:LTS | linux-aws-6.17, linux-oracle-6.17 | 6.17.0-1007.7~24.04.1 | UBUNTU-CVE-2025-68250 |
| Ubuntu | 24.04:LTS | linux-gcp-6.17 | 6.17.0-1008.8~24.04.1 | UBUNTU-CVE-2025-68250 |
| Ubuntu | 24.04:LTS | linux-nvidia-6.17 | 6.17.0-1008.8 | UBUNTU-CVE-2025-68250 |
| Ubuntu | 24.04:LTS | linux-oem-6.17 | 6.17.0-1011.11 | UBUNTU-CVE-2025-68250 USN-8048-1 |
| Ubuntu | 24.04:LTS | linux-riscv, linux-oem-6.8, linux-gcp-6.11 and 8 more | no fix listed | UBUNTU-CVE-2025-68250 |
| Ubuntu | 25.10 | linux | 6.17.0-14.14 | UBUNTU-CVE-2025-68250 USN-8029-1 |
| Ubuntu | 25.10 | linux-aws, linux-gcp, linux-oracle | 6.17.0-1007.7 | UBUNTU-CVE-2025-68250 USN-8029-2 USN-8030-1 |
| Ubuntu | 25.10 | linux-azure, linux-raspi | 6.17.0-1008.8 | UBUNTU-CVE-2025-68250 USN-8029-1 USN-8029-3 |
| 4 more for Ubuntu in the JSON and on Ubuntu's page. | ||||
| Alpaquita | stream | linux-lts | 6.18.35-r1 | BELL-CVE-2025-68250 |
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 Low.
A low impact flaw was found in the Linux kernel's hung task detector (hung_task) blocker tracking mechanism, which encodes a blocking type in the lower bits of a lock pointer and therefore assumes that lock pointers are at least 4-byte aligned. On architectures that guarantee only 2-byte alignment of 32-bit values, such as m68k, valid lock pointers can have non-zero low bits that collide with this type encoding, causing two WARN_ON_ONCE checks in the blocker set and clear paths to trigger. The direct consequence is spurious kernel warnings and unreliable hung task diagnostics; on systems configured to treat kernel warnings as fatal, for example with panic_on_warn enabled, these warnings could escalate into a local denial of service. Red Hat assesses this flaw as low impact because it is local in nature, has no confidentiality or integrity impact, and manifests only on architectures with weaker pointer alignment guarantees.
The vulnerable blocker tracking code was introduced in the upstream Linux 6.16 kernel and is not present in the Red Hat Enterprise Linux kernels shipped in supported Red Hat products. All in-support Red Hat products, including Red Hat Enterprise Linux 7 through 10 (kernel and kernel-rt) and Red Hat In-Vehicle OS, are recorded as not affected for this flaw because the vulnerable code is not present; the Red Hat Enterprise Linux 6 Extended Lifecycle Support stream is out of support scope. The upstream CVE record assigns a higher severity (CVSS 3.1 score 8.2, Important, based on a network attack vector with confidentiality and availability impact). Red Hat's assessment differs because the verified behavior is a local, warning-only defect that cannot be triggered by a remote or unauthenticated network attacker; Red Hat rates it low impact with CVSS 3.1 score 5.5 (AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).
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 | Not 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-2025-68250.