CVE-2023-54119: inotify: Avoid reporting event with invalid wd
Noroxi assessment
Priority: Monitor (action score 0/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.21% (FIRST EPSS).
- Fixed version: Linux Linux 145f54ea336b06cf4f92eeee996f2ffca939ea43, 17ad86d8c12220de97e80d88b5b4c934a40e1812, 2d65c97777e5b4a845637800d5d7b648f5772106.
Low priority for now. Upgrade to Linux Linux 145f54ea336b06cf4f92eeee996f2ffca939ea43, 17ad86d8c12220de97e80d88b5b4c934a40e1812, 2d65c97777e5b4a845637800d5d7b648f5772106 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: inotify: Avoid reporting event with invalid wd When inotify_freeing_mark() races with inotify_handle_inode_event() it can happen that inotify_handle_inode_event() sees that i_mark->wd got already reset to -1 and reports this value to userspace which can confuse the inotify listener. Avoid the problem by validating that wd is sensible (and pretend the mark got removed before the event got generated otherwise).
- Published
- Dec 24, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
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.31affected
- 7e790dd5fc937bc8d2400c30a05e32a9e9eef276 and later · before 8fb33166aed888769ea63d6af49515893f8a1f14affected · git
- 7e790dd5fc937bc8d2400c30a05e32a9e9eef276 and later · before 2d65c97777e5b4a845637800d5d7b648f5772106affected · git
- 7e790dd5fc937bc8d2400c30a05e32a9e9eef276 and later · before 17ad86d8c12220de97e80d88b5b4c934a40e1812affected · git
- 7e790dd5fc937bc8d2400c30a05e32a9e9eef276 and later · before 145f54ea336b06cf4f92eeee996f2ffca939ea43affected · git
- 7e790dd5fc937bc8d2400c30a05e32a9e9eef276 and later · before fb3294998489d39835006240e9c6e6b2ac62022eaffected · git
- 7e790dd5fc937bc8d2400c30a05e32a9e9eef276 and later · before a48bacee05860c6089c3482bcdc80720b0ee5732affected · git
- 7e790dd5fc937bc8d2400c30a05e32a9e9eef276 and later · before c915d8f5918bea7c3962b09b8884ca128bfd9b0caffected · git
- before 2.6.31not affected · semver
- 5.4.243 and later · up to and including 5.4.*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.37-1 | 6.1.37-1 |
| Debian:13 | linux | before 6.3.7-1 | 6.3.7-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-2023-54117Dec 24, 2025 · s390/dcssblk: fix kernel crash with list_add corruption0Monitor
- ← EarlierCVE-2023-54118Dec 24, 2025 · serial: sc16is7xx: setup GPIO controller later in probe0Monitor
- Later →CVE-2023-54121Dec 24, 2025 · btrfs: fix incorrect splitting in btrfs_drop_extent_map_range31Monitor
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 | 145f54ea336b06cf4f92eeee996f2ffca939ea43 | Vendor (CNA) |
| Linux Linux | 17ad86d8c12220de97e80d88b5b4c934a40e1812 | Vendor (CNA) |
| Linux Linux | 2d65c97777e5b4a845637800d5d7b648f5772106 | Vendor (CNA) |
| Linux Linux | 8fb33166aed888769ea63d6af49515893f8a1f14 | Vendor (CNA) |
| Linux Linux | a48bacee05860c6089c3482bcdc80720b0ee5732 | Vendor (CNA) |
| Linux Linux | c915d8f5918bea7c3962b09b8884ca128bfd9b0c | Vendor (CNA) |
| Linux Linux | fb3294998489d39835006240e9c6e6b2ac62022e | Vendor (CNA) |
| debian:linux | 6.1.37-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.
No history yet (it accumulates with the daily EPSS job).
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
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/17ad86d8c12220de97e80d88b5b4c934a40e1812
- git.kernel.org/stable/c/2d65c97777e5b4a845637800d5d7b648f5772106
- git.kernel.org/stable/c/8fb33166aed888769ea63d6af49515893f8a1f14
- git.kernel.org/stable/c/a48bacee05860c6089c3482bcdc80720b0ee5732
- git.kernel.org/stable/c/c915d8f5918bea7c3962b09b8884ca128bfd9b0c
- git.kernel.org/stable/c/fb3294998489d39835006240e9c6e6b2ac62022e
Vendor advisories and official records. Exploit/PoC links are deliberately left out.