Kernel memory corruption via stale DVB entity pointer
Published Oct 4, 2025 · Updated Oct 4, 2025
Double free in the Linux kernel DVB core allows local users to corrupt kernel memory during media-device registration failures. When dvbdev->pad allocation fails, dvb_create_media_entity() frees dvb->entity without clearing the pointer, and caller cleanup frees it again. Reachability requires low-privileged local access and the DVB media-registration error path; successful exploitation can crash the kernel or compromise kernel-managed data.
Summary
What happened
Double free in the Linux kernel DVB core allows local users to corrupt kernel memory during media-device registration failures. When dvbdev->pad allocation fails, dvb_create_media_entity() frees dvb->entity without clearing the pointer, and caller cleanup frees it again. Reachability requires low-privileged local access and the DVB media-registration error path; successful exploitation can crash the kernel or compromise kernel-managed data.
The record
- CVE
- CVE-2022-50499
- Published
- Oct 4, 2025
- Updated
- Oct 4, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-415, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 4, 2025CVE publishedPublication date reported by the CVE source.
- Oct 4, 2025Record 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=1399a136127bfe1b9bb7c951d9851da62a519121 <e9a78485b658361fab6a5547377be6c1af6f1b3d
- Affected versionversion=202be5d6e46f682b9d1d79cd4dc6ab726e62ef1c
- Affected versionversion=4df2427a5148093987437054bb82da4d014dcd59 <70bc51303871159796b55ba1a8f16637b46c2511
- Affected versionversion=5.4
- Affected versionversion=8c17f6f5d0d6aab72a2af25c9911ac66e984be06
- Affected versionversion=9db28659aa893c68f162b11fd63bb7f6a713e52f <0588b12c418c3e4f927ced11f27b02ef4a5bfb07
- Affected versionversion=fcd5ce4b3936242e6679875a4d3c3acfc8743e15 <123eddf92a114e03919942641d2c2b1f4ca56ea6
- Affected versionversion=fcd5ce4b3936242e6679875a4d3c3acfc8743e15 <6b0d0477fce747d4137aa65856318b55fba72198
- Affected versionversion=fcd5ce4b3936242e6679875a4d3c3acfc8743e15 <772892b29ac50c2c5e918fc80104aa6ede81d837
- Affected versionversion=fcd5ce4b3936242e6679875a4d3c3acfc8743e15 <7dd5a68cdbbbe7fc67ba701cb52ba10d8ba149f8
- Affected versionversion=fcd5ce4b3936242e6679875a4d3c3acfc8743e15 <acf984a3718c2458eb9e08b6714490a04f213c58
- Affected versionversion=fcd5ce4b3936242e6679875a4d3c3acfc8743e15 <b21f62b49ee9c3e0216d685d9cfd6003e5727271
What conditions does exploitation require?
What is affected?
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.
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