CVE-2026-74359: configfs_lookup(): don't leave ->s_dentry dangling on failure
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.12% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 10da12d352b7b2bb330a8609fdda9a58bf0e9856, 3e83b2203aa59bd279e4f677ec793d49dc9d019e, 57088b06109f3222963c639d8d743f42c2899b13.
Low priority for now. Upgrade to Linux Linux 10da12d352b7b2bb330a8609fdda9a58bf0e9856, 3e83b2203aa59bd279e4f677ec793d49dc9d019e, 57088b06109f3222963c639d8d743f42c2899b13 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: configfs_lookup(): don't leave ->s_dentry dangling on failure Normally ->s_dentry is cleared when dentry it's pointing to becomes negative (on eviction, realistically). However, that only happens if dentry gets to be positive in the first place; in case of inode allocation failure dentry never becomes positive, so ->d_iput() is not called at all. We do part of what normally would've been done by configfs_d_iput() (dropping the reference to configfs_dirent) manually, but we do not clear ->s_dentry there. Sloppy as it is, it does not matter in case of configfs_create_{dir,link}() - there configfs_dirent does not survive dropping the sole reference to it. However, for configfs_lookup() it *does* survive, with a dangling pointer to soon to be freed dentry sitting it its ->s_dentry. Subsequent getdents(2) in that directory will end up dereferencing that pointer in order to pick the inode number. Use after free... This is the minimal fix; the right approach is to set the linkage between dentry and configfs_dirent only after we know that we have an inode, but that takes more surgery and the bug had been there since 2006, so...
- Published
- Aug 15, 2026
- Updated
- Oct 16, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- —
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.16affected
- 3d0f89bb169482d26d5aa4e82e763077e7e9bc4d and later · before 3e83b2203aa59bd279e4f677ec793d49dc9d019eaffected · git
- 3d0f89bb169482d26d5aa4e82e763077e7e9bc4d and later · before b6e9c82522ddaa3ac0706b295ff4a71975d4f883affected · git
- 3d0f89bb169482d26d5aa4e82e763077e7e9bc4d and later · before eee07d769da5ac4e4f7bd0bc17828646a318d499affected · git
- 3d0f89bb169482d26d5aa4e82e763077e7e9bc4d and later · before 9c747dcee164ead300de90550ad9e4122f0d1bbbaffected · git
- 3d0f89bb169482d26d5aa4e82e763077e7e9bc4d and later · before c3b073a209a9baa691b744318ac929fecdd8847caffected · git
- 3d0f89bb169482d26d5aa4e82e763077e7e9bc4d and later · before 57088b06109f3222963c639d8d743f42c2899b13affected · git
- 3d0f89bb169482d26d5aa4e82e763077e7e9bc4d and later · before 10da12d352b7b2bb330a8609fdda9a58bf0e9856affected · git
- before 2.6.16not affected · semver
- 5.15.212 and later · up to and including 5.15.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.180-1 | 6.1.180-1 |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-74355Aug 15, 2026 · iommu/vt-d: Fix RB-tree corruption in probe error path32Monitor
- ← EarlierCVE-2026-74356Aug 15, 2026 · vhost: fix vhost_get_avail_idx for a non empty ring29Monitor
- Later →CVE-2026-74361Aug 15, 2026 · nvme: fix FDP fdpcidx bounds check39Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 10da12d352b7b2bb330a8609fdda9a58bf0e9856 | Vendor (CNA) |
| Linux Linux | 3e83b2203aa59bd279e4f677ec793d49dc9d019e | Vendor (CNA) |
| Linux Linux | 57088b06109f3222963c639d8d743f42c2899b13 | Vendor (CNA) |
| Linux Linux | 9c747dcee164ead300de90550ad9e4122f0d1bbb | Vendor (CNA) |
| Linux Linux | b6e9c82522ddaa3ac0706b295ff4a71975d4f883 | Vendor (CNA) |
| Linux Linux | c3b073a209a9baa691b744318ac929fecdd8847c | Vendor (CNA) |
| Linux Linux | eee07d769da5ac4e4f7bd0bc17828646a318d499 | Vendor (CNA) |
| debian:linux | 6.1.180-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/3e83b2203aa59bd279e4f677ec793d49dc9d019e
- git.kernel.org/stable/c/57088b06109f3222963c639d8d743f42c2899b13
- git.kernel.org/stable/c/9c747dcee164ead300de90550ad9e4122f0d1bbb
- git.kernel.org/stable/c/b6e9c82522ddaa3ac0706b295ff4a71975d4f883
- git.kernel.org/stable/c/c3b073a209a9baa691b744318ac929fecdd8847c
- git.kernel.org/stable/c/eee07d769da5ac4e4f7bd0bc17828646a318d499
Vendor advisories and official records. Exploit/PoC links are deliberately left out.