{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72478 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72478 is a high-severity memory corruption vulnerability in Linux, published on 15 Aug 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-72478 and fix it if it is affected.\n\nWhat it is: CVE-2026-72478 is a high-severity memory corruption vulnerability in Linux, published on 15 Aug 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-72478 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-72478/ (Markdown: https://insights.sbomify.com/CVE-2026-72478/index.md)","id":"CVE-2026-72478","markdown":"https://insights.sbomify.com/CVE-2026-72478/index.md","name":"CVE-2026-72478","record":{"aliases":["BELL-CVE-2026-72478","DEBIAN-CVE-2026-72478","GHSA-pcrg-m6wx-53ch","UBUNTU-CVE-2026-72478"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel NTFS3","requires_auth":"none","summary":"A missing bounds check in the Linux kernel NTFS3 driver allows out-of-bounds reads during mount, potentially causing crashes or leaking memory.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":8.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/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\nfs/ntfs3: add bounds check to run_get_highest_vcn()\n\nrun_get_highest_vcn() parses a packed NTFS mapping-pairs buffer without\nany length bound, relying solely on a 0x00 terminator to stop.  A\ncrafted $LogFile UpdateMappingPairs record whose embedded attribute\ncontains mapping-pairs runs without a terminator causes the function to\nread past the slab allocation, triggering a KASAN slab-out-of-bounds\nread on mount.\n\nThe sibling function run_unpack() received an analogous bounds-check in\ncommit b62567bca474 (\"ntfs3: add buffer boundary checks to run_unpack()\"),\nbut run_get_highest_vcn() was missed.\n\nTake a run_buf_size parameter and reject any run header whose payload\nwould extend past the buffer end, mirroring the pattern used by\nrun_unpack().  The caller in fslog.c passes the remaining attribute\nbytes after the mapping-pairs offset.\n\nKASAN report (on mainline v7.1 merge window HEAD):\n\n  BUG: KASAN: slab-out-of-bounds in run_get_highest_vcn+0x3c0/0x410\n  Read of size 1 at addr ffff88800e2d5400 by task mount/72\n  Call Trace:\n   run_get_highest_vcn+0x3c0/0x410\n   do_action.isra.0+0x3ba8/0x7b50\n   log_replay+0x9ddd/0x10200\n   ntfs_loadlog_and_replay+0x4ad/0x610\n   ntfs_fill_super+0x214a/0x4540","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: add bounds check to run_get_highest_vcn()","id":"CVE-2026-72478","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"iio: accel: mma8452: handle I2C read error(s) in mma8452_read()","id":"CVE-2026-72479"},"packages":[],"prev":{"headline":"fs/ntfs3: call _ntfs_bad_inode() when failing to rename","id":"CVE-2026-72477"},"products":["Linux"],"published":"2026-08-15","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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-16","vendors":["Linux"]},"summary":"A missing bounds check in the Linux kernel NTFS3 driver allows out-of-bounds reads during mount, potentially causing crashes or leaking memory.","url":"https://insights.sbomify.com/CVE-2026-72478/"}