CVE-2025-68250

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!

CVSS v3 8.2 HIGH

8.2^/10

CVSS v3 : HIGH

Vector :

Exploitability : 3.9 / Impact : 4.2

Attack Vector NETWORK

Attack Complexity LOW

Privileges Required NONE

User Interaction NONE

Confidentiality Impact LOW

Integrity Impact NONE

Availability Impact HIGH

Scope UNCHANGED

References

Link	Resource
https://git.kernel.org/stable/c/c0e2dcbe54cb15ecdf9d8f4501c6720423243888
https://git.kernel.org/stable/c/c97513cddcfc235f2522617980838e500af21d01

Configurations

No configuration.

History

30 Jul 2026, 06:24

Type	Values Removed	Values Added
CVSS	v2 : ~~unknown~~ v3 : ~~unknown~~	v2 : unknown v3 : 8.2

16 Dec 2025, 15:15

Type	Values Removed	Values Added
New CVE

Information

Published : 2025-12-16 15:15

Updated : 2026-07-30 06:24

NVD link : CVE-2025-68250

Mitre link : CVE-2025-68250

CVE.ORG link : CVE-2025-68250

JSON object : View

Products Affected

No product.

CWE

No CWE.

{"id": "CVE-2025-68250", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 8.2, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "LOW"}, "impactScore": 4.2, "exploitabilityScore": 3.9}]}, "affected": [{"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "affectedData": [{"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "product": "Linux", "versions": [{"status": "affected", "version": "e711faaafbe54a884f33b53472434063d342f6d4", "lessThan": "c0e2dcbe54cb15ecdf9d8f4501c6720423243888", "versionType": "git"}, {"status": "affected", "version": "e711faaafbe54a884f33b53472434063d342f6d4", "lessThan": "c97513cddcfc235f2522617980838e500af21d01", "versionType": "git"}], "programFiles": ["include/linux/hung_task.h"], "defaultStatus": "unaffected"}, {"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "product": "Linux", "versions": [{"status": "affected", "version": "6.16"}, {"status": "unaffected", "version": "0", "lessThan": "6.16", "versionType": "semver"}, {"status": "unaffected", "version": "6.17.6", "versionType": "semver", "lessThanOrEqual": "6.17.*"}, {"status": "unaffected", "version": "6.18", "versionType": "original_commit_for_fix", "lessThanOrEqual": "*"}], "programFiles": ["include/linux/hung_task.h"], "defaultStatus": "affected"}]}], "published": "2025-12-16T15:15:54.307", "references": [{"url": "https://git.kernel.org/stable/c/c0e2dcbe54cb15ecdf9d8f4501c6720423243888", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/c97513cddcfc235f2522617980838e500af21d01", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}], "vulnStatus": "Deferred", "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nhung_task: fix warnings caused by unaligned lock pointers\n\nThe blocker tracking mechanism assumes that lock pointers are at least\n4-byte aligned to use their lower bits for type encoding.\n\nHowever, as reported by Eero Tamminen, some architectures like m68k\nonly guarantee 2-byte alignment of 32-bit values. This breaks the\nassumption and causes two related WARN_ON_ONCE checks to trigger.\n\nTo fix this, the runtime checks are adjusted to silently ignore any lock\nthat is not 4-byte aligned, effectively disabling the feature in such\ncases and avoiding the related warnings.\n\nThanks to Geert Uytterhoeven for bisecting!"}], "lastModified": "2026-07-30T06:24:34.843", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}