CVE-2024-38611: media: i2c: et8ek8: Don't strip remove function when driver is builtin
In the Linux kernel, the following vulnerability has been resolved:
media: i2c: et8ek8: Don't strip remove function when driver is builtin
Using __exit for the remove function results in the remove callback
being discarded with CONFIG_VIDEO_ET8EK8=y. When such a device gets
unbound (e.g. using sysfs or hotplug), the driver is just removed
without the cleanup being performed. This results in resource leaks. Fix
it by compiling in the remove callback unconditionally.
This also fixes a W=1 modpost warning:
WARNING: modpost: drivers/media/i2c/et8ek8/et8ek8: section mismatch in reference: et8ek8_i2c_driver+0x10 (section: .data) -> et8ek8_remove (section: .exit.text)
Security readout for executives and security teams
Plain-English summary
CVE-2024-38611 is a Linux kernel issue in the ET8EK8 camera sensor driver. If the driver is built into the kernel, its cleanup routine can be omitted, causing resource leaks when the device is unbound or hotplugged. Evidence points to availability or stability impact, not data theft or remote compromise.
Executive priority
Treat as routine kernel hygiene unless your environment ships Linux camera devices using ET8EK8. Patch through normal kernel maintenance. Escalate only for embedded fleets where resource leaks could affect device uptime.
Technical view
The et8ek8 I2C media driver marked its remove callback with __exit. With CONFIG_VIDEO_ET8EK8=y, that callback is discarded, so unbind or hotplug removal skips cleanup and leaks resources. Kernel stable commits compile the remove callback unconditionally. Severity and CVSS are not provided in the source bundle.
Likely exposure
Exposure appears limited to Linux systems with the ET8EK8 camera driver built into the kernel and affected kernel versions. Servers and cloud workloads are unlikely to use this driver, but embedded, mobile, or camera-enabled Linux builds should check configuration.
Exploitation context
No KEV listing or cited source indicates active exploitation. Triggering requires the affected driver and a device unbind or hotplug path. The documented impact is resource leakage, which may affect reliability over time.
Researcher notes
The record describes a cleanup omission caused by section mismatch, not a memory corruption primitive. The affected condition is specific: builtin ET8EK8 driver and device unbind or hotplug. Public sources do not provide CVSS, CWE, exploit reports, or broader impact claims.
Mitigation direction
Update to a vendor kernel containing the referenced stable fixes.
Apply Debian LTS kernel updates where applicable.
Check vendor advisories for your distribution or device build.
Avoid building CONFIG_VIDEO_ET8EK8 into kernels that do not need it.
Validation and detection
Identify systems running Linux kernels with ET8EK8 support.
Confirm whether CONFIG_VIDEO_ET8EK8 is built in.
Check kernel version or vendor package against fixed releases.
Verify the relevant stable commit is present in custom kernels.
Prioritize embedded or camera-enabled Linux devices for review.
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-38611 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.