fix(kubernetes): panic on empty ListenHosts#7857
Merged
Merged
Conversation
The boundIPs function checked ListenHosts with a nil comparison, which missed the case of a non-nil empty slice. Accessing index 0 on that slice caused a panic found by OSS-Fuzz. Use len() instead, matching the guard already used in the loop and trace plugins. Signed-off-by: Ville Vesilehto <ville@vesilehto.fi>
yongtang
approved these changes
Feb 16, 2026
yongtang
pushed a commit
to yongtang/coredns
that referenced
this pull request
Mar 18, 2026
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
2 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.
1. Why is this pull request needed and what does it do?
The
boundIPsfunction checkedListenHostswith anilcomparison, which missed the case of a non-nil empty slice. Accessing index 0 on that slice caused a panic found by OSS-Fuzz. Uselen()instead, matching the guard already used in the loop and trace plugins.2. Which issues (if any) are related?
Fixes OSS-Fuzz finding #482318524 (not publicly accessible).
3. Which documentation changes (if any) need to be made?
None.
4. Does this introduce a backward incompatible change or deprecation?
No.