csq: fix segfault when the VCF header has no contig lines - #2590
Merged
Conversation
In init_chr_names(), bcf_hdr_seqnames() returns nseq=0 and a non-NULL calloc(0,...) pointer (glibc) when the header has no contigs, so the !vcf guard misses and vcf[0]/strcmp() dereference garbage past a zero-length array. This crashes in init, before any record is read. Also guard nseq==0. Signed-off-by: Piotr Balwierz <balwierz@gmail.com>
Member
|
Thank you |
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.
bcftools csqsegfaults on a VCF whose header has no##contiglines — in init, before any record is read, so even a header-only VCF crashes it.In
init_chr_names(),bcf_hdr_seqnames()returnsnseq=0and a non-NULLcalloc(0,…)pointer (glibc), so the!vcfguard misses andvcf[0]/strcmp()read past a zero-length array. Fix also guardsnseq==0.