Kernel crash via uninitialized vidtv mux dereference
Published Feb 27, 2025 · Updated May 11, 2026
NULL pointer dereference in affected Linux kernel releases from 5.10 allows local users to crash the kernel through the vidtv test driver. The vidtv_start_streaming path can leave dvb->mux uninitialized when vidtv_mux_init fails, but vidtv_mux_stop_thread dereferences that null mux pointer during feed teardown. Reaching the flaw requires a local user to exercise the vidtv test driver after mux initialization fails, and exploitation interrupts the host by crashing its kernel.
Summary
What happened
NULL pointer dereference in affected Linux kernel releases from 5.10 allows local users to crash the kernel through the vidtv test driver. The vidtv_start_streaming path can leave dvb->mux uninitialized when vidtv_mux_init fails, but vidtv_mux_stop_thread dereferences that null mux pointer during feed teardown. Reaching the flaw requires a local user to exercise the vidtv test driver after mux initialization fails, and exploitation interrupts the host by crashing its kernel.
The record
- CVE
- CVE-2024-57834
- Published
- Feb 27, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 27, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.10
- Affected versionversion=f90cf6079bf67988f8b1ad1ade70fc89d0080905 <1221989555db711578a327a9367f1be46500cb48
- Affected versionversion=f90cf6079bf67988f8b1ad1ade70fc89d0080905 <2c5601b99d79d196fe4a37159e3dfb38e778ea18
- Affected versionversion=f90cf6079bf67988f8b1ad1ade70fc89d0080905 <52d3512f9a7a52ef92864679b1e8e8aa16202c6a
- Affected versionversion=f90cf6079bf67988f8b1ad1ade70fc89d0080905 <59a707ad952eb2ea8d59457d662b6f4138f17b08
- Affected versionversion=f90cf6079bf67988f8b1ad1ade70fc89d0080905 <86307e443c5844f38e1b98e2c51a4195c55576cd
- Affected versionversion=f90cf6079bf67988f8b1ad1ade70fc89d0080905 <904a8323cc8afa7eb9ce3e67303a2b3f2f787306
- Affected versionversion=f90cf6079bf67988f8b1ad1ade70fc89d0080905 <95432a37778c9c5dd105b7b9f19e9695c9e166cf
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo