From: Georg Wild <georg.wild@gmx.de>
To: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Segfault in dvbv5-scan
Date: Sat, 06 Aug 2016 22:34:30 +0200 [thread overview]
Message-ID: <4767396.pAn5xf8Txs@acerpc.lan> (raw)
Hello,
I recently got segmentation faults when using dvbv5-scan (dvbv5-scan
-l UNIVERSAL -S1 /usr/share/dvbv5/dvb-s/Astra-19.2E).
I found out that this happened due to (d->length < len) in int isdbt_desc_delivery_init for some transponder, which results in irrealistic d->num_freqs. I did not trace back why this happens, but suggest the patch below to get at least rid of the segfault.
Additionally I found a memory leak:
1. dvb-dev.c, dvb_dev_alloc: dvb is alloc'd, dvb->d is returned, the rest is never freed.
Regards
Georg
---------------- lib/libdvbv5/descriptors/desc_isdbt_delivery.c ----------------
index 4a0f294..6623ca4 100644
@@ -36,7 +36,12 @@ int isdbt_desc_delivery_init(struct dvb_v5_fe_parms *parms,
bswap16(d->bitfield);
- d->num_freqs = (d->length - len)/ sizeof(uint16_t);
+ if (d->length < len) {
+ dvb_perror("d->length>len!!");
+ d->num_freqs=0;
+ }
+ else
+ d->num_freqs = (d->length - len)/ sizeof(uint16_t);
if (!d->num_freqs)
return 0;
d->frequency = malloc(d->num_freqs * sizeof(*d->frequency));
--------------------------- lib/libdvbv5/dvb-file.c ---------------------------
index 33481e5..169c0b5 100644
@@ -1274,6 +1274,7 @@ int dvb_store_channel(struct dvb_file **dvb_file,
return 0;
}
+ if (dvb_scan_handler->sdt->service)
dvb_sdt_service_foreach(service, dvb_scan_handler->sdt) {
char *channel = NULL;
char *vchannel = NULL;
next reply other threads:[~2016-08-06 20:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-06 20:34 Georg Wild [this message]
2016-08-07 12:10 ` Segfault in dvbv5-scan Mauro Carvalho Chehab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4767396.pAn5xf8Txs@acerpc.lan \
--to=georg.wild@gmx.de \
--cc=linux-media@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox