LiveActive security incident?Get immediate response
CVE Record

CVE-2024-58003: media: i2c: ds90ub9x3: Fix extra fwnode_handle_put()

In the Linux kernel, the following vulnerability has been resolved: media: i2c: ds90ub9x3: Fix extra fwnode_handle_put() The ub913 and ub953 drivers call fwnode_handle_put(priv->sd.fwnode) as part of their remove process, and if the driver is removed multiple times, eventually leads to put "overflow", possibly causing memory corruption or crash. The fwnode_handle_put() is a leftover from commit 905f88ccebb1 ("media: i2c: ds90ub9x3: Fix sub-device matching"), which changed the code related to the sd.fwnode, but missed removing these fwnode_handle_put() calls.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can corrupt memory or crash a system when specific media I2C drivers are removed repeatedly. The evidence points to a narrow driver lifecycle bug, not a broadly reachable network flaw. Business urgency depends on whether affected kernels and these drivers are present in production or embedded video platforms.

Executive priority

Treat as targeted remediation for Linux fleets with affected media hardware or embedded deployments. It is not currently evidenced as internet-scale or actively exploited, but kernel memory corruption and crash risk justify timely patch planning where exposure exists.

Technical view

The ds90ub9x3 media I2C ub913 and ub953 drivers call fwnode_handle_put() during removal even though prior code changes made that release incorrect. Repeated driver removal can cause reference-count put overflow, with possible memory corruption or crash. Stable kernel commits are referenced as fixes.

Likely exposure

Most exposure is likely in Linux systems using affected kernel versions with the ds90ub9x3 ub913 or ub953 media I2C drivers. General-purpose servers without these drivers or hardware paths are less likely exposed. Version and configuration evidence is required.

Exploitation context

The source bundle does not report active exploitation, public exploit use, or KEV listing. Triggering requires repeated removal of the affected driver path, based on the CVE description. Remote exploitation is not supported by the provided evidence.

Researcher notes

Key unknowns are privilege requirements, reachability in real deployments, and whether memory corruption is practically exploitable beyond denial of service. The provided sources identify the faulty extra fwnode_handle_put() and stable fixes, but do not provide CVSS, CWE, or exploitation evidence.

Mitigation direction

  • Update affected Linux kernels using vendor or stable kernel guidance.
  • Prioritize systems using ds90ub9x3 ub913 or ub953 media I2C drivers.
  • Avoid repeated unload/remove workflows for affected drivers until patched.
  • Track downstream distribution advisories for backported fixes.
  • Do not deploy directly; follow normal tested kernel rollout procedures.

Validation and detection

  • Inventory kernel versions against vendor-fixed releases and referenced stable commits.
  • Check whether ds90ub9x3, ub913, or ub953 drivers are built or loaded.
  • Identify embedded or video platforms using these media I2C paths.
  • Review logs for crashes around driver removal or device teardown.
  • Confirm remediation through vendor package metadata or kernel commit backports.
Prepared
Confidence
medium
Sources
6

Public sources used

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-58003 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
0ADP providers
5Source links

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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux905f88ccebb14e42bcd19455b0d9c0d4808f1897, 905f88ccebb14e42bcd19455b0d9c0d4808f1897, 905f88ccebb14e42bcd19455b0d9c0d4808f1897, 905f88ccebb14e42bcd19455b0d9c0d4808f1897unaffected
LinuxLinux6.6, 0, 6.6.78, 6.12.14, 6.13.3, 6.14affected
Weakness

CWE details

No CWE listed

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