{"id":"CVE-2026-98136","published":"2026-09-25T11:17:45.043","lastModified":"2026-09-25T11:17:45.043","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nntfs: bound $AttrDef table walk to the loaded table size\n\nntfs_attr_find_in_attrdef() walks the in-memory $AttrDef table, but the\nloop condition bounds only the start of each entry, not the whole entry:\n\n\tfor (ad = vol->attrdef; (u8 *)ad - (u8 *)vol->attrdef <\n\t\t\tvol->attrdef_size && ad->type; ++ad)\n\nstruct attr_def is 160 bytes; the guard reads ad->type at offset 128 and\nthe loop body reads further fields. vol->attrdef is kvzalloc(i_size),\nwhere i_size is the on-disk $AttrDef data size, checked in\nload_and_init_attrdef() only as 0 < i_size <= 0x7fffffff. A volume whose\n$AttrDef data size is smaller than one entry (e.g. 120 bytes) makes the\nread of ad->type run past the allocation. Creating a file reaches this\nthrough ntfs_attr_size_bounds_check() and reads out of bounds:\n\n  BUG: KASAN: slab-out-of-bounds in ntfs_attr_find_in_attrdef+0x66/0xa0\n  Read of size 4 at addr ffff888005833280 by task init/1\n   ntfs_attr_find_in_attrdef\n   ntfs_attr_size_bounds_check\n   ntfs_attr_can_be_non_resident\n   ntfs_attr_add\n\nRequire the whole entry to lie within attrdef_size in the loop guard, and\nreject at mount a $AttrDef too small to hold one attr_def entry.","cvssScore":null,"cvssSeverity":null,"cvssVector":null,"cwes":[],"vendors":[],"products":[],"references":[{"url":"https://git.kernel.org/stable/c/3e2ae47b8ebc632c27e7843a4632d9a7c060885e","tags":[]},{"url":"https://git.kernel.org/stable/c/c8504fc1245f5322af5fa5c325ab05f9cf792b87","tags":[]}],"exploitRefs":[],"hasPoc":false,"ai":null}