[GHSA-f4hp-rmr7-r7v8] PyTorch is Vulnerable to Memory Consumption through pad_packed_sequence Function - #9773
Open
JacobMenge wants to merge 1 commit into
Conversation
github-actions
Bot
changed the base branch from
main
to
JacobMenge/advisory-improvement-9773
September 24, 2026 19:58
Author
|
Hi! Quick note: I didn't mean to remove the CVSS v3 score. The improvement form only shows CVSS v4, so it got dropped automatically. Please keep the existing v3 score. The only changes I intended are the fixed version (2.10.0) and the added PR link. Thanks! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updates
Comments
The fix for this issue (commit 494518046816d29099b7d056a74ffa5c244fdcdd,
PR #167521 "Add empty tensor check for _pad_packed_sequence") was merged on
2025-11-11 and closes pytorch/pytorch#149622. The commit is included in the
v2.10.0 release tag but not in v2.9.0 or v2.9.1, so versions 2.7.0 through
2.9.1 are also affected. The affected range should therefore be < 2.10.0 with
2.10.0 as the first patched version.