[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025121623-CVE-2025-68250-9b9c@gregkh>
Date: Tue, 16 Dec 2025 15:32:26 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-68250: hung_task: fix warnings caused by unaligned lock pointers
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
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!
The Linux kernel CVE team has assigned CVE-2025-68250 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.16 with commit e711faaafbe54a884f33b53472434063d342f6d4 and fixed in 6.17.6 with commit c0e2dcbe54cb15ecdf9d8f4501c6720423243888
Issue introduced in 6.16 with commit e711faaafbe54a884f33b53472434063d342f6d4 and fixed in 6.18 with commit c97513cddcfc235f2522617980838e500af21d01
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2025-68250
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
include/linux/hung_task.h
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/c0e2dcbe54cb15ecdf9d8f4501c6720423243888
https://git.kernel.org/stable/c/c97513cddcfc235f2522617980838e500af21d01
Powered by blists - more mailing lists