Kernel memory corruption via DVB disconnect race
Published Nov 25, 2022 · Updated Apr 29, 2025
Use-after-free in the Linux kernel DVB frontend through 6.0.9 allows local users to corrupt memory by disconnecting a DVB device. A disconnect can race DVB frontend teardown, causing the driver to access frontend state after its backing allocation has been freed. Reaching the flaw requires low-privilege local access and a disconnectable DVB device; resulting memory corruption can crash the kernel or compromise the host.
Summary
What happened
Use-after-free in the Linux kernel DVB frontend through 6.0.9 allows local users to corrupt memory by disconnecting a DVB device. A disconnect can race DVB frontend teardown, causing the driver to access frontend state after its backing allocation has been freed. Reaching the flaw requires low-privilege local access and a disconnectable DVB device; resulting memory corruption can crash the kernel or compromise the host.
The record
- CVE
- CVE-2022-45885
- Published
- Nov 25, 2022
- Updated
- Apr 29, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-362, CWE-416
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 25, 2022CVE publishedPublication date reported by the CVE source.
- Apr 29, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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