Integer overflow in HierarchicalAllocator::get_offset_address()

[pytorchbot]

Stack from ghstack (oldest at bottom):

• -> Integer overflow in HierarchicalAllocator::get_offset_address() #12699
• Out-of-bounds accesses in operator execution #12698
• Check for buffer overflow in prim_ops::et_copy_index() #12697

^
Test on top of D78676341.

Differential Revision: D78703809

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/12828

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

❗ 1 Active SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

• Replace all macOS instances with nextjs due CVE-2025-55182

❌ 5 New Failures, 10 Pending

As of commit 0830af8 with merge base de24489 ():

NEW FAILURES - The following jobs have failed:

• pull / test-eval_llama-mmlu-linux / linux-job (gh)
  RuntimeError: Command docker exec -t 172c06308c8159301f8270351068ac80aa063b403f287254cb129e5c551fe38d /exec failed with exit code 1
• pull / test-eval_llama-wikitext-linux / linux-job (gh)
  RuntimeError: Command docker exec -t 1be69d32fea5c76abcee898a251d2e0bb537a8e133c14234f9d4be99a0aed496 /exec failed with exit code 1
• pull / test-llama-runner-qnn-linux (fp32, qnn_16a16w, qnn) / linux-job (gh)
  RuntimeError: Command docker exec -t 990aa66dc9b40e2b42d63cafc16c8bf1b6ac5ed9a510a316b41f33df7f80e0e1 /exec failed with exit code 1
• pull / unittest-arm-backend-with-no-fvp (test_pytest_models) / linux-job (gh)
  RuntimeError: Command docker exec -t abfc6db2c37f5aedd7e58cc3930b25f9bed72f1736ea97b04152e670d24ca1a5 /exec failed with exit code 1
• pull / unittest-arm-backend-with-no-fvp (test_pytest_ops) / linux-job (gh)
  RuntimeError: Command docker exec -t 00e01a557a69282f015897168d794ac0751bfa41eb0b87adc18697c17bc5840c /exec failed with exit code 1

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[github-actions]

Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as Stale.
Feel free to remove the Stale label if you feel this was a mistake.
If you are unable to remove the Stale label please contact a maintainer in order to do so.
If you want the bot to never mark this PR stale again, add the no-stale label.
Stale pull requests will automatically be closed after 30 days of inactivity.