From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-99741: tmpfs: keep the quota soft limits of an unused id
Date: Fri, 20 Nov 2026 06:52:07 +0100 [thread overview]
Message-ID: <2026112017-CVE-2026-99741-bbb5@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
tmpfs: keep the quota soft limits of an unused id
When the last reference to a dquot goes away, shmem_release_dquot()
stores its limits in the rb tree of the mount, unless
shmem_is_empty_dquot() says that there is nothing worth storing. That
function looks at the usage and at the two hard limits only.
So if the administrator sets nothing but soft limits for an id that owns
no file yet, the entry is thrown away as soon as the dquot that
Q_SETQUOTA used is released, and the id never gets to see a limit.
To fix it, compare the soft limits as well: an entry can be empty only if
both soft limits are zero as well, which is exactly what
shmem_acquire_dquot() sets for a new entry.
Fix generated by an LLM and sent by Josef Bacik in private.
[ david: slightly adjusted description ]
The Linux kernel CVE team has assigned CVE-2026-99741 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.6 with commit de4c0e7ca8b526a82ff7e5ee5533787bb6d01724 and fixed in 6.12.118 with commit b66796d176dfc107ec7fd2d6b4e9b6fa8b160dd6
Issue introduced in 6.6 with commit de4c0e7ca8b526a82ff7e5ee5533787bb6d01724 and fixed in 6.18.64 with commit e6158f1736ebc3681ee164e8d5b5c1607ac60138
Issue introduced in 6.6 with commit de4c0e7ca8b526a82ff7e5ee5533787bb6d01724 and fixed in 7.3.5 with commit 3aa51c92711896c86da9fcef01b1155e8caa7e74
Issue introduced in 6.6 with commit de4c0e7ca8b526a82ff7e5ee5533787bb6d01724 and fixed in 7.4-rc2 with commit 968d73463059156e1b89bfa6b189acd7d27197b2
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-2026-99741
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:
mm/shmem_quota.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/b66796d176dfc107ec7fd2d6b4e9b6fa8b160dd6
https://git.kernel.org/stable/c/e6158f1736ebc3681ee164e8d5b5c1607ac60138
https://git.kernel.org/stable/c/3aa51c92711896c86da9fcef01b1155e8caa7e74
https://git.kernel.org/stable/c/968d73463059156e1b89bfa6b189acd7d27197b2
reply other threads:[~2026-11-20 6:00 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=2026112017-CVE-2026-99741-bbb5@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@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.