{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2026-72368", "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "state": "PUBLISHED", "assignerShortName": "Linux", "dateReserved": "2026-08-09T03:40:39.922Z", "datePublished": "2026-08-15T05:56:05.329Z", "dateUpdated": "2026-08-17T05:43:22.072Z"}, "containers": {"cna": {"providerMetadata": {"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "shortName": "Linux", "dateUpdated": "2026-08-17T05:43:22.072Z"}, "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ncachefiles: Fix double unlock in nomem_d_alloc error path\n\nWhen start_creating() fails and returns -ENOMEM, it has already\nreleased the parent directory lock in __start_dirop():\n\n static struct dentry *__start_dirop(...)\n {\n ...\n inode_lock_nested(dir, I_MUTEX_PARENT);\n dentry = lookup_one_qstr_excl(name, parent, lookup_flags);\n if (IS_ERR(dentry))\n inode_unlock(dir); <-- Lock released on error\n return dentry;\n }\n\nHowever, the nomem_d_alloc error path in cachefiles_get_directory()\nunconditionally calls inode_unlock(d_inode(dir)) again, causing a\ndouble unlock that corrupts the rwsem state.\n\nThis is a leftover from commit 7ab96df840e60 which replaced manual\nlocking with start_creating() but failed to update the nomem_d_alloc\npath (while correctly updating mkdir_error and lookup_error paths)."}], "metrics": [{"cvssV3_1": {"version": "3.1", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H", "baseScore": 7.8, "baseSeverity": "HIGH"}, "scenarios": [{"lang": "en", "value": "AV:L - The flaw is in cachefiles VFS directory creation reached only via local `/dev/cachefiles` ioctl/bind or local NFS/CIFS/9p fscache volume setup during mount, not from remote packet handling like nfsd or ksmbd.\nAC:L - Triggering requires only a `-ENOMEM` from `start_creating()` during `cachefiles_get_directory()`, which an attacker can reliably force with local memory pressure or repeated bind/mount attempts; no uncontrollable race or rare layout is needed once CACHEFILES is active.\nPR:L - Exploitation needs `CAP_SYS_ADMIN` to open `/dev/cachefiles` and bind the cache, or to mount a network filesystem with fscache while cachefilesd is running; both are obtainable in an unprivileged user namespace, not solely init-namespace root.\nUI:N - No separate victim action is required beyond attacker-controlled local steps (opening `/dev/cachefiles`, binding, or mounting with fscache under memory pressure); cachefilesd does not need a user to click or open a file.\nS:U - Corrupting a backing-directory inode rwsem affects kernel/VFS locking within the same host security boundary and does not cross VM, IOMMU, or container hypervisor isolation by itself.\nC:H - Double-unlocking the parent directory rwsem corrupts kernel lock state and can leave the inode lock inconsistent, enabling concurrent VFS access and memory corruption primitives that may disclose kernel memory under kernel guidance for lock corruption bugs.\nI:H - Rwsem corruption breaks directory serialization, allowing unsynchronized create/lookup/mkdir operations on cache backing storage and creating conditions for further VFS metadata corruption or control-flow manipulation consistent with high integrity impact.\nA:H - An extra `inode_unlock()` on an already-released rwsem corrupts lock owner/count state and commonly produces DEBUG_RWSEMS warnings, oopses, or kernel panics, matching high availability impact for kernel crash bugs."}]}], "affected": [{"product": "Linux", "vendor": "Linux", "defaultStatus": "unaffected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": ["fs/cachefiles/namei.c"], "versions": [{"version": "7ab96df840e60eb933abfe65fc5fe44e72f16dc0", "lessThan": "26757dac15175f2a42e3537f1ba86e62456d48f1", "status": "affected", "versionType": "git"}, {"version": "7ab96df840e60eb933abfe65fc5fe44e72f16dc0", "lessThan": "8c256fba2b46020004201c500b2a1fbc707a33ef", "status": "affected", "versionType": "git"}]}, {"product": "Linux", "vendor": "Linux", "defaultStatus": "affected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": ["fs/cachefiles/namei.c"], "versions": [{"version": "6.19", "status": "affected"}, {"version": "0", "lessThan": "6.19", "status": "unaffected", "versionType": "semver"}, {"version": "7.1.5", "lessThanOrEqual": "7.1.*", "status": "unaffected", "versionType": "semver"}, {"version": "7.2", "lessThanOrEqual": "*", "status": "unaffected", "versionType": "original_commit_for_fix"}]}], "cpeApplicability": [{"nodes": [{"operator": "OR", "negate": false, "cpeMatch": [{"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.19", "versionEndExcluding": "7.1.5"}, {"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.19", "versionEndExcluding": "7.2"}]}]}], "references": [{"url": "https://git.kernel.org/stable/c/26757dac15175f2a42e3537f1ba86e62456d48f1"}, {"url": "https://git.kernel.org/stable/c/8c256fba2b46020004201c500b2a1fbc707a33ef"}], "title": "cachefiles: Fix double unlock in nomem_d_alloc error path", "x_generator": {"engine": "bippy-1.2.0"}}}}

