Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-38611media: i2c: et8ek8: Don't strip remove function when driver is builtin

Description

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)

Timeline

  1. ID reserved

    By Linux

  2. · 1 day later

    Published

  3. · 2 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-38611, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.3CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.23% · top 86% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.3.

Affected products

  • Linux · Linux

    • affected c5254e72b8edc2ca0a98703e92e8c34959343d2c – < 963523600d9f1e36bc35ba774c2493d6baa4dd8f
    • affected c5254e72b8edc2ca0a98703e92e8c34959343d2c – < ece3fc1c10197052044048bea4f13cfdcf25b416
    • affected c5254e72b8edc2ca0a98703e92e8c34959343d2c – < 04d1086a62ac492ebb6bb0c94c1c8cb55f5d1f36
    • affected c5254e72b8edc2ca0a98703e92e8c34959343d2c – < c1a3803e5bb91c13e9ad582003e4288f67f06cd9
    • affected c5254e72b8edc2ca0a98703e92e8c34959343d2c – < 43fff07e4b1956d0e5cf23717507e438278ea3d9
    • affected c5254e72b8edc2ca0a98703e92e8c34959343d2c – < 904db2ba44ae60641b6378c5013254d09acf5e80
    • affected c5254e72b8edc2ca0a98703e92e8c34959343d2c – < 545b215736c5c4b354e182d99c578a472ac9bfce
  • Linux · Linux

    • affected 4.11
    • unaffected < 4.11
    • unaffected 5.10.236 – ≤ 5.10.*
    • unaffected 5.15.180 – ≤ 5.15.*
    • unaffected 6.1.133 – ≤ 6.1.*
    • unaffected 6.6.33 – ≤ 6.6.*
    • unaffected 6.8.12 – ≤ 6.8.*
    • unaffected 6.9.3 – ≤ 6.9.*
    • unaffected 6.10 – ≤ *

References

References9

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-38611 badge
[![CVE-2024-38611](https://cveledger.app/badge/CVE-2024-38611.svg)](https://cveledger.app/cve/CVE-2024-38611)

Record last updated .