{
  "id": "CVE-2026-90133",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-90133",
  "published_at": "2026-09-17T16:06:33.234Z",
  "title": "ntfs: Fix index_root heap OOB write in ntfs_ir_to_ib()",
  "vendor": "Linux",
  "product": "Linux",
  "cvss": {
    "score": 7.8,
    "source": "cna",
    "vector": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "description": "In the Linux kernel, the following vulnerability has been resolved:\n\nntfs: Fix index_root heap OOB write in ntfs_ir_to_ib()\n\nntfs_ir_to_ib copies all entries from index_root into a freshly allocated\nindex_block_size-byte buffer without verifying that the entries fit in the\navailable space. The entries in index_root may be larger than the usable\nentry space in the index block.\n\nThis can cause OOB writes past the end of the allocation.\n\nThe validator ntfs_index_root_inconsistent() checks that entries are\nself-consistent within the IR value, but never cross-checks them against\nindex_block_size. There is no bounds check in ntfs_ir_to_ib() before the\nmemcpy.\n\nFixing this at the sink in ntfs_ir_to_ib() since\nntfs_index_root_inconsistent() validates the logical consistency of\nindex_root as a structure and a root with large entries is a structurally\nvalid root. The bug is a size conflict of ntfs_ir_to_ib().\nAlso, the validator is called once per inode load in\nntfs_read_locked_inode() while ntfs_ir_to_ib() is only called during a\nreparent, a check there adds no overhead to the common path.\nMoreover, even a future call path that bypasses the validator would still\nbe protected.\n\nWith NULL as first parameter of ntfs_error(), the volume error flag is\nnever set by this call, so the device name will be absent from the error\nmessage. In any case, that the caller, ntfs_ir_reparent(), prints an error\nmessage that includes the device name on NULL returns.\nI think this is the best solution available without adding\n'struct super_block *sb' as a parameter to ntfs_ir_to_ib().\n\nThis heap out-of-bounds write is triggered by a crafted filesystem image,\nwhich is not in the kernel threat model, anyway, fixing memory errors would\nbe nice to keep  things secure.",
  "cvss_by_source": {
    "cna": 7.8
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "Linux",
        "product": "Linux",
        "ranges": [
          "\u003e= 0a8ac0c1fa0b99a5b29002bc7f232ed7eafddef0, \u003c 825dec5120933e90c54e30e31ccfa6c3449043a8",
          "\u003e= 0a8ac0c1fa0b99a5b29002bc7f232ed7eafddef0, \u003c dc09bf79b76f9a7157e225f449655f3f62f96c9c"
        ],
        "fixed_in": [
          "825dec5120933e90c54e30e31ccfa6c3449043a8",
          "dc09bf79b76f9a7157e225f449655f3f62f96c9c"
        ]
      },
      {
        "vendor": "Linux",
        "product": "Linux",
        "ranges": [
          "7.1"
        ],
        "fixed_in": [
          "0",
          "7.2.6",
          "7.3"
        ]
      }
    ],
    "upgrade": [
      "Upgrade Linux to 825dec5120933e90c54e30e31ccfa6c3449043a8 or dc09bf79b76f9a7157e225f449655f3f62f96c9c or later.",
      "Upgrade Linux to 0 or 7.2.6 or 7.3 or later."
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
