CVE-2022-50725media: vidtv: Fix use-after-free in vidtv_bridge_dvb_init()
- —Not scoredno CVSS score yet
- 0.24%Exploitation in 30 daysEPSS · top 85% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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.
Timeline
ID reserved
By Linux
Published
- 5 months later
· 5 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.
- EPSS (exploitation in 30 days)
- 0.24% · top 85% of all CVEs (17 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected f90cf6079bf67988f8b1ad1ade70fc89d0080905 – < 0369af6fe33d4053899b121b32e91f870b2cf0ae
- affected f90cf6079bf67988f8b1ad1ade70fc89d0080905 – < c290aa527fd832d278c6388a3ba53a9890fbd74a
- affected f90cf6079bf67988f8b1ad1ade70fc89d0080905 – < 06398ce69571a43a8a0dd0f1bfe35d221f726a6a
- affected f90cf6079bf67988f8b1ad1ade70fc89d0080905 – < 8a204a0b4a0d105229735222c515759ea2b126c1
- affected f90cf6079bf67988f8b1ad1ade70fc89d0080905 – < ba8d9405935097e296bcf7a942c3a01df0edb865
- affected 5.10
- unaffected < 5.10
- unaffected 5.10.163 – ≤ 5.10.*
- unaffected 5.15.86 – ≤ 5.15.*
- unaffected 6.0.16 – ≤ 6.0.*
- unaffected 6.1.2 – ≤ 6.1.*
- unaffected 6.2 – ≤ *
References
References5
- https://git.kernel.org/stable/c/0369af6fe33d4053899b121b32e91f870b2cf0ae (opens in a new tab)
- https://git.kernel.org/stable/c/c290aa527fd832d278c6388a3ba53a9890fbd74a (opens in a new tab)
- https://git.kernel.org/stable/c/06398ce69571a43a8a0dd0f1bfe35d221f726a6a (opens in a new tab)
- https://git.kernel.org/stable/c/8a204a0b4a0d105229735222c515759ea2b126c1 (opens in a new tab)
- https://git.kernel.org/stable/c/ba8d9405935097e296bcf7a942c3a01df0edb865 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2022-55764 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2022-50725)Record last updated .