[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025061857-CVE-2022-50083-faff@gregkh>
Date: Wed, 18 Jun 2025 13:02:28 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2022-50083: ext4: add EXT4_INODE_HAS_XATTR_SPACE macro in xattr.h
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ext4: add EXT4_INODE_HAS_XATTR_SPACE macro in xattr.h
When adding an xattr to an inode, we must ensure that the inode_size is
not less than EXT4_GOOD_OLD_INODE_SIZE + extra_isize + pad. Otherwise,
the end position may be greater than the start position, resulting in UAF.
The Linux kernel CVE team has assigned CVE-2022-50083 to this issue.
Affected and fixed versions
===========================
Fixed in 4.9.326 with commit 214c68423fd632646c68f3ec8b3c2602cf8273f3
Fixed in 4.14.291 with commit f217b1ccb178475192e6a516fab7230f51ddae94
Fixed in 4.19.256 with commit 0e69cf833161b29b2e25dcbf2f2b4e70d75b15cf
Fixed in 5.4.211 with commit 748d17d47687e178f8e38938447fa4636c071c41
Fixed in 5.10.137 with commit 2da44a2927a71bff2bc66cefa8cfbd2ace702536
Fixed in 5.15.61 with commit e6321fda51e5b4dd7ec295afb84cbf63c2634c7b
Fixed in 5.18.18 with commit 37d82aa78346866552d573e8badc0aa8db8f1eea
Fixed in 5.19.2 with commit 4cdc284ffadd6a989f24107ee7f09be43b748fbb
Fixed in 6.0 with commit 179b14152dcb6a24c3415200603aebca70ff13af
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-50083
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/ext4/xattr.h
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/214c68423fd632646c68f3ec8b3c2602cf8273f3
https://git.kernel.org/stable/c/f217b1ccb178475192e6a516fab7230f51ddae94
https://git.kernel.org/stable/c/0e69cf833161b29b2e25dcbf2f2b4e70d75b15cf
https://git.kernel.org/stable/c/748d17d47687e178f8e38938447fa4636c071c41
https://git.kernel.org/stable/c/2da44a2927a71bff2bc66cefa8cfbd2ace702536
https://git.kernel.org/stable/c/e6321fda51e5b4dd7ec295afb84cbf63c2634c7b
https://git.kernel.org/stable/c/37d82aa78346866552d573e8badc0aa8db8f1eea
https://git.kernel.org/stable/c/4cdc284ffadd6a989f24107ee7f09be43b748fbb
https://git.kernel.org/stable/c/179b14152dcb6a24c3415200603aebca70ff13af
Powered by blists - more mailing lists