LiveActive security incident?Get immediate response
CVE Record

CVE-2023-54119: inotify: Avoid reporting event with invalid wd

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).

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can cause inotify, a file-change notification mechanism, to report an invalid watch descriptor to user space during a race condition. The published description frames the impact as confusing the inotify listener, not as code execution or privilege escalation.

Executive priority

Treat this as a kernel correctness issue with uncertain severity. Address through routine kernel patch governance, elevating priority for systems where missed or malformed file-event monitoring could affect security controls or operations.

Technical view

A race between inotify_freeing_mark() and inotify_handle_inode_event() can let i_mark->wd be observed after reset to -1. The fix validates that the watch descriptor is sensible and treats invalid cases as if the mark was removed before event generation.

Likely exposure

Exposure is limited to Linux systems running affected kernel versions or downstream builds without the referenced stable fixes. The bundle lists Linux kernel affected version records but does not provide precise distribution package status.

Exploitation context

The source bundle does not cite active exploitation, public exploit code, KEV inclusion, CVSS, or CWE mapping. The described effect is incorrect event reporting to user space, which may affect applications relying on inotify correctness.

Researcher notes

The key condition is a race where a freeing mark and inode event handling overlap, exposing wd=-1 to user space. Evidence does not establish a security boundary bypass, exploitability, or broad impact beyond listener confusion.

Mitigation direction

  • Inventory Linux kernel versions across servers, appliances, containers hosts, and endpoints.
  • Review Linux stable commits and distribution advisories for the backported fix.
  • Patch or upgrade kernels through vendor-supported update channels when available.
  • Prioritize systems where security tooling or applications rely on inotify events.
  • Track vendor guidance because CVSS, CWE, and distribution status are incomplete.

Validation and detection

  • Compare running kernel versions with the CVE record and distribution advisories.
  • Check whether referenced Linux stable fixes are present in source or package changelogs.
  • Identify services that consume inotify events and assess operational sensitivity.
  • Confirm updated systems booted into the patched kernel after maintenance.
  • Document exceptions where vendor fix status remains unavailable.
Prepared
Confidence
medium
Sources
9

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-54119 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
8Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux7e790dd5fc937bc8d2400c30a05e32a9e9eef276, 7e790dd5fc937bc8d2400c30a05e32a9e9eef276, 7e790dd5fc937bc8d2400c30a05e32a9e9eef276, 7e790dd5fc937bc8d2400c30a05e32a9e9eef276, 7e790dd5fc937bc8d2400c30a05e32a9e9eef276, 7e790dd5fc937bc8d2400c30a05e32a9e9eef276, 7e790dd5fc937bc8d2400c30a05e32a9e9eef276unaffected
LinuxLinux2.6.31, 0, 5.4.243, 5.10.180, 5.15.112, 6.1.29, 6.2.16, 6.3.3, 6.4affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.