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-38637greybus: lights: check return of get_channel_from_mode

Description

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/[email protected]

Timeline

  1. ID reserved

    By Linux

  2. · 3 days later

    Published

  3. · 23 months 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-38637, by who scored it
Scored byCVSSScoreVector
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 (16 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: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 2870b52bae4c81823ffcb3ed2b0626fb39d64f48 – < 8f4a76d477f0cc3c54d512f07f6f88c8e1c1e07b
    • affected 2870b52bae4c81823ffcb3ed2b0626fb39d64f48 – < e2c64246e5dc8c0d35ec41770b85e2b4cafdff21
    • affected 2870b52bae4c81823ffcb3ed2b0626fb39d64f48 – < eac10cf3a97ffd4b4deb0a29f57c118225a42850
    • affected 2870b52bae4c81823ffcb3ed2b0626fb39d64f48 – < 330f6bcdcef03f70f81db5f2ed6747af656a09f2
    • affected 2870b52bae4c81823ffcb3ed2b0626fb39d64f48 – < 9b41a9b9c8be8c552f10633453fdb509e83b66f8
    • affected 2870b52bae4c81823ffcb3ed2b0626fb39d64f48 – < 518e2c46b5dbce40b1aa0100001d03c3ceaa7d38
    • affected 2870b52bae4c81823ffcb3ed2b0626fb39d64f48 – < 895cdd9aa9546523df839f9cc1488a0ecc1e0731
    • affected 2870b52bae4c81823ffcb3ed2b0626fb39d64f48 – < a1ba19a1ae7cd1e324685ded4ab563e78fe68648
  • Linux · Linux

    • affected 4.9
    • unaffected < 4.9
    • unaffected 4.19.316 – ≤ 4.19.*
    • unaffected 5.4.278 – ≤ 5.4.*
    • unaffected 5.10.219 – ≤ 5.10.*
    • unaffected 5.15.161 – ≤ 5.15.*
    • unaffected 6.1.93 – ≤ 6.1.*
    • unaffected 6.6.33 – ≤ 6.6.*
    • unaffected 6.9.4 – ≤ 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-38637 badge
[![CVE-2024-38637](https://cveledger.app/badge/CVE-2024-38637.svg)](https://cveledger.app/cve/CVE-2024-38637)

Record last updated .