linux-cve-announce - CVE-2025-38549: efivarfs: Fix memory leak of efivarfs_fs_info in fs

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: <2025081628-CVE-2025-38549-1e8e@gregkh>
Date: Sat, 16 Aug 2025 13:34:26 +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-38549: efivarfs: Fix memory leak of efivarfs_fs_info in fs_context error paths

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

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

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

efivarfs: Fix memory leak of efivarfs_fs_info in fs_context error paths

When processing mount options, efivarfs allocates efivarfs_fs_info (sfi)
early in fs_context initialization. However, sfi is associated with the
superblock and typically freed when the superblock is destroyed. If the
fs_context is released (final put) before fill_super is called—such as
on error paths or during reconfiguration—the sfi structure would leak,
as ownership never transfers to the superblock.

Implement the .free callback in efivarfs_context_ops to ensure any
allocated sfi is properly freed if the fs_context is torn down before
fill_super, preventing this memory leak.

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


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

	Issue introduced in 6.7 with commit 5329aa5101f73c451bcd48deaf3f296685849d9c and fixed in 6.12.40 with commit 816d36973467d1c9c08a48bdffe4675e219a2e84
	Issue introduced in 6.7 with commit 5329aa5101f73c451bcd48deaf3f296685849d9c and fixed in 6.15.8 with commit e9fabe7036bb8be6071f39dc38605508f5f57b20
	Issue introduced in 6.7 with commit 5329aa5101f73c451bcd48deaf3f296685849d9c and fixed in 6.16 with commit 64e135f1eaba0bbb0cdee859af3328c68d5b9789

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-38549
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/efivarfs/super.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/816d36973467d1c9c08a48bdffe4675e219a2e84
	https://git.kernel.org/stable/c/e9fabe7036bb8be6071f39dc38605508f5f57b20
	https://git.kernel.org/stable/c/64e135f1eaba0bbb0cdee859af3328c68d5b9789