cve.bz

CVE-2025-68250 linux linux

8.2 highEPSS 0.3%Fix available

High (8.2) in linux linux. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: hung_task: fix warnings caused by unaligned lock pointers The blocker tracking mechanism assumes that lock pointers are at least 4-byte aligned to use their lower bits for type encoding. However, as reported by Eero Tamminen, some architectures like m68k only guarantee 2-byte alignment of 32-bit values. This breaks the assumption and causes two related WARN_ON_ONCE checks to trigger. To fix this, the runtime checks are adjusted to silently ignore any lock that is not 4-byte aligned, effectively disabling the feature in such cases and avoiding the related warnings. Thanks to Geert Uytterhoeven for bisecting!

Severity

CVSS 3.1

8.2 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 24th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain 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.

Badge for a README or a site

CVE-2025-68250

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2025-68250](https://cve.bz/cve/badge/CVE-2025-68250.svg)](https://cve.bz/cve/CVE-2025-68250)

HTML:

<a href="https://cve.bz/cve/CVE-2025-68250"><img src="https://cve.bz/cve/badge/CVE-2025-68250.svg" alt="CVE-2025-68250"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux6.16 and later

Fixed in

ProductRelease lineFixed in
Linux6.176.17.6
Linuxlater releases6.18

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian14linux6.17.6-1DEBIAN-CVE-2025-68250
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2025-68250
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2025-68250
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2025-68250
Ubuntu22.04:LTSlinux-riscv, linux-aws-6.2, linux-aws-6.5 and 30 moreno fix listedUBUNTU-CVE-2025-68250
Ubuntu24.04:LTSlinux-aws-6.17, linux-oracle-6.176.17.0-1007.7~24.04.1UBUNTU-CVE-2025-68250
Ubuntu24.04:LTSlinux-gcp-6.176.17.0-1008.8~24.04.1UBUNTU-CVE-2025-68250
Ubuntu24.04:LTSlinux-nvidia-6.176.17.0-1008.8UBUNTU-CVE-2025-68250
Ubuntu24.04:LTSlinux-oem-6.176.17.0-1011.11UBUNTU-CVE-2025-68250 USN-8048-1
Ubuntu24.04:LTSlinux-riscv, linux-oem-6.8, linux-gcp-6.11 and 8 moreno fix listedUBUNTU-CVE-2025-68250
Ubuntu25.10linux6.17.0-14.14UBUNTU-CVE-2025-68250 USN-8029-1
Ubuntu25.10linux-aws, linux-gcp, linux-oracle6.17.0-1007.7UBUNTU-CVE-2025-68250 USN-8029-2 USN-8030-1
Ubuntu25.10linux-azure, linux-raspi6.17.0-1008.8UBUNTU-CVE-2025-68250 USN-8029-1 USN-8029-3
4 more for Ubuntu in the JSON and on Ubuntu's page.
Alpaquitastreamlinux-lts6.18.35-r1BELL-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

Red Hat rates this Low.

Red Hat's statement

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).

Red Hat's mitigation

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.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelNot affected
Red Hat Enterprise Linux 6kernelOut of support scope
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelNot affected
Red Hat Enterprise Linux 9kernel-rtNot 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.

References

Check your stackJSON