{}

{"affected": [{"affectedData": [{"defaultStatus": "unaffected", "product": "Linux", "programFiles": ["fs/cachefiles/namei.c"], "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "versions": [{"lessThan": "26757dac15175f2a42e3537f1ba86e62456d48f1", "status": "affected", "version": "7ab96df840e60eb933abfe65fc5fe44e72f16dc0", "versionType": "git"}, {"lessThan": "8c256fba2b46020004201c500b2a1fbc707a33ef", "status": "affected", "version": "7ab96df840e60eb933abfe65fc5fe44e72f16dc0", "versionType": "git"}]}, {"defaultStatus": "affected", "product": "Linux", "programFiles": ["fs/cachefiles/namei.c"], "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "versions": [{"status": "affected", "version": "6.19"}, {"lessThan": "6.19", "status": "unaffected", "version": "0", "versionType": "semver"}, {"lessThanOrEqual": "7.1.*", "status": "unaffected", "version": "7.1.5", "versionType": "semver"}, {"lessThanOrEqual": "*", "status": "unaffected", "version": "7.2", "versionType": "original_commit_for_fix"}]}], "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}], "cveTags": [], "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ncachefiles: Fix double unlock in nomem_d_alloc error path\n\nWhen start_creating() fails and returns -ENOMEM, it has already\nreleased the parent directory lock in __start_dirop():\n\n static struct dentry *__start_dirop(...)\n {\n ...\n inode_lock_nested(dir, I_MUTEX_PARENT);\n dentry = lookup_one_qstr_excl(name, parent, lookup_flags);\n if (IS_ERR(dentry))\n inode_unlock(dir); <-- Lock released on error\n return dentry;\n }\n\nHowever, the nomem_d_alloc error path in cachefiles_get_directory()\nunconditionally calls inode_unlock(d_inode(dir)) again, causing a\ndouble unlock that corrupts the rwsem state.\n\nThis is a leftover from commit 7ab96df840e60 which replaced manual\nlocking with start_creating() but failed to update the nomem_d_alloc\npath (while correctly updating mkdir_error and lookup_error paths)."}], "id": "CVE-2026-72368", "lastModified": "2026-08-17T06:18:41.010", "metrics": {"cvssMetricV31": [{"cvssData": {"attackComplexity": "LOW", "attackVector": "LOCAL", "availabilityImpact": "HIGH", "baseScore": 7.8, "baseSeverity": "HIGH", "confidentialityImpact": "HIGH", "integrityImpact": "HIGH", "privilegesRequired": "LOW", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H", "version": "3.1"}, "exploitabilityScore": 1.8, "impactScore": 5.9, "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "type": "Secondary"}]}, "published": "2026-08-15T06:22:10.227", "references": [{"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "url": "https://git.kernel.org/stable/c/26757dac15175f2a42e3537f1ba86e62456d48f1"}, {"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "url": "https://git.kernel.org/stable/c/8c256fba2b46020004201c500b2a1fbc707a33ef"}], "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "vulnStatus": "Received"}

{"bugzilla": {"description": "kernel: cachefiles: Fix double unlock in nomem_d_alloc error path", "id": "2516619", "url": "https://bugzilla.redhat.com/show_bug.cgi?id=2516619"}, "csaw": false, "cvss3": {"cvss3_base_score": "5.5", "cvss3_scoring_vector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H", "status": "draft"}, "cwe": "CWE-832", "details": ["In the Linux kernel, the following vulnerability has been resolved:\ncachefiles: Fix double unlock in nomem_d_alloc error path\nWhen start_creating() fails and returns -ENOMEM, it has already\nreleased the parent directory lock in __start_dirop():\nstatic struct dentry *__start_dirop(...)\n{\n...\ninode_lock_nested(dir, I_MUTEX_PARENT);\ndentry = lookup_one_qstr_excl(name, parent, lookup_flags);\nif (IS_ERR(dentry))\ninode_unlock(dir); <-- Lock released on error\nreturn dentry;\n}\nHowever, the nomem_d_alloc error path in cachefiles_get_directory()\nunconditionally calls inode_unlock(d_inode(dir)) again, causing a\ndouble unlock that corrupts the rwsem state.\nThis is a leftover from commit 7ab96df840e60 which replaced manual\nlocking with start_creating() but failed to update the nomem_d_alloc\npath (while correctly updating mkdir_error and lookup_error paths).", "A flaw was found in the `cachefiles` component of the Linux kernel. When a directory creation operation fails due to memory exhaustion, a double unlock of the parent directory lock occurs. This issue corrupts the read-write semaphore (rwsem) state, which can lead to system instability or a kernel panic, resulting in a Denial of Service (DoS)."], "name": "CVE-2026-72368", "package_state": [{"cpe": "cpe:/o:redhat:enterprise_linux:10", "fix_state": "Not affected", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 10"}, {"cpe": "cpe:/o:redhat:enterprise_linux:6", "fix_state": "Out of support scope", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 6"}, {"cpe": "cpe:/o:redhat:enterprise_linux:7", "fix_state": "Not affected", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 7"}, {"cpe": "cpe:/o:redhat:enterprise_linux:7", "fix_state": "Not affected", "package_name": "kernel-rt", "product_name": "Red Hat Enterprise Linux 7"}, {"cpe": "cpe:/o:redhat:enterprise_linux:8", "fix_state": "Not affected", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 8"}, {"cpe": "cpe:/o:redhat:enterprise_linux:8", "fix_state": "Not affected", "package_name": "kernel-rt", "product_name": "Red Hat Enterprise Linux 8"}, {"cpe": "cpe:/o:redhat:enterprise_linux:9", "fix_state": "Not affected", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 9"}, {"cpe": "cpe:/o:redhat:enterprise_linux:9", "fix_state": "Not affected", "package_name": "kernel-rt", "product_name": "Red Hat Enterprise Linux 9"}], "public_date": "2026-08-15T00:00:00Z", "references": ["https://www.cve.org/CVERecord?id=CVE-2026-72368\nhttps://nvd.nist.gov/vuln/detail/CVE-2026-72368\nhttps://lore.kernel.org/linux-cve-announce/2026081515-CVE-2026-72368-ca7c@gregkh/T"], "threat_severity": "Moderate"}

{"affected": [{"configurations": [{"platform": null, "status": "affected", "versions": {"scheme": "code_commit", "value": "[7ab96df840e60eb933abfe65fc5fe44e72f16dc0,26757dac15175f2a42e3537f1ba86e62456d48f1)"}}, {"platform": null, "status": "affected", "versions": {"scheme": "code_commit", "value": "[7ab96df840e60eb933abfe65fc5fe44e72f16dc0,8c256fba2b46020004201c500b2a1fbc707a33ef)"}}], "enrichment": {"confidence": 99.0, "confidence_source": "inferred", "scores": [{"score": 99.0, "source": "inferred"}, {"score": 100.0, "source": "matching"}]}, "original": {"product": "Linux", "source": "cna", "vendor": "Linux"}, "product": "linux_kernel", "vendor": "linux"}, {"configurations": [{"platform": null, "status": "affected", "versions": {"scheme": "generic", "value": "6.19"}}, {"platform": null, "status": "unaffected", "versions": {"scheme": "generic", "value": "[0,6.19)"}}, {"platform": null, "status": "unaffected", "versions": {"scheme": "semver", "value": "[7.1.5,7.2.0)"}}, {"platform": null, "status": "unaffected", "versions": {"scheme": "generic", "value": "[7.2-rc2,*]"}}], "enrichment": {"confidence": 99.0, "confidence_source": "inferred", "scores": [{"score": 99.0, "source": "inferred"}, {"score": 100.0, "source": "matching"}]}, "original": {"product": "Linux", "source": "cna", "vendor": "Linux"}, "product": "linux_kernel", "vendor": "linux"}], "created": "2026-08-15T10:45:06.977232+00:00", "updated": "2026-08-22T08:00:13.623857+00:00", "vendors": ["linux", "linux$PRODUCT$linux_kernel"]}