LiveActive security incident?Get immediate response
CVE Record

CVE-2025-38529: comedi: aio_iiro_16: Fix bit shift out of bounds

In the Linux kernel, the following vulnerability has been resolved: comedi: aio_iiro_16: Fix bit shift out of bounds When checking for a supported IRQ number, the following test is used: if ((1 << it->options[1]) & 0xdcfc) { However, `it->options[i]` is an unchecked `int` value from userspace, so the shift amount could be negative or out of bounds. Fix the test by requiring `it->options[1]` to be within bounds before proceeding with the original test. Valid `it->options[1]` values that select the IRQ will be in the range [1,15]. The value 0 explicitly disables the use of interrupts.

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

Security readout for executives and security teams

Plain-English summary

CVE-2025-38529 is a Linux kernel bug in the Comedi aio_iiro_16 driver. A userspace-supplied IRQ option was not checked before a bit shift, allowing invalid values. Public sources do not state a proven impact, CVSS score, or active exploitation.

Executive priority

Treat as routine-to-priority kernel maintenance, not an emergency based on current evidence. Prioritize specialized Linux systems using Comedi drivers and apply vendor kernel updates through normal change control.

Technical view

The aio_iiro_16 Comedi driver tested supported IRQ values using a shift based on it->options[1], an unchecked int from userspace. Negative or out-of-range shift values could trigger undefined behavior. The fix bounds-checks the option and treats valid IRQ selections as 1 through 15, with 0 disabling interrupts.

Likely exposure

Exposure is likely limited to Linux systems running affected kernel versions with the Comedi aio_iiro_16 driver path reachable. The source bundle lists Linux kernel branches as affected and references stable kernel fixes plus Debian LTS advisories.

Exploitation context

No KEV listing is present, and the provided sources do not report active exploitation. The described input comes from userspace, suggesting local interaction with the relevant driver configuration path, but public impact details are incomplete.

Researcher notes

The public record identifies the root cause and fix but does not provide CVSS, CWE, exploitability, or concrete impact. Avoid assuming remote reachability or active exploitation. Validation should focus on kernel version, driver presence, and downstream vendor advisories.

Mitigation direction

  • Update to a kernel containing the referenced stable fixes.
  • Review Debian LTS advisories if running Debian-based systems.
  • Prioritize systems using Comedi or relevant data-acquisition hardware.
  • If uncertain, follow your Linux distribution’s kernel security guidance.

Validation and detection

  • Inventory Linux kernel versions across affected assets.
  • Check whether Comedi and aio_iiro_16 are present or in use.
  • Compare installed kernels against vendor fixed releases and stable commits.
  • Confirm distribution security advisories have been applied.
Prepared
Confidence
medium
Sources
12

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-2025-38529 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
1ADP providers
11Source links

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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxad7a370c8be47247f68f7187cc82f4f25a347116, ad7a370c8be47247f68f7187cc82f4f25a347116, ad7a370c8be47247f68f7187cc82f4f25a347116, ad7a370c8be47247f68f7187cc82f4f25a347116, ad7a370c8be47247f68f7187cc82f4f25a347116, ad7a370c8be47247f68f7187cc82f4f25a347116, ad7a370c8be47247f68f7187cc82f4f25a347116, ad7a370c8be47247f68f7187cc82f4f25a347116unaffected
LinuxLinux4.0, 0, 5.4.297, 5.10.241, 5.15.190, 6.1.147, 6.6.100, 6.12.40, 6.15.8, 6.16affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.