[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2024122913-CVE-2024-56710-78af@gregkh>
Date: Sun, 29 Dec 2024 09:48:14 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2024-56710: ceph: fix memory leak in ceph_direct_read_write()
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ceph: fix memory leak in ceph_direct_read_write()
The bvecs array which is allocated in iter_get_bvecs_alloc() is leaked
and pages remain pinned if ceph_alloc_sparse_ext_map() fails.
There is no need to delay the allocation of sparse_ext map until after
the bvecs array is set up, so fix this by moving sparse_ext allocation
a bit earlier. Also, make a similar adjustment in __ceph_sync_read()
for consistency (a leak of the same kind in __ceph_sync_read() has been
addressed differently).
The Linux kernel CVE team has assigned CVE-2024-56710 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.6 with commit 03bc06c7b0bd8d86b9f17f459acaeb1283ba2700 and fixed in 6.12.7 with commit eb9041837123f31d5897e99bb761f46cb4ce5859
Issue introduced in 6.6 with commit 03bc06c7b0bd8d86b9f17f459acaeb1283ba2700 and fixed in 6.13-rc4 with commit 66e0c4f91461d17d48071695271c824620bed4ef
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-2024-56710
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/ceph/file.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/eb9041837123f31d5897e99bb761f46cb4ce5859
https://git.kernel.org/stable/c/66e0c4f91461d17d48071695271c824620bed4ef
Powered by blists - more mailing lists