{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-80673 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-80673 is a critical memory corruption vulnerability in Linux, published on 28 Aug 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-80673 and fix it if it is affected.\n\nWhat it is: CVE-2026-80673 is a critical memory corruption vulnerability in Linux, published on 28 Aug 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-80673 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-80673/ (Markdown: https://insights.sbomify.com/CVE-2026-80673/index.md)","id":"CVE-2026-80673","markdown":"https://insights.sbomify.com/CVE-2026-80673/index.md","name":"CVE-2026-80673","record":{"aliases":["DEBIAN-CVE-2026-80673","GHSA-hmfm-f852-mmj6","UBUNTU-CVE-2026-80673"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Linux kernel NTFS","requires_auth":"none","summary":"A crafted NTFS image triggers an out-of-bounds read in the Linux kernel, potentially leaking memory or causing a crash.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nntfs: bound the look-ahead attribute-list entry in ntfs_external_attr_find()\n\nWhen resolving an attribute lookup with a non-zero @lowest_vcn,\nntfs_external_attr_find() peeks at the next $ATTRIBUTE_LIST entry to\ndecide whether to keep searching, but bounds that not-yet-validated\nentry only with \"(u8 *)next_al_entry + 6 \u003c al_end\" (which proves just\nbytes 0..6 are in range) and \"(u8 *)next_al_entry + length \u003c= al_end\"\nwith an attacker-controlled, non-8-aligned length. It then reads\nnext_al_entry-\u003elowest_vcn (an __le64 at offset 8) and the name at\nnext_al_entry-\u003ename_offset, both of which can lie past al_end -- the\nexact end of the kvmalloc'd attribute-list buffer (allocated at the\non-disk attr_list_size, no rounding). A crafted on-disk $ATTRIBUTE_LIST\nwhose last entry sits a few bytes before al_end therefore yields a slab\nout-of-bounds read when the inode is read.\n\nValidate the look-ahead entry with ntfs_attr_list_entry_is_valid() (added\nin patch 1/3) before dereferencing lowest_vcn and the name, so the same\nfixed-header, length and name bounds the main attribute-list walk uses now\nguard this read too.","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":"ntfs: bound the look-ahead attribute-list entry in ntfs_external_attr_find()","id":"CVE-2026-80673","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"ntfs: validate resident attribute lists and harden the validator","id":"CVE-2026-80674"},"packages":[],"prev":{"headline":"ntfs: fix u16 truncation of restart-area length check","id":"CVE-2026-80672"},"products":["Linux"],"published":"2026-08-28","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-08-29","vendors":["Linux"]},"summary":"A crafted NTFS image triggers an out-of-bounds read in the Linux kernel, potentially leaking memory or causing a crash.","url":"https://insights.sbomify.com/CVE-2026-80673/"}