[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2024122426-CVE-2024-53146-c503@gregkh>
Date: Tue, 24 Dec 2024 12:29:26 +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-53146: NFSD: Prevent a potential integer overflow
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
NFSD: Prevent a potential integer overflow
If the tag length is >= U32_MAX - 3 then the "length + 4" addition
can result in an integer overflow. Address this by splitting the
decoding into several steps so that decode_cb_compound4res() does
not have to perform arithmetic on the unsafe length value.
The Linux kernel CVE team has assigned CVE-2024-53146 to this issue.
Affected and fixed versions
===========================
Fixed in 4.19.325 with commit 745f7ce5a95e783ba62fe774325829466aec2aa8
Fixed in 5.4.287 with commit 90adbae9dd158da8331d9fdd32077bd1af04f553
Fixed in 5.10.231 with commit 3c5f545c9a1f8a1869246f6f3ae8c17289d6a841
Fixed in 5.15.174 with commit 842f1c27a1aef5367e535f9e85c8c3b06352151a
Fixed in 6.1.120 with commit de53c5305184ca1333b87e695d329d1502d694ce
Fixed in 6.6.64 with commit dde654cad08fdaac370febb161ec41eb58e9d2a2
Fixed in 6.11.11 with commit 084f797dbc7e52209a4ab6dbc7f0109268754eb9
Fixed in 6.12.2 with commit ccd3394f9a7200d6b088553bf38e688620cd27af
Fixed in 6.13-rc1 with commit 7f33b92e5b18e904a481e6e208486da43e4dc841
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-53146
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/nfsd/nfs4callback.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/745f7ce5a95e783ba62fe774325829466aec2aa8
https://git.kernel.org/stable/c/90adbae9dd158da8331d9fdd32077bd1af04f553
https://git.kernel.org/stable/c/3c5f545c9a1f8a1869246f6f3ae8c17289d6a841
https://git.kernel.org/stable/c/842f1c27a1aef5367e535f9e85c8c3b06352151a
https://git.kernel.org/stable/c/de53c5305184ca1333b87e695d329d1502d694ce
https://git.kernel.org/stable/c/dde654cad08fdaac370febb161ec41eb58e9d2a2
https://git.kernel.org/stable/c/084f797dbc7e52209a4ab6dbc7f0109268754eb9
https://git.kernel.org/stable/c/ccd3394f9a7200d6b088553bf38e688620cd27af
https://git.kernel.org/stable/c/7f33b92e5b18e904a481e6e208486da43e4dc841
Powered by blists - more mailing lists