Skip to content

Add null checks in tensor parser to prevent SIGSEGV#19267

Merged
rascani merged 2 commits into
pytorch:mainfrom
rascani:export-D103467786
May 12, 2026
Merged

Add null checks in tensor parser to prevent SIGSEGV#19267
rascani merged 2 commits into
pytorch:mainfrom
rascani:export-D103467786

Conversation

@rascani
Copy link
Copy Markdown
Contributor

@rascani rascani commented May 1, 2026

Summary:
Add two defensive checks in tensor_parser_exec_aten.cpp:

  1. getMemPlannedPtr(): Validate that the HierarchicalAllocator pointer is non-null before dereferencing it. A null allocator causes a SIGSEGV when a model has memory-planned tensors but the caller provides zero planned buffers (T266226256 — wearables Android crash at 0.0003% hit rate).

  2. getTensorDataPtr(): When a tensor has allocation_info (indicating it expects memory-planned storage), validate that the allocator is non-null before any code path reaches getMemPlannedPtr(). This is the primary fix; the check in getMemPlannedPtr is defense-in-depth.

Differential Revision: D103467786

@pytorch-bot
Copy link
Copy Markdown

pytorch-bot Bot commented May 1, 2026

🔗 Helpful Links

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

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

❌ 1 New Failure

As of commit a46ab55 with merge base 23a91d5 (image):

NEW FAILURE - The following job has failed:

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

@meta-cla meta-cla Bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label May 1, 2026
@meta-codesync
Copy link
Copy Markdown
Contributor

meta-codesync Bot commented May 1, 2026

@rascani has exported this pull request. If you are a Meta employee, you can view the originating Diff in D103467786.

@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 1, 2026

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

Summary:
Add two defensive checks in `tensor_parser_exec_aten.cpp`:

1. `getMemPlannedPtr()`: Validate that the `HierarchicalAllocator` pointer is non-null before dereferencing it. A null allocator causes a SIGSEGV when a model has memory-planned tensors but the caller provides zero planned buffers (T266226256 — wearables Android crash at 0.0003% hit rate).

2. `getTensorDataPtr()`: When a tensor has `allocation_info` (indicating it expects memory-planned storage), validate that the allocator is non-null before any code path reaches `getMemPlannedPtr()`. This is the primary fix; the check in `getMemPlannedPtr` is defense-in-depth.

Differential Revision: D103467786
@rascani rascani force-pushed the export-D103467786 branch from 6b96a40 to f0fa552 Compare May 1, 2026 23:48
@meta-codesync
Copy link
Copy Markdown
Contributor

meta-codesync Bot commented May 11, 2026

@rascani has imported this pull request. If you are a Meta employee, you can view this in D103467786.

@rascani rascani merged commit 7ceccdf into pytorch:main May 12, 2026
176 of 177 checks passed
usamahz pushed a commit to usamahz/executorch that referenced this pull request May 13, 2026
Summary:
Add two defensive checks in `tensor_parser_exec_aten.cpp`:

1. `getMemPlannedPtr()`: Validate that the `HierarchicalAllocator`
pointer is non-null before dereferencing it. A null allocator causes a
SIGSEGV when a model has memory-planned tensors but the caller provides
zero planned buffers (T266226256 — wearables Android crash at 0.0003%
hit rate).

2. `getTensorDataPtr()`: When a tensor has `allocation_info` (indicating
it expects memory-planned storage), validate that the allocator is
non-null before any code path reaches `getMemPlannedPtr()`. This is the
primary fix; the check in `getMemPlannedPtr` is defense-in-depth.

Differential Revision: D103467786
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. fb-exported meta-exported

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants