LiveActive security incident?Get immediate response
CVE Record

CVE-2024-57834: media: vidtv: Fix a null-ptr-deref in vidtv_mux_stop_thread

In the Linux kernel, the following vulnerability has been resolved: media: vidtv: Fix a null-ptr-deref in vidtv_mux_stop_thread syzbot report a null-ptr-deref in vidtv_mux_stop_thread. [1] If dvb->mux is not initialized successfully by vidtv_mux_init() in the vidtv_start_streaming(), it will trigger null pointer dereference about mux in vidtv_mux_stop_thread(). Adjust the timing of streaming initialization and check it before stopping it. [1] KASAN: null-ptr-deref in range [0x0000000000000128-0x000000000000012f] CPU: 0 UID: 0 PID: 5842 Comm: syz-executor248 Not tainted 6.13.0-rc4-syzkaller-00012-g9b2ffa6148b1 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 RIP: 0010:vidtv_mux_stop_thread+0x26/0x80 drivers/media/test-drivers/vidtv/vidtv_mux.c:471 Code: 90 90 90 90 66 0f 1f 00 55 53 48 89 fb e8 82 2e c8 f9 48 8d bb 28 01 00 00 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 <0f> b6 04 02 84 c0 74 02 7e 3b 0f b6 ab 28 01 00 00 31 ff 89 ee e8 RSP: 0018:ffffc90003f2faa8 EFLAGS: 00010202 RAX: dffffc0000000000 RBX: 0000000000000000 RCX: ffffffff87cfb125 RDX: 0000000000000025 RSI: ffffffff87d120ce RDI: 0000000000000128 RBP: ffff888029b8d220 R08: 0000000000000005 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000003 R12: ffff888029b8d188 R13: ffffffff8f590aa0 R14: ffffc9000581c5c8 R15: ffff888029a17710 FS: 00007f7eef5156c0(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f7eef5e635c CR3: 0000000076ca6000 CR4: 00000000003526f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> vidtv_stop_streaming drivers/media/test-drivers/vidtv/vidtv_bridge.c:209 [inline] vidtv_stop_feed+0x151/0x250 drivers/media/test-drivers/vidtv/vidtv_bridge.c:252 dmx_section_feed_stop_filtering+0x90/0x160 drivers/media/dvb-core/dvb_demux.c:1000 dvb_dmxdev_feed_stop.isra.0+0x1ee/0x270 drivers/media/dvb-core/dmxdev.c:486 dvb_dmxdev_filter_stop+0x22a/0x3a0 drivers/media/dvb-core/dmxdev.c:559 dvb_dmxdev_filter_free drivers/media/dvb-core/dmxdev.c:840 [inline] dvb_demux_release+0x92/0x550 drivers/media/dvb-core/dmxdev.c:1246 __fput+0x3f8/0xb60 fs/file_table.c:450 task_work_run+0x14e/0x250 kernel/task_work.c:239 get_signal+0x1d3/0x2610 kernel/signal.c:2790 arch_do_signal_or_restart+0x90/0x7e0 arch/x86/kernel/signal.c:337 exit_to_user_mode_loop kernel/entry/common.c:111 [inline] exit_to_user_mode_prepare include/linux/entry-common.h:329 [inline] __syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline] syscall_exit_to_user_mode+0x150/0x2a0 kernel/entry/common.c:218 do_syscall_64+0xda/0x250 arch/x86/entry/common.c:89 entry_SYSCALL_64_after_hwframe+0x77/0x7f

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2024-57834 is a Linux kernel bug in the vidtv media test driver. If streaming setup fails, cleanup can touch an uninitialized mux pointer and trigger a kernel null-pointer dereference. The practical concern is availability, not confirmed data theft or remote compromise.

Executive priority

Treat as a normal kernel maintenance priority unless vidtv is enabled on systems with untrusted local access. There is no cited active exploitation, but kernel null dereferences can still cause service disruption.

Technical view

The flaw is in drivers/media/test-drivers/vidtv. A failed vidtv_mux_init() path in vidtv_start_streaming() can leave dvb->mux unset, then vidtv_mux_stop_thread() dereferences it during stop/cleanup. Kernel stable commits adjust initialization timing and add a stop-time check.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions where the vidtv media test driver is present and reachable. The source lists Linux kernel versions around 5.10 through 6.14 and Debian LTS advisories, but it does not identify specific deployed distributions beyond those references.

Exploitation context

The report came from syzbot with KASAN evidence on a syzkaller kernel. The bundle does not show CISA KEV listing, public exploitation, remote reachability, privilege impact, or weaponized exploit details.

Researcher notes

Evidence supports a null-pointer dereference in the vidtv cleanup path after failed mux initialization. Impact beyond denial of service is not established in the provided sources. Fixed commits exist across stable branches, and Debian LTS advisories reference related kernel updates.

Mitigation direction

  • Update to a vendor kernel containing the referenced stable vidtv fixes.
  • Apply relevant Debian LTS kernel updates where those advisories apply.
  • Reboot into the patched kernel after updating.
  • Follow vendor guidance for reducing unused vidtv/media test-driver exposure if patching is delayed.

Validation and detection

  • Inventory Linux kernel versions and compare them with vendor fixed releases.
  • Check whether the vidtv media test driver is built, loaded, or packaged.
  • Confirm the running kernel includes one of the referenced stable commits or vendor backports.
  • Review kernel logs for crashes referencing vidtv_mux_stop_thread or vidtv_stop_streaming.
Prepared
Confidence
medium
Sources
11

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-57834 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
1ADP providers
10Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxf90cf6079bf67988f8b1ad1ade70fc89d0080905, f90cf6079bf67988f8b1ad1ade70fc89d0080905, f90cf6079bf67988f8b1ad1ade70fc89d0080905, f90cf6079bf67988f8b1ad1ade70fc89d0080905, f90cf6079bf67988f8b1ad1ade70fc89d0080905, f90cf6079bf67988f8b1ad1ade70fc89d0080905, f90cf6079bf67988f8b1ad1ade70fc89d0080905unaffected
LinuxLinux5.10, 0, 5.10.235, 5.15.179, 6.1.129, 6.6.79, 6.12.16, 6.13.4, 6.14affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.