From: Andrey Karelin <a.karelin@ideco.ru>
To: Mauro Carvalho Chehab <mchehab@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Andrey Karelin <a.karelin@ideco.ru>,
Hans Verkuil <hverkuil+cisco@kernel.org>,
linux-media@vger.kernel.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org, lvc-project@linuxtesting.org
Subject: [PATCH 0/3] staging: media: av7110: check demux and net initialization in av7110_register()
Date: Mon, 2 Nov 2026 17:51:28 +0500 [thread overview]
Message-ID: <20261102125149.82725-1-a.karelin@ideco.ru> (raw)
av7110_register() ignores the return values of dvb_dmx_init(),
dvb_dmxdev_init() and dvb_net_init() for both the main and the optional
budget-patch demux. On failure probing continues with half-initialized
objects, which leads to NULL pointer dereferences on first use or on
device removal. av7110_attach() does not call dvb_unregister() when
av7110_register() fails, so with this series av7110_register() unwinds
what it has set up on its own.
Andrey Karelin (3):
staging: media: av7110: check dvb_dmx_init() result in
av7110_register()
staging: media: av7110: check dvb_dmxdev_init() result in
av7110_register()
staging: media: av7110: check dvb_net_init() result in
av7110_register()
drivers/staging/media/av7110/av7110.c | 49 ++++++++++++++++++++++-----
1 file changed, 40 insertions(+), 9 deletions(-)
base-commit: 6628e7d4c6b25c8d18f1345e3a20d21829aae7e4
--
2.56.0
next reply other threads:[~2026-11-02 12:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 12:51 Andrey Karelin [this message]
2026-11-02 12:51 ` [PATCH 1/3] staging: media: av7110: check dvb_dmx_init() result " Andrey Karelin
2026-11-02 12:51 ` [PATCH 2/3] staging: media: av7110: check dvb_dmxdev_init() " Andrey Karelin
2026-11-02 12:51 ` [PATCH 3/3] staging: media: av7110: check dvb_net_init() " Andrey Karelin
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=20261102125149.82725-1-a.karelin@ideco.ru \
--to=a.karelin@ideco.ru \
--cc=gregkh@linuxfoundation.org \
--cc=hverkuil+cisco@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=lvc-project@linuxtesting.org \
--cc=mchehab@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
all inboxes | Powered by JetHome®