[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025061848-CVE-2022-50056-dfbb@gregkh>
Date: Wed, 18 Jun 2025 13:02:01 +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-50056: fs/ntfs3: Fix missing i_op in ntfs_read_mft
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
fs/ntfs3: Fix missing i_op in ntfs_read_mft
There is null pointer dereference because i_op == NULL.
The bug happens because we don't initialize i_op for records in $Extend.
The Linux kernel CVE team has assigned CVE-2022-50056 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.15 with commit 82cae269cfa953032fbb8980a7d554d60fb00b17 and fixed in 5.15.63 with commit c293e8abc09e6e1faa50d967bd8862b1cbd575e5
Issue introduced in 5.15 with commit 82cae269cfa953032fbb8980a7d554d60fb00b17 and fixed in 5.19.4 with commit 8089a1bc27b41e6800590a92d17c119e9aa8ff53
Issue introduced in 5.15 with commit 82cae269cfa953032fbb8980a7d554d60fb00b17 and fixed in 6.0 with commit 37a530bfe56ca9a0d3129598803f2794c7428aae
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-50056
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/ntfs3/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/c293e8abc09e6e1faa50d967bd8862b1cbd575e5
https://git.kernel.org/stable/c/8089a1bc27b41e6800590a92d17c119e9aa8ff53
https://git.kernel.org/stable/c/37a530bfe56ca9a0d3129598803f2794c7428aae
Powered by blists - more mailing lists