{"api_version":"1","generated_at":"2026-11-20T07:29:59+00:00","cve":"CVE-2026-99741","urls":{"html":"https://cve.report/CVE-2026-99741","api":"https://cve.report/api/cve/CVE-2026-99741.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-99741","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-99741"},"summary":{"title":"tmpfs: keep the quota soft limits of an unused id","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ntmpfs: keep the quota soft limits of an unused id\n\nWhen the last reference to a dquot goes away, shmem_release_dquot()\nstores its limits in the rb tree of the mount, unless\nshmem_is_empty_dquot() says that there is nothing worth storing. That\nfunction looks at the usage and at the two hard limits only.\n\nSo if the administrator sets nothing but soft limits for an id that owns\nno file yet, the entry is thrown away as soon as the dquot that\nQ_SETQUOTA used is released, and the id never gets to see a limit.\n\nTo fix it, compare the soft limits as well: an entry can be empty only if\nboth soft limits are zero as well, which is exactly what\nshmem_acquire_dquot() sets for a new entry.\n\nFix generated by an LLM and sent by Josef Bacik in private.\n\n[ david: slightly adjusted description ]","state":"PUBLISHED","assigner":"Linux","published_at":"2026-11-20 06:18:11","updated_at":"2026-11-20 06:18:11"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/3aa51c92711896c86da9fcef01b1155e8caa7e74","name":"https://git.kernel.org/stable/c/3aa51c92711896c86da9fcef01b1155e8caa7e74","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/b66796d176dfc107ec7fd2d6b4e9b6fa8b160dd6","name":"https://git.kernel.org/stable/c/b66796d176dfc107ec7fd2d6b4e9b6fa8b160dd6","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/968d73463059156e1b89bfa6b189acd7d27197b2","name":"https://git.kernel.org/stable/c/968d73463059156e1b89bfa6b189acd7d27197b2","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/e6158f1736ebc3681ee164e8d5b5c1607ac60138","name":"https://git.kernel.org/stable/c/e6158f1736ebc3681ee164e8d5b5c1607ac60138","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-99741","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99741","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected de4c0e7ca8b526a82ff7e5ee5533787bb6d01724 b66796d176dfc107ec7fd2d6b4e9b6fa8b160dd6 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected de4c0e7ca8b526a82ff7e5ee5533787bb6d01724 e6158f1736ebc3681ee164e8d5b5c1607ac60138 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected de4c0e7ca8b526a82ff7e5ee5533787bb6d01724 3aa51c92711896c86da9fcef01b1155e8caa7e74 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected de4c0e7ca8b526a82ff7e5ee5533787bb6d01724 968d73463059156e1b89bfa6b189acd7d27197b2 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.6","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.6 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.118 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.64 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3.5 7.3.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.4-rc2 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["mm/shmem_quota.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"b66796d176dfc107ec7fd2d6b4e9b6fa8b160dd6","status":"affected","version":"de4c0e7ca8b526a82ff7e5ee5533787bb6d01724","versionType":"git"},{"lessThan":"e6158f1736ebc3681ee164e8d5b5c1607ac60138","status":"affected","version":"de4c0e7ca8b526a82ff7e5ee5533787bb6d01724","versionType":"git"},{"lessThan":"3aa51c92711896c86da9fcef01b1155e8caa7e74","status":"affected","version":"de4c0e7ca8b526a82ff7e5ee5533787bb6d01724","versionType":"git"},{"lessThan":"968d73463059156e1b89bfa6b189acd7d27197b2","status":"affected","version":"de4c0e7ca8b526a82ff7e5ee5533787bb6d01724","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["mm/shmem_quota.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.6"},{"lessThan":"6.6","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.118","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.64","versionType":"semver"},{"lessThanOrEqual":"7.3.*","status":"unaffected","version":"7.3.5","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.4-rc2","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.118","versionStartIncluding":"6.6","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.64","versionStartIncluding":"6.6","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3.5","versionStartIncluding":"6.6","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.4-rc2","versionStartIncluding":"6.6","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\ntmpfs: keep the quota soft limits of an unused id\n\nWhen the last reference to a dquot goes away, shmem_release_dquot()\nstores its limits in the rb tree of the mount, unless\nshmem_is_empty_dquot() says that there is nothing worth storing. That\nfunction looks at the usage and at the two hard limits only.\n\nSo if the administrator sets nothing but soft limits for an id that owns\nno file yet, the entry is thrown away as soon as the dquot that\nQ_SETQUOTA used is released, and the id never gets to see a limit.\n\nTo fix it, compare the soft limits as well: an entry can be empty only if\nboth soft limits are zero as well, which is exactly what\nshmem_acquire_dquot() sets for a new entry.\n\nFix generated by an LLM and sent by Josef Bacik in private.\n\n[ david: slightly adjusted description ]"}],"providerMetadata":{"dateUpdated":"2026-11-20T05:51:13.712Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/b66796d176dfc107ec7fd2d6b4e9b6fa8b160dd6"},{"url":"https://git.kernel.org/stable/c/e6158f1736ebc3681ee164e8d5b5c1607ac60138"},{"url":"https://git.kernel.org/stable/c/3aa51c92711896c86da9fcef01b1155e8caa7e74"},{"url":"https://git.kernel.org/stable/c/968d73463059156e1b89bfa6b189acd7d27197b2"}],"title":"tmpfs: keep the quota soft limits of an unused id","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-99741","datePublished":"2026-11-20T05:51:13.712Z","dateReserved":"2026-09-25T10:25:14.432Z","dateUpdated":"2026-11-20T05:51:13.712Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-11-20 06:18:11","lastModifiedDate":"2026-11-20 06:18:11","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"99741","Ordinal":"1","Title":"tmpfs: keep the quota soft limits of an unused id","CVE":"CVE-2026-99741","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"99741","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\ntmpfs: keep the quota soft limits of an unused id\n\nWhen the last reference to a dquot goes away, shmem_release_dquot()\nstores its limits in the rb tree of the mount, unless\nshmem_is_empty_dquot() says that there is nothing worth storing. That\nfunction looks at the usage and at the two hard limits only.\n\nSo if the administrator sets nothing but soft limits for an id that owns\nno file yet, the entry is thrown away as soon as the dquot that\nQ_SETQUOTA used is released, and the id never gets to see a limit.\n\nTo fix it, compare the soft limits as well: an entry can be empty only if\nboth soft limits are zero as well, which is exactly what\nshmem_acquire_dquot() sets for a new entry.\n\nFix generated by an LLM and sent by Josef Bacik in private.\n\n[ david: slightly adjusted description ]","Type":"Description","Title":"tmpfs: keep the quota soft limits of an unused id"}]}}}