CVE-2024-27043: media: edia: dvbdev: fix a use-after-free
In the Linux kernel, the following vulnerability has been resolved:
media: edia: dvbdev: fix a use-after-free
In dvb_register_device, *pdvbdev is set equal to dvbdev, which is freed
in several error-handling paths. However, *pdvbdev is not set to NULL
after dvbdev's deallocation, causing use-after-frees in many places,
for example, in the following call chain:
budget_register
|-> dvb_dmxdev_init
|-> dvb_register_device
|-> dvb_dmxdev_release
|-> dvb_unregister_device
|-> dvb_remove_device
|-> dvb_device_put
|-> kref_put
When calling dvb_unregister_device, dmxdev->dvbdev (i.e. *pdvbdev in
dvb_register_device) could point to memory that had been freed in
dvb_register_device. Thereafter, this pointer is transferred to
kref_put and triggering a use-after-free.
Security readout for executives and security teams
Plain-English summary
A Linux kernel flaw can leave a freed Digital Video Broadcasting device object accessible during error cleanup. A local, low-privileged user could potentially trigger memory corruption, threatening confidentiality, integrity, and availability. Exposure depends on the installed kernel, relevant DVB functionality, and vendor backports.
Executive priority
Treat this as a high-priority kernel maintenance issue, especially on shared or otherwise locally accessible Linux hosts using DVB functionality. It is less urgent than an unauthenticated remote flaw because local access is required and active exploitation is not evidenced. Use vendor package status, not upstream version numbers alone, to schedule remediation.
Technical view
dvb_register_device can assign *pdvbdev before freeing dvbdev on an error path without clearing the caller’s pointer. Later cleanup can pass this stale pointer through dvb_unregister_device, dvb_remove_device, dvb_device_put, and kref_put, causing a use-after-free. The supplied CVSS 3.1 score is 7.8 with local, low-privilege attack requirements.
Likely exposure
Systems running affected Linux kernel branches with relevant media/DVB functionality are the likely exposure population. The bundle lists affected releases across branches from 2.6.21 through 6.9, but does not provide enough normalized range data to determine every vulnerable build. Distribution backports may change status.
Exploitation context
The supplied CVSS vector describes local exploitation requiring low privileges, low complexity, and no user interaction. Successful exploitation could affect confidentiality, integrity, and availability. The bundle marks this CVE as absent from KEV and provides no evidence of active exploitation or a public working exploit.
Researcher notes
The defect is a stale output pointer caused by incomplete error-path cleanup, culminating in kref_put operating on freed memory. Multiple stable-kernel commit references indicate branch-specific fixes. The bundle does not establish practical exploit reliability, affected configurations beyond DVB involvement, or precise distribution package boundaries.
Mitigation direction
Apply a vendor-supported kernel update containing the appropriate stable fix or backport.
Prioritize multi-user systems where untrusted local users can access relevant DVB functionality.
If updates are delayed, consult vendor guidance about safely disabling unused DVB functionality.
Reboot into the updated kernel and remove superseded vulnerable kernels where operationally appropriate.
Validation and detection
Inventory running kernel versions and installed kernel packages across Linux systems.
Determine whether DVB media drivers or associated hardware are present and operationally required.
Compare vendor advisories and package changelogs for CVE-2024-27043 backport confirmation.
Confirm the running kernel after remediation, including required reboots.
Regression-test DVB-dependent services after updating or disabling functionality.
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-27043 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.