LiveActive security incident?Get immediate response
CVE Record

CVE-2024-38637: greybus: lights: check return of get_channel_from_mode

In the Linux kernel, the following vulnerability has been resolved: greybus: lights: check return of get_channel_from_mode If channel for the given node is not found we return null from get_channel_from_mode. Make sure we validate the return pointer before using it in two of the missing places. This was originally reported in [0]: Found by Linux Verification Center (linuxtesting.org) with SVACE. [0] https://lore.kernel.org/all/20240301190425.120605-1-m.lobanov@rosalinux.ru

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

Security readout for executives and security teams

Plain-English summary

CVE-2024-38637 is a Linux kernel bug in the Greybus lights driver. The code could use a missing channel pointer without checking it first. The provided sources do not include CVSS, CWE, or active exploitation evidence. Treat this as a targeted kernel patching issue for systems that include or use Greybus lights support.

Executive priority

Handle through normal kernel vulnerability management unless affected Greybus-capable systems are business-critical. There is insufficient evidence for emergency response: no CVSS, no KEV listing, and no cited exploitation. Prioritize accurate asset scoping and timely kernel updates.

Technical view

The issue is a missing NULL check after get_channel_from_mode can return no channel for a node. Linux resolved it by validating the pointer before use in two call sites. The CVE lists affected Linux versions and multiple stable kernel commits, but does not provide a severity score, exploitability assessment, or detailed impact statement.

Likely exposure

Exposure is most likely limited to Linux systems running affected kernel versions with the Greybus lights driver present or reachable. Standard servers may have no practical exposure if the relevant driver is absent, disabled, or unused. Distribution backports may change version-based conclusions.

Exploitation context

The bundle provides no evidence of active exploitation and KEV is false. The report appears to come from static analysis by Linux Verification Center using SVACE. No public exploit status, attacker prerequisites, or confirmed impact path is provided in the supplied sources.

Researcher notes

The source evidence supports a NULL-pointer validation flaw in drivers/staging/greybus/light.c behavior, fixed across stable branches. Impact is not explicitly characterized in the bundle, so do not overstate confidentiality, integrity, or availability consequences without additional vendor analysis.

Mitigation direction

  • Apply vendor or distribution kernel updates that include the referenced stable fixes.
  • Check Debian LTS guidance if running affected Debian LTS kernels.
  • Prioritize systems where Greybus lights support is enabled or hardware-relevant.
  • If no vendor advisory exists, monitor kernel and distribution guidance.
  • Avoid assuming mainline version numbers prove exposure without checking backports.

Validation and detection

  • Inventory Linux kernel versions across affected assets.
  • Check whether Greybus lights driver support is built, loaded, or packaged.
  • Map installed kernels to vendor advisories and stable fix commits.
  • Confirm patched kernels are deployed and booted, not only installed.
  • Review distribution changelogs for CVE-2024-38637 backports.
Prepared
Confidence
medium
Sources
11

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-38637 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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux2870b52bae4c81823ffcb3ed2b0626fb39d64f48, 2870b52bae4c81823ffcb3ed2b0626fb39d64f48, 2870b52bae4c81823ffcb3ed2b0626fb39d64f48, 2870b52bae4c81823ffcb3ed2b0626fb39d64f48, 2870b52bae4c81823ffcb3ed2b0626fb39d64f48, 2870b52bae4c81823ffcb3ed2b0626fb39d64f48, 2870b52bae4c81823ffcb3ed2b0626fb39d64f48, 2870b52bae4c81823ffcb3ed2b0626fb39d64f48unaffected
LinuxLinux4.9, 0, 4.19.316, 5.4.278, 5.10.219, 5.15.161, 6.1.93, 6.6.33, 6.9.4, 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.