Bug 2577649 (CVE-2026-99741) - CVE-2026-99741 kernel: kernel: Quota limit bypass via discarded tmpfs soft limits
Summary: CVE-2026-99741 kernel: kernel: Quota limit bypass via discarded tmpfs soft li...
Keywords:
Status: NEW
Alias: CVE-2026-99741
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-11-20 06:06 UTC by OSIDB Bzimport
Modified: 2026-11-20 10:01 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-11-20 06:06:14 UTC
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 ]


Note You need to log in before you can comment on or make changes to this bug.