{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89779 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89779 is a critical vulnerability in Linux, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-89779 and fix it if it is affected.\n\nWhat it is: CVE-2026-89779 is a critical vulnerability in Linux, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-89779 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-89779/ (Markdown: https://insights.sbomify.com/CVE-2026-89779/index.md)","id":"CVE-2026-89779","markdown":"https://insights.sbomify.com/CVE-2026-89779/index.md","name":"CVE-2026-89779","record":{"aliases":["AZL-101265","BELL-CVE-2026-89779","DEBIAN-CVE-2026-89779","GHSA-gg5m-j9gf-rmhm","UBUNTU-CVE-2026-89779"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Linux kernel NTFS3","requires_auth":"none","summary":"A local attacker can leak heap memory by mounting a crafted NTFS image, exploiting a missing size validation in the Linux kernel's NTFS3 driver.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nfs/ntfs3: validate ef-\u003esize covers the record's name and value\n\nWhen an EA record has a non-zero ef-\u003esize, ntfs_read_ea() only checks\nthat the record fits in the remaining buffer (ea_size \u003e bytes), not that\nef-\u003esize is large enough to hold the record's own name_len + 1 + elength.\n\nA crafted image can pass validation with, e.g., ef-\u003esize = 24 but\nelength = 0xffff. ntfs_get_ea() then trusts elength and copies it out of\nthe undersized record, reading past the kmalloc(info-\u003esize) allocation\nand leaking heap memory to userspace via getxattr():\n\n BUG: KASAN: slab-out-of-bounds in ntfs_get_ea (fs/ntfs3/xattr.c:302)\n Read of size 65535 at addr ffff888100794550 by task exploit\n  __asan_memcpy (mm/kasan/shadow.c:105)\n  ntfs_get_ea (fs/ntfs3/xattr.c:302)\n  ntfs_getxattr (fs/ntfs3/xattr.c:848)\n  __vfs_getxattr (fs/xattr.c:441)\n  vfs_getxattr (fs/xattr.c:474)\n  do_getxattr (fs/xattr.c:800)\n  path_getxattrat (fs/xattr.c:868)\n  do_syscall_64 (arch/x86/entry/syscall_64.c:94)\n\n The buggy address is located 80 bytes inside of\n  allocated 84-byte region in cache kmalloc-96\n\nCompute the size the record needs and require ef-\u003esize to cover it.","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":"fs/ntfs3: validate ef-\u003esize covers the record's name and value","id":"CVE-2026-89779","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"net: qualcomm: rmnet: restore skb-\u003edev on deaggregated frames","id":"CVE-2026-89780"},"packages":[],"prev":{"headline":"isofs: fix out-of-bounds page array access on empty zisofs block","id":"CVE-2026-89778"},"products":["Linux"],"published":"2026-09-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A local attacker can leak heap memory by mounting a crafted NTFS image, exploiting a missing size validation in the Linux kernel's NTFS3 driver.","url":"https://insights.sbomify.com/CVE-2026-89779/"}