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-38671i2c: qup: jump out of the loop in case of timeout

Description

In the Linux kernel, the following vulnerability has been resolved: i2c: qup: jump out of the loop in case of timeout Original logic only sets the return value but doesn't jump out of the loop if the bus is kept active by a client. This is not expected. A malicious or buggy i2c client can hang the kernel in this case and should be avoided. This is observed during a long time test with a PCA953x GPIO extender. Fix it by changing the logic to not only sets the return value, but also jumps out of the loop and return to the caller with -ETIMEDOUT.

Timeline

  1. ID reserved

    By Linux

  2. · 4 months later

    Published

  3. · 15 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-38671, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.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 (15 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 fbfab1ab065879370541caf0e514987368eb41b2 – < cbec4406998185e0311ae97dfacc649f9cd79b0b
    • affected fbfab1ab065879370541caf0e514987368eb41b2 – < acfa2948be630ad857535cb36153697f3cbf9ca9
    • affected fbfab1ab065879370541caf0e514987368eb41b2 – < d05ec13aa3eb868a60dc961b489053a643863ddc
    • affected fbfab1ab065879370541caf0e514987368eb41b2 – < c523bfba46c4b4d7676fb050909533a766698ecd
    • affected fbfab1ab065879370541caf0e514987368eb41b2 – < 0d33913fce67a93c1eb83396c3c9d6b411dcab33
    • affected fbfab1ab065879370541caf0e514987368eb41b2 – < 42c4471b30fa203249f476dd42321cd7efb7f6a8
    • affected fbfab1ab065879370541caf0e514987368eb41b2 – < 89459f168b78e5c801dc8b7ad037b62898bc4f57
    • affected fbfab1ab065879370541caf0e514987368eb41b2 – < a7982a14b3012527a9583d12525cd0dc9f8d8934
  • Linux · Linux

    • affected 4.17
    • unaffected < 4.17
    • unaffected 5.4.297 – ≤ 5.4.*
    • unaffected 5.10.241 – ≤ 5.10.*
    • unaffected 5.15.190 – ≤ 5.15.*
    • unaffected 6.1.148 – ≤ 6.1.*
    • unaffected 6.6.101 – ≤ 6.6.*
    • unaffected 6.12.41 – ≤ 6.12.*
    • unaffected 6.15.9 – ≤ 6.15.*
    • unaffected 6.16 – ≤ *

References

References10

Sources

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

Badge for a README or a ticket

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

Record last updated .