linux-cve-announce - CVE-2022-49739: gfs2: Always check inode size of inline 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: <2025032756-CVE-2022-49739-a93e@gregkh>
Date: Thu, 27 Mar 2025 17:42:57 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2022-49739: gfs2: Always check inode size of inline inodes

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

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

gfs2: Always check inode size of inline inodes

Check if the inode size of stuffed (inline) inodes is within the allowed
range when reading inodes from disk (gfs2_dinode_in()).  This prevents
us from on-disk corruption.

The two checks in stuffed_readpage() and gfs2_unstuffer_page() that just
truncate inline data to the maximum allowed size don't actually make
sense, and they can be removed now as well.

The Linux kernel CVE team has assigned CVE-2022-49739 to this issue.


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

	Fixed in 4.19.280 with commit 45df749f827c286adbc951f2a4865b67f0442ba9
	Fixed in 5.4.240 with commit 4d4cb76636134bf9a0c9c3432dae936f99954586
	Fixed in 5.10.177 with commit 7c414f6f06e9a3934901b6edc3177ae5a1e07094
	Fixed in 5.15.93 with commit 46c9088cabd4d0469fdb61ac2a9c5003057fe94d
	Fixed in 6.1.11 with commit d458a0984429c2d47e60254f5bc4119cbafe83a2
	Fixed in 6.2 with commit 70376c7ff31221f1d21db5611d8209e677781d3a

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-2022-49739
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/gfs2/aops.c
	fs/gfs2/bmap.c
	fs/gfs2/glops.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/45df749f827c286adbc951f2a4865b67f0442ba9
	https://git.kernel.org/stable/c/4d4cb76636134bf9a0c9c3432dae936f99954586
	https://git.kernel.org/stable/c/7c414f6f06e9a3934901b6edc3177ae5a1e07094
	https://git.kernel.org/stable/c/46c9088cabd4d0469fdb61ac2a9c5003057fe94d
	https://git.kernel.org/stable/c/d458a0984429c2d47e60254f5bc4119cbafe83a2
	https://git.kernel.org/stable/c/70376c7ff31221f1d21db5611d8209e677781d3a