linux-cve-announce - CVE-2022-50519: nilfs2: replace WARN_ONs by nilfs

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: <2025100704-CVE-2022-50519-4c44@gregkh>
Date: Tue,  7 Oct 2025 17:19:06 +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-50519: nilfs2: replace WARN_ONs by nilfs_error for checkpoint acquisition failure

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

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

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

nilfs2: replace WARN_ONs by nilfs_error for checkpoint acquisition failure

If creation or finalization of a checkpoint fails due to anomalies in the
checkpoint metadata on disk, a kernel warning is generated.

This patch replaces the WARN_ONs by nilfs_error, so that a kernel, booted
with panic_on_warn, does not panic.  A nilfs_error is appropriate here to
handle the abnormal filesystem condition.

This also replaces the detected error codes with an I/O error so that
neither of the internal error codes is returned to callers.

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


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

	Fixed in 4.9.331 with commit b63026b5e13040cd5afa11769dd0d9e1504b031a
	Fixed in 4.14.296 with commit ae16440c44ae2acda6d72aff9d74eccf8967dae5
	Fixed in 4.19.262 with commit bf98be80cbe3b4e6c86c36ed00457389aca3eb15
	Fixed in 5.4.218 with commit 259c0f68168ac6a598db3486597b10e74d625db0
	Fixed in 5.10.148 with commit 8a18fdc5ae8e6d7ac33c6ee0a2e5f9f1414ef412
	Fixed in 5.15.74 with commit c0c3d3d3ea41cb5228ee90568bb953f9a56c3227
	Fixed in 5.19.16 with commit 090fcfb6edeb9367a915b2749e2bd1f8b48d8898
	Fixed in 6.0.2 with commit 5c0776b5bc31de7cd28afb558fae37a20f33602e
	Fixed in 6.1 with commit 723ac751208f6d6540191689cfbf6c77135a7a1b

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-50519
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/segment.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/b63026b5e13040cd5afa11769dd0d9e1504b031a
	https://git.kernel.org/stable/c/ae16440c44ae2acda6d72aff9d74eccf8967dae5
	https://git.kernel.org/stable/c/bf98be80cbe3b4e6c86c36ed00457389aca3eb15
	https://git.kernel.org/stable/c/259c0f68168ac6a598db3486597b10e74d625db0
	https://git.kernel.org/stable/c/8a18fdc5ae8e6d7ac33c6ee0a2e5f9f1414ef412
	https://git.kernel.org/stable/c/c0c3d3d3ea41cb5228ee90568bb953f9a56c3227
	https://git.kernel.org/stable/c/090fcfb6edeb9367a915b2749e2bd1f8b48d8898
	https://git.kernel.org/stable/c/5c0776b5bc31de7cd28afb558fae37a20f33602e
	https://git.kernel.org/stable/c/723ac751208f6d6540191689cfbf6c77135a7a1b