{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89618 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89618 is a vulnerability in Linux, published on 11 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-89618 and fix it if it is affected.\n\nWhat it is: CVE-2026-89618 is a vulnerability in Linux, published on 11 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-89618 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-89618/ (Markdown: https://insights.sbomify.com/CVE-2026-89618/index.md)","id":"CVE-2026-89618","markdown":"https://insights.sbomify.com/CVE-2026-89618/index.md","name":"CVE-2026-89618","record":{"aliases":["AZL-100584","BELL-CVE-2026-89618","DEBIAN-CVE-2026-89618","GHSA-jw9q-gp66-86rq","UBUNTU-CVE-2026-89618"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A missing initialization in the Linux kernel eventfs subsystem can cause a false warning and potential crash during memory pressure, leading to denial of service.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"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't\ninitialized, it will give a false warning.\n\nFix it by moving the list initialization into init_ei().\n\n[ Rewrote change log ]","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"eventfs: Initialize ei-\u003echildren and ei-\u003elist in init_ei()","id":"CVE-2026-89618","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"HID: intel-thc-hid: intel-quickspi: bound GET_REPORT response to the caller buffer","id":"CVE-2026-89619"},"packages":[],"prev":{"headline":"fs/ntfs3: validate dirty page table on log replay","id":"CVE-2026-89617"},"products":["Linux"],"published":"2026-09-11","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A missing initialization in the Linux kernel eventfs subsystem can cause a false warning and potential crash during memory pressure, leading to denial of service.","url":"https://insights.sbomify.com/CVE-2026-89618/"}