LiveActive security incident?Get immediate response
CVE Record

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)

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysislow

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.
Prepared
Confidence
high
Sources
11

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.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

0CVSS vectors
3Timeline events
2ADP providers
10Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxc5254e72b8edc2ca0a98703e92e8c34959343d2c, c5254e72b8edc2ca0a98703e92e8c34959343d2c, c5254e72b8edc2ca0a98703e92e8c34959343d2c, c5254e72b8edc2ca0a98703e92e8c34959343d2c, c5254e72b8edc2ca0a98703e92e8c34959343d2c, c5254e72b8edc2ca0a98703e92e8c34959343d2c, c5254e72b8edc2ca0a98703e92e8c34959343d2cunaffected
LinuxLinux4.11, 0, 5.10.236, 5.15.180, 6.1.133, 6.6.33, 6.8.12, 6.9.3, 6.10affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.