From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2025-21964: cifs: Fix integer overflow while processing acregmax mount option
Date: Tue, 1 Apr 2025 16:45:49 +0100 [thread overview]
Message-ID: <2025040145-CVE-2025-21964-e2c1@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
cifs: Fix integer overflow while processing acregmax mount option
User-provided mount parameter acregmax of type u32 is intended to have
an upper limit, but before it is validated, the value is converted from
seconds to jiffies which can lead to an integer overflow.
Found by Linux Verification Center (linuxtesting.org) with SVACE.
The Linux kernel CVE team has assigned CVE-2025-21964 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.12 with commit 5780464614f6abe6026f00cf5a0777aa453ba450 and fixed in 6.1.132 with commit dd190168e60ac15408f074a1fe0ce36aff34027b
Issue introduced in 5.12 with commit 5780464614f6abe6026f00cf5a0777aa453ba450 and fixed in 6.6.84 with commit 0252c33cc943e9e48ddfafaa6b1eb72adb68a099
Issue introduced in 5.12 with commit 5780464614f6abe6026f00cf5a0777aa453ba450 and fixed in 6.12.20 with commit 833f2903eb8b70faca7967319e580e9ce69729fc
Issue introduced in 5.12 with commit 5780464614f6abe6026f00cf5a0777aa453ba450 and fixed in 6.13.8 with commit 5f500874ab9b3cc8c169c2ab49f00b838520b9c5
Issue introduced in 5.12 with commit 5780464614f6abe6026f00cf5a0777aa453ba450 and fixed in 6.14 with commit 7489161b1852390b4413d57f2457cd40b34da6cc
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-2025-21964
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/smb/client/fs_context.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/dd190168e60ac15408f074a1fe0ce36aff34027b
https://git.kernel.org/stable/c/0252c33cc943e9e48ddfafaa6b1eb72adb68a099
https://git.kernel.org/stable/c/833f2903eb8b70faca7967319e580e9ce69729fc
https://git.kernel.org/stable/c/5f500874ab9b3cc8c169c2ab49f00b838520b9c5
https://git.kernel.org/stable/c/7489161b1852390b4413d57f2457cd40b34da6cc
reply other threads:[~2025-04-01 15:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2025040145-CVE-2025-21964-e2c1@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.