CVE-2022-50725 json
media: vidtv: Fix use-after-free in vidtv_bridge_dvb_init()
published 2025-12-24 10 mo ago modified 2026-06-17 4 mo ago also EUVD-2022-55764
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 14%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
media: vidtv: Fix use-after-free in vidtv_bridge_dvb_init()
KASAN reports a use-after-free: BUG: KASAN: use-after-free in dvb_dmxdev_release+0x4d5/0x5d0 [dvb_core] Call Trace: ... dvb_dmxdev_release+0x4d5/0x5d0 [dvb_core] vidtv_bridge_probe+0x7bf/0xa40 [dvb_vidtv_bridge] platform_probe+0xb6/0x170 ... Allocated by task 1238: ... dvb_register_device+0x1a7/0xa70 [dvb_core] dvb_dmxdev_init+0x2af/0x4a0 [dvb_core] vidtv_bridge_probe+0x766/0xa40 [dvb_vidtv_bridge] ... Freed by task 1238: dvb_register_device+0x6d2/0xa70 [dvb_core] dvb_dmxdev_init+0x2af/0x4a0 [dvb_core] vidtv_bridge_probe+0x766/0xa40 [dvb_vidtv_bridge] ...
It is because the error handling in vidtv_bridge_dvb_init() is wrong.
First, vidtv_bridge_dmx(dev)_init() will clean themselves when fail, but goto fail_dmx(_dev): calls release functions again, which causes use-after-free.
Also, in fail_fe, fail_tuner_probe and fail_demod_probe, j = i will cause out-of-bound when i finished its loop (i == NUM_FE). And the loop releasing is wrong, although now NUM_FE is 1 so it won't cause problem.
Fix this by correctly releasing everything.
Patch / fix
- Linux Linux 5.10.163, 5.15.86, 6.0.16, 6.1.2, 6.2
- linux Debian 14, Debian 13, Debian 12 6.1.4-1
debian advisories DEBIAN-CVE-2022-50725
- linux Ubuntu 22.04 LTS 5.15.0-69.76
- linux-aws Ubuntu 22.04 LTS 5.15.0-1033.37
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1031.38
- linux-gke Ubuntu 22.04 LTS 5.15.0-1030.35
- linux-ibm Ubuntu 22.04 LTS 5.15.0-1027.30
- linux-kvm Ubuntu 22.04 LTS 5.15.0-1030.35
- linux-azure Ubuntu 22.04 LTS 5.15.0-1035.42
- linux-gkeop Ubuntu 22.04 LTS 5.15.0-1017.22
ubuntu advisories UBUNTU-CVE-2022-50725
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/0369af6fe33d4053899b121b32e91f870b2cf0ae commit
- git.kernel.org/stable/c/c290aa527fd832d278c6388a3ba53a9890fbd74a commit
- git.kernel.org/stable/c/06398ce69571a43a8a0dd0f1bfe35d221f726a6a commit
- git.kernel.org/stable/c/8a204a0b4a0d105229735222c515759ea2b126c1 commit
- git.kernel.org/stable/c/ba8d9405935097e296bcf7a942c3a01df0edb865 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2022-50725 updated
kernel: media: vidtv: Fix use-after-free in vidtv_bridge_dvb_init()
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.24% chance of exploitation in the next 30 days, higher than 14% of all scored CVEs (FIRST EPSS, 2026-11-08).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/0369af6fe33d4053899b121b32e91f870b2cf0ae
- git.kernel.org /stable/c/c290aa527fd832d278c6388a3ba53a9890fbd74a
- git.kernel.org /stable/c/06398ce69571a43a8a0dd0f1bfe35d221f726a6a
- git.kernel.org /stable/c/8a204a0b4a0d105229735222c515759ea2b126c1
- git.kernel.org /stable/c/ba8d9405935097e296bcf7a942c3a01df0edb865
Sources
- CVE List CVE-2022-50725
- NVD CVE-2022-50725
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.