Kernel deadlock via DVB event lock misuse
Published Apr 24, 2023 · Updated Mar 18, 2025
Deadlock in the Linux kernel 6.2 DVB Core driver allows local users to hang the kernel through a crafted FE_GET_EVENT ioctl sequence. In dvb_frontend_get_event, wait_event_interruptible evaluates dvb_frontend_test_event, which calls down on fepriv->sem while the task is not running. Access to the DVB frontend device and permission to issue FE_GET_EVENT are required; triggering the lock sequence can deadlock the kernel and halt the host.
Summary
What happened
Deadlock in the Linux kernel 6.2 DVB Core driver allows local users to hang the kernel through a crafted FE_GET_EVENT ioctl sequence. In dvb_frontend_get_event, wait_event_interruptible evaluates dvb_frontend_test_event, which calls down on fepriv->sem while the task is not running. Access to the DVB frontend device and permission to issue FE_GET_EVENT are required; triggering the lock sequence can deadlock the kernel and halt the host.
The record
- CVE
- CVE-2023-31084
- Published
- Apr 24, 2023
- Updated
- Mar 18, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-833, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 24, 2023CVE publishedPublication date reported by the CVE source.
- Mar 18, 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.
Public exploit references
- Syzkaller and C reproducers for DVB frontend deadlockproof of concept · demonstrated
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