linux-cve-announce - CVE-2025-38663: nilfs2: reject invalid file types when reading inodes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025082259-CVE-2025-38663-b1e8@gregkh>
Date: Fri, 22 Aug 2025 18:03:00 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-38663: nilfs2: reject invalid file types when reading inodes

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

nilfs2: reject invalid file types when reading inodes

To prevent inodes with invalid file types from tripping through the vfs
and causing malfunctions or assertion failures, add a missing sanity check
when reading an inode from a block device.  If the file type is not valid,
treat it as a filesystem error.

The Linux kernel CVE team has assigned CVE-2025-38663 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 2.6.30 with commit 05fe58fdc10df9ebea04c0eaed57adc47af5c184 and fixed in 6.1.148 with commit 1a5c204e175a78556b8ef1f7683249fa5197295a
	Issue introduced in 2.6.30 with commit 05fe58fdc10df9ebea04c0eaed57adc47af5c184 and fixed in 6.6.101 with commit bf585ee198bba4ff25b0d80a0891df4656cb0d08
	Issue introduced in 2.6.30 with commit 05fe58fdc10df9ebea04c0eaed57adc47af5c184 and fixed in 6.12.41 with commit 79663a15a1c70ca84f86f2dbba07b423fe7d5d4f
	Issue introduced in 2.6.30 with commit 05fe58fdc10df9ebea04c0eaed57adc47af5c184 and fixed in 6.15.9 with commit 42cd46b3a8b1497b9258dc7ac445dbd6beb73e2f
	Issue introduced in 2.6.30 with commit 05fe58fdc10df9ebea04c0eaed57adc47af5c184 and fixed in 6.16 with commit 4aead50caf67e01020c8be1945c3201e8a972a27

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-38663
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/nilfs2/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/1a5c204e175a78556b8ef1f7683249fa5197295a
	https://git.kernel.org/stable/c/bf585ee198bba4ff25b0d80a0891df4656cb0d08
	https://git.kernel.org/stable/c/79663a15a1c70ca84f86f2dbba07b423fe7d5d4f
	https://git.kernel.org/stable/c/42cd46b3a8b1497b9258dc7ac445dbd6beb73e2f
	https://git.kernel.org/stable/c/4aead50caf67e01020c8be1945c3201e8a972a27