GCVE Workshop - 22 September 2026 (14:00-18:00), Luxembourg Before The Vulnopticon Conference - Registration

GHSA-JW9Q-GP66-86RQ

Vulnerability from github – Published: 2026-09-11 21:31 – Updated: 2026-09-14 15:32
VLAI
Details

In the Linux kernel, the following vulnerability has been resolved:

eventfs: Initialize ei->children and ei->list in init_ei()

eventfs_create_dir() allocates the eventfs_inode and initializes it with init_ei(). But this does not initialize the eventfs_inode list_heads. If the eventfs_create_dir() fails due to memory pressure, it will call free_ei() before it initialized the lists, and that checks to make sure the eventfs_inode has no children. But because the list wasn't initialized, it will give a false warning.

Fix it by moving the list initialization into init_ei().

[ Rewrote change log ]

Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2026-89618"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-09-11T20:19:47Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\neventfs: Initialize ei-\u003echildren and ei-\u003elist in init_ei()\n\neventfs_create_dir() allocates the eventfs_inode and initializes it with\ninit_ei(). But this does not initialize the eventfs_inode list_heads. If\nthe eventfs_create_dir() fails due to memory pressure, it will call\nfree_ei() before it initialized the lists, and that checks to make sure\nthe eventfs_inode has no children. But because the list wasn\u0027t\ninitialized, it will give a false warning.\n\nFix it by moving the list initialization into init_ei().\n\n[ Rewrote change log ]",
  "id": "GHSA-jw9q-gp66-86rq",
  "modified": "2026-09-14T15:32:32Z",
  "published": "2026-09-11T21:31:34Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-89618"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/069729282fbecfaa8a54062266c338ed23f08005"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/1704aaaf5d22bc765c168402350d191e24e245bc"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/5333e18e6b425fcc39c7fea89e3949a2a98bc5e4"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/76e0f85f650738d768449dbccbc7c55d05f5b609"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/c480f8af173d5b19c6d9c4311df6bbe352face9e"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Detection rules are retrieved from Rulezet.