[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025122405-CVE-2025-68727-8481@gregkh>
Date: Wed, 24 Dec 2025 11:35:29 +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-68727: ntfs3: Fix uninit buffer allocated by __getname()
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ntfs3: Fix uninit buffer allocated by __getname()
Fix uninit errors caused after buffer allocation given to 'de'; by
initializing the buffer with zeroes. The fix was found by using KMSAN.
The Linux kernel CVE team has assigned CVE-2025-68727 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.15 with commit 78ab59fee07f22464f32eafebab2bd97ba94ff2d and fixed in 6.12.63 with commit 4b1fd82848fdf0e01b3320815b261006c1722c3e
Issue introduced in 5.15 with commit 78ab59fee07f22464f32eafebab2bd97ba94ff2d and fixed in 6.17.13 with commit d88d4b455b6794f48d7adad52593f1700c7bd50e
Issue introduced in 5.15 with commit 78ab59fee07f22464f32eafebab2bd97ba94ff2d and fixed in 6.18.2 with commit b40a4eb4a0543d49686a6e693745009dac3b86a9
Issue introduced in 5.15 with commit 78ab59fee07f22464f32eafebab2bd97ba94ff2d and fixed in 6.19-rc1 with commit 9948dcb2f7b5a1bf8e8710eafaf6016e00be3ad6
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-68727
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:
fs/ntfs3/inode.c
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/4b1fd82848fdf0e01b3320815b261006c1722c3e
https://git.kernel.org/stable/c/d88d4b455b6794f48d7adad52593f1700c7bd50e
https://git.kernel.org/stable/c/b40a4eb4a0543d49686a6e693745009dac3b86a9
https://git.kernel.org/stable/c/9948dcb2f7b5a1bf8e8710eafaf6016e00be3ad6
Powered by blists - more mailing lists