Skip to main content
VulnerabilityPublished Updated

CVE-2025-38671: Linux kernel · i2c: qup: jump out of the loop in case of timeout

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in d05ec13aa3eb868a60dc961b489053a643863ddc : update Linux kernel when convenient.

Data as of 5 Nov 2026, 21:34 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-05.

Patch
Available – fixed in d05ec13aa3eb868a60dc961b489053a643863ddc, cbec4406998185e0311ae97dfacc649f9cd79b0b, c523bfba46c4b4d7676fb050909533a766698ecd +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ fbfab1ab065879370541caf0e514987368eb41b2, < d05ec13aa3eb868a60dc961b489053a643863ddc
Fixed in
  • d05ec13aa3eb868a60dc961b489053a643863ddc
LinuxLinuxAffected
  • ≥ fbfab1ab065879370541caf0e514987368eb41b2, < cbec4406998185e0311ae97dfacc649f9cd79b0b
Fixed in
  • cbec4406998185e0311ae97dfacc649f9cd79b0b
LinuxLinuxAffected
  • ≥ fbfab1ab065879370541caf0e514987368eb41b2, < c523bfba46c4b4d7676fb050909533a766698ecd
Fixed in
  • c523bfba46c4b4d7676fb050909533a766698ecd
LinuxLinuxAffected
  • ≥ fbfab1ab065879370541caf0e514987368eb41b2, < acfa2948be630ad857535cb36153697f3cbf9ca9
Fixed in
  • acfa2948be630ad857535cb36153697f3cbf9ca9
LinuxLinuxAffected
  • ≥ fbfab1ab065879370541caf0e514987368eb41b2, < a7982a14b3012527a9583d12525cd0dc9f8d8934
Fixed in
  • a7982a14b3012527a9583d12525cd0dc9f8d8934
LinuxLinuxAffected
  • ≥ fbfab1ab065879370541caf0e514987368eb41b2, < 89459f168b78e5c801dc8b7ad037b62898bc4f57
Fixed in
  • 89459f168b78e5c801dc8b7ad037b62898bc4f57

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.

References

Community reviews

Loading reviews…