The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2026-011309 advisory.

    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.

Tenable has extracted the preceding description block directly from the Unity Linux security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - 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. (CVE-2022-50725)

Note that Nessus relies on the presence of the package as reported by the vendor.

The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2026-013588 advisory.

    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.

Tenable has extracted the preceding description block directly from the Unity Linux security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

An update of the linux package has been released.

ID	Name	Product	Family	Published	Updated	Severity
308826	Unity Linux 20.1060e / 20.1070e Security Update: kernel (UTSA-2026-011309)	Nessus	Unity Linux Local Security Checks	4/21/2026	4/21/2026	critical
280016	Linux Distros Unpatched Vulnerability : CVE-2022-50725	Nessus	Misc.	12/26/2025	2/4/2026	high
309426	Unity Linux 20.1060a / 20.1070a Security Update: kernel (UTSA-2026-013588)	Nessus	Unity Linux Local Security Checks	4/22/2026	4/26/2026	critical
151965	Photon OS 4.0: Linux PHSA-2021-4.0-0065	Nessus	PhotonOS Local Security Checks	7/22/2021	3/23/2026	high

Detections

Analytics

Plugins Search

critical

high

critical

high