Conversation
(cherry picked from commit 3e3a583)
hxy7yx
approved these changes
Apr 29, 2026
Author
|
Thanks for the green light — let me know if any adjustment is needed before merge. |
Author
|
Thanks for taking a look, @hxy7yx. |
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
3 participants
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.
CVE-2024-10964 one-liner for v2.6 — just the
strcpy → strncpy(..., NEU_PLUGIN_LIBRARY_LEN)onhandle_add_plugin. The upstream commit also toucheshandle_update_plugin, but that function did not exist yet on v2.6 (introduced later on v2.7+), so only the add_plugin half of the diff is applicable.Deliberately did NOT import handle_update_plugin from newer branches — that would be feature-add, not a security backport. If you'd like update-plugin coverage on v2.6 too, happy to follow up separately with a proper merge from v2.7.