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-2025-38237media: platform: exynos4-is: Add hardware sync wait to fimc_is_hw_change_mode()

Description

In the Linux kernel, the following vulnerability has been resolved: media: platform: exynos4-is: Add hardware sync wait to fimc_is_hw_change_mode() In fimc_is_hw_change_mode(), the function changes camera modes without waiting for hardware completion, risking corrupted data or system hangs if subsequent operations proceed before the hardware is ready. Add fimc_is_hw_wait_intmsr0_intmsd0() after mode configuration, ensuring hardware state synchronization and stable interrupt handling.

Timeline

  1. ID reserved

    By Linux

  2. · 3 months later

    Published

  3. · 14 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-2025-38237, 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.18% · top 92% of all CVEs (16 Nov 2026)
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 9a761e436843f228eaa2decda6d2c6dbd5ef1480 – < b0d92b94278561f43057003a73a17ce13b7c1a1a
    • affected 9a761e436843f228eaa2decda6d2c6dbd5ef1480 – < e4077a10a25560ec0bd0b42322e4ea027d6f76e2
    • affected 9a761e436843f228eaa2decda6d2c6dbd5ef1480 – < bb97dfab7615fea97322b8a6131546e80f878a69
    • affected 9a761e436843f228eaa2decda6d2c6dbd5ef1480 – < 9b03c3ce32a685f9cb82d33c63fc18bfcee0ba1b
    • affected 9a761e436843f228eaa2decda6d2c6dbd5ef1480 – < 71209954f1e8ff0f0ba944c8d3b64bbed83d400c
    • affected 9a761e436843f228eaa2decda6d2c6dbd5ef1480 – < 2fbe83fe23f541798bcdd7d6b56a08d4ac205bad
    • affected 9a761e436843f228eaa2decda6d2c6dbd5ef1480 – < 14acbb5af101b7bb58c0952949bba4c5fdf0ee7e
    • affected 9a761e436843f228eaa2decda6d2c6dbd5ef1480 – < bd9f6ce7d512fa21249415c16af801a4ed5d97b6
  • Linux · Linux

    • affected 3.10
    • unaffected < 3.10
    • unaffected 5.4.295 – ≤ 5.4.*
    • unaffected 5.10.239 – ≤ 5.10.*
    • unaffected 5.15.186 – ≤ 5.15.*
    • unaffected 6.1.187 – ≤ 6.1.*
    • unaffected 6.6.156 – ≤ 6.6.*
    • unaffected 6.12.108 – ≤ 6.12.*
    • unaffected 6.15.4 – ≤ 6.15.*
    • unaffected 6.16 – ≤ *

References

References9

Sources

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

Badge for a README or a ticket

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

Record last updated .