configfs: pin the symlink target's dirent instead of chasing ->ci_dentry
In the Linux kernel, the following vulnerability has been resolved: configfs: pin the symlink target's dirent instead of chasing ->ci_dentry create_link() reads the target's configfs_dirent from item->ci_dentry->d_fsdata, relying on the item reference taken by get_target(). That reference pins the item, not its dentry: the dentry is pinned by DCACHE_PERSISTENT, which configfs_remove_dir() releases via simple_rmdir() while the item is still alive. A symlink racing with rmdir of its target can therefore find ->ci_dentry freed and its dirent released, triggering WARN_ON(!atomic_read(&sd->s_count)) in configfs_get(). Take the dirent in get_target() as well, under ->d_lock and atomically with the item reference, and pass it down to create_link(). A hashed dentry has not been killed yet, so its ->d_fsdata reference keeps the dirent alive there.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.12.112, 6.18.53, 6.6.160, 7.2.7
- CVEs
- CVE-2026-97950
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 4 Nov 2026, 18:58 UTC · Revision 1
Source evidence
configfs: pin the symlink target's dirent instead of chasing ->ci_dentry
core-osv · Original sourcePublished 25 Sept 2026, 10:22 UTC
In the Linux kernel, the following vulnerability has been resolved: configfs: pin the symlink target's dirent instead of chasing ->ci_dentry create_link() reads the target's configfs_dirent from item->ci_dentry->d_fsdata, relying on the item reference taken by get_target(). That reference pins the item, not its dentry: the dentry is pinned by DCACHE_PERSISTENT, which configfs_remove_dir() releases via simple_rmdir() while the item is still alive. A symlink racing with rmdir of its target can therefore find ->ci_dentry freed and its dirent released, triggering WARN_ON(!atomic_read(&sd->s_count)) in configfs_get(). Take the dirent in get_target() as well, under ->d_lock and atomically with the item reference, and pass it down to create_link(). A hashed dentry has not been killed yet, so its ->d_fsdata reference keeps the dirent alive there.
osv:CVE-2026-97950
Kernel
Fixed versions: 6.6.160, 6.12.112, 6.18.53, 7.2.7
Complete source record
{
"id": "edd854c70d4e86389dcb0ce53c9e6e78a775ce79b795ad1672632bef94128388",
"url": "https://osv.dev/vulnerability/CVE-2026-97950",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "configfs: pin the symlink target's dirent instead of chasing ->ci_dentry",
"summary": "In the Linux kernel, the following vulnerability has been resolved: configfs: pin the symlink target's dirent instead of chasing ->ci_dentry create_link() reads the target's configfs_dirent from item->ci_dentry->d_fsdata, relying on the item reference taken by get_target(). That reference pins the item, not its dentry: the dentry is pinned by DCACHE_PERSISTENT, which configfs_remove_dir() releases via simple_rmdir() while the item is still alive. A symlink racing with rmdir of its target can therefore find ->ci_dentry freed and its dirent released, triggering WARN_ON(!atomic_read(&sd->s_count)) in configfs_get(). Take the dirent in get_target() as well, under ->d_lock and atomically with the item reference, and pass it down to create_link(). A hashed dentry has not been killed yet, so its ->d_fsdata reference keeps the dirent alive there.",
"evidence": "osv:CVE-2026-97950",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.6.160",
"evidence": "/affected/1/ranges"
},
{
"value": "6.12.112",
"evidence": "/affected/1/ranges"
},
{
"value": "6.18.53",
"evidence": "/affected/1/ranges"
},
{
"value": "7.2.7",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2026-97950",
"aliases": [
"CVE-2026-97950"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "7063fbf2261194f72ee75afca67b3b38b554b5fa"
},
{
"fixed": "a44744454eafbc158e8c8e3ef8d207076410b195"
},
{
"fixed": "846ff40fd57a47e59a41f4e331ec3b34efaddc23"
},
{
"fixed": "4f54beb2e7f6d399396466682fba3539bcdcb414"
},
{
"fixed": "d47c5de1cd6bfbe1067fc310bf90e4e00205e839"
},
{
"fixed": "a7c1290eef60711c10289c056ad32ed1f2b47b12"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-97950.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "2.6.16"
},
{
"fixed": "6.6.160"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.12.112"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.18.53"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "7.2.7"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-97950.json"
}
}
],
"modified": "2026-10-28T02:30:38.514041217Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/4f54beb2e7f6d399396466682fba3539bcdcb414",
"https://git.kernel.org/stable/c/846ff40fd57a47e59a41f4e331ec3b34efaddc23",
"https://git.kernel.org/stable/c/a44744454eafbc158e8c8e3ef8d207076410b195",
"https://git.kernel.org/stable/c/a7c1290eef60711c10289c056ad32ed1f2b47b12",
"https://git.kernel.org/stable/c/d47c5de1cd6bfbe1067fc310bf90e4e00205e839",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/97xxx/CVE-2026-97950.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-97950",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/97xxx/CVE-2026-97950.json"
}
},
"related_cves": [
{
"value": "CVE-2026-97950",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 505928,
"published_at": "2026-09-25T10:22:58.97+00:00"
}