{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90048 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90048 is a critical memory corruption 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-90048 and fix it if it is affected.\n\nWhat it is: CVE-2026-90048 is a critical memory corruption 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-90048 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-90048/ (Markdown: https://insights.sbomify.com/CVE-2026-90048/index.md)","id":"CVE-2026-90048","markdown":"https://insights.sbomify.com/CVE-2026-90048/index.md","name":"CVE-2026-90048","record":{"aliases":["AZL-101576","BELL-CVE-2026-90048","DEBIAN-CVE-2026-90048","GHSA-rmc3-723g-fx4m","UBUNTU-CVE-2026-90048"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Linux kernel NTFS3","requires_auth":"none","summary":"A local attacker can trigger a heap buffer overflow in the Linux kernel NTFS3 driver via a crafted image, potentially leading to code execution or privilege escalation.","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\nfs/ntfs3: fix slab-out-of-bounds write in ni_create_attr_list()\n\nni_create_attr_list() allocates a fixed buffer of al_aligned(record_size)\n(== record_size) bytes and then walks every attribute of the primary MFT\nrecord, writing one ATTR_LIST_ENTRY per attribute and advancing the cursor\nby le_size(name_len), with no check against the end of the buffer; the\ntotal size is only computed after the loop.\n\nA minimum-size resident attribute occupies SIZEOF_RESIDENT (0x18 = 24)\nbytes on disk, but an unnamed attribute expands to le_size(0) (0x20 = 32)\nbytes in the list.  Because the number of attributes in a record is not\nbounded (mi_enum_attr() accepts arbitrarily many equal-type, nameless\nminimum-size attributes), a crafted record packed with such attributes\nproduces a list larger than record_size and overflows the heap buffer.\n\nThis is reachable from a crafted, loop-mounted NTFS image: opening the file\nand adding an attribute (e.g. via setxattr) drives ntfs_set_ea() -\u003e\nni_insert_resident() -\u003e ni_insert_attr() -\u003e ni_ins_attr_ext() -\u003e\nni_create_attr_list().\n\n  BUG: KASAN: slab-out-of-bounds in ni_create_attr_list+0xc48/0x1058\n  Write of size 4 at addr ffff000008984c00 by task setfattr/345\n   ni_create_attr_list+0xc48/0x1058\n   ni_ins_attr_ext+0x510/0x7c0\n   ni_insert_attr+0x3f8/0x70c\n   ni_insert_resident+0xc8/0x3b0\n   ntfs_set_ea+0x66c/0xd28\n   ntfs_setxattr+0x4d8/0x5b0\n   __arm64_sys_setxattr+0xa4/0x124\n  Allocated by task 345:\n   ni_create_attr_list+0x188/0x1058\n  The buggy address belongs to the cache kmalloc-1k of size 1024\n  (the write lands at object+1024).\n\nSize the buffer from the actual attributes instead of assuming a single\nrecord_size is always enough.","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: fix slab-out-of-bounds write in ni_create_attr_list()","id":"CVE-2026-90048","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"net: skbuff: don't skb_tx_error() the source skb in skb_zerocopy()","id":"CVE-2026-90049"},"packages":[],"prev":{"headline":"drm/xe: Don't hand out the flat CCS storage as usable VRAM","id":"CVE-2026-90047"},"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 trigger a heap buffer overflow in the Linux kernel NTFS3 driver via a crafted image, potentially leading to code execution or privilege escalation.","url":"https://insights.sbomify.com/CVE-2026-90048/"}