{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-80869 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-80869 is a vulnerability in Linux, published on 4 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-80869 and fix it if it is affected.\n\nWhat it is: CVE-2026-80869 is a vulnerability in Linux, published on 4 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-80869 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-80869/ (Markdown: https://insights.sbomify.com/CVE-2026-80869/index.md)","id":"CVE-2026-80869","markdown":"https://insights.sbomify.com/CVE-2026-80869/index.md","name":"CVE-2026-80869","record":{"aliases":["DEBIAN-CVE-2026-80869","GHSA-3w59-j737-r4rc","UBUNTU-CVE-2026-80869"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A crafted NTFS image can cause an out-of-bounds read in the Linux kernel during mount, potentially disclosing memory contents to local attackers.","user_interaction":"required","vuln_class":"information_disclosure"},"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\nntfs: bound the attribute-list entry in ntfs_read_inode_mount()\n\nThe $MFT attribute-list walk in ntfs_read_inode_mount() validates each\nentry only with \"(u8 *)al_entry + 6 \u003e al_end\" and\n\"(u8 *)al_entry + le16_to_cpu(al_entry-\u003elength) \u003e al_end\", but then reads\nal_entry-\u003elowest_vcn (an __le64 at offset 8) and al_entry-\u003emft_reference\n(offset 16) -- fields beyond the 6 bytes proven in range. al_entry-\u003elength\nis attacker-controlled and only required non-zero, so a short entry (e.g.\nlength 8) placed at the tail passes both checks while the lowest_vcn /\nmft_reference reads fall past al_end.\n\nal_end is ni-\u003eattr_list + attr_list_size (the on-disk size); the buffer is\nkvzalloc(round_up(attr_list_size, SECTOR_SIZE)), so the sector rounding\nusually absorbs the over-read -- but when attr_list_size is a multiple of\nSECTOR_SIZE there is no slack and a crafted $MFT attribute list produces an\nout-of-bounds read at mount time.\n\nValidate the entry with ntfs_attr_list_entry_is_valid() (added in patch\n1/3) before dereferencing it, matching the bound the other attribute-list\nwalks now use. The validator already requires the length to cover the fixed\nheader, which makes the separate \"!al_entry-\u003elength\" check redundant, so\ndrop it 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 attribute-list entry in ntfs_read_inode_mount()","id":"CVE-2026-80869","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"drm/amdkfd: Validate CRIU-restored IDs before idr_alloc","id":"CVE-2026-80870"},"packages":[],"prev":{"headline":"ntfs3: Allocate iomap inline_data using alloc_page","id":"CVE-2026-80868"},"products":["Linux"],"published":"2026-09-04","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-09-04","vendors":["Linux"]},"summary":"A crafted NTFS image can cause an out-of-bounds read in the Linux kernel during mount, potentially disclosing memory contents to local attackers.","url":"https://insights.sbomify.com/CVE-2026-80869/"}