[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025032758-CVE-2022-49743-a049@gregkh>
Date: Thu, 27 Mar 2025 17:43:01 +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-49743: ovl: Use "buf" flexible array for memcpy() destination
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ovl: Use "buf" flexible array for memcpy() destination
The "buf" flexible array needs to be the memcpy() destination to avoid
false positive run-time warning from the recent FORTIFY_SOURCE
hardening:
memcpy: detected field-spanning write (size 93) of single field "&fh->fb"
at fs/overlayfs/export.c:799 (size 21)
The Linux kernel CVE team has assigned CVE-2022-49743 to this issue.
Affected and fixed versions
===========================
Fixed in 5.15.93 with commit a77141a06367825d639ac51b04703d551163e36c
Fixed in 6.1.11 with commit 07a96977b2f462337a9121302de64277b8747ab1
Fixed in 6.2 with commit cf8aa9bf97cadf85745506c6a3e244b22c268d63
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-49743
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/overlayfs/export.c
fs/overlayfs/overlayfs.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/a77141a06367825d639ac51b04703d551163e36c
https://git.kernel.org/stable/c/07a96977b2f462337a9121302de64277b8747ab1
https://git.kernel.org/stable/c/cf8aa9bf97cadf85745506c6a3e244b22c268d63
Powered by blists - more mailing lists