CVE-2025-38530: comedi: pcl812: Fix bit shift out of bounds
In the Linux kernel, the following vulnerability has been resolved:
comedi: pcl812: Fix bit shift out of bounds
When checking for a supported IRQ number, the following test is used:
if ((1 << it->options[1]) & board->irq_bits) {
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.
Security readout for executives and security teams
Plain-English summary
CVE-2025-38530 is a Linux kernel bug in the comedi pcl812 driver. A value supplied from userspace was not bounds-checked before a bit shift. The public record does not state a business impact, CVSS score, or active exploitation. Treat it as a kernel maintenance risk, especially where this driver is present or used.
Executive priority
Schedule remediation through the normal kernel patch process unless local exposure to this driver is confirmed. Escalate priority for systems using comedi pcl812 in operational environments, because kernel bugs can have outsized reliability or security consequences despite incomplete scoring.
Technical view
The vulnerable code checks a supported IRQ using an unchecked userspace-controlled integer as the shift amount. Negative or out-of-range values can trigger an out-of-bounds bit shift. The resolved logic requires option 1 to be within the valid IRQ selection range before applying the original IRQ bitmask test.
Likely exposure
Exposure appears limited to Linux systems with affected kernel versions where the comedi pcl812 driver path is reachable. The source bundle does not identify remote exposure, default exploitability, affected distributions beyond Debian notices, or impacted hardware deployments.
Exploitation context
No active exploitation is supported by the provided sources. The CVE is not marked KEV, and the bundle does not include public exploit claims. The described input comes from userspace, so validation should focus on local kernel attack surface and driver availability.
Researcher notes
The record identifies the root cause and fixed logic but omits CVSS, CWE, exploitability, and concrete impact. Avoid assuming privilege escalation or denial of service without additional evidence. Review the stable commits and downstream advisories for exact backport coverage.
Mitigation direction
Apply vendor kernel updates that include the referenced stable fixes.
For Debian LTS systems, follow the cited Debian LTS advisories.
Prioritize hosts where comedi pcl812 is enabled or operationally required.
If patching is delayed, check vendor guidance for supported compensating measures.
Validation and detection
Inventory Linux kernel versions against the affected and fixed version information.
Confirm whether the comedi pcl812 driver is present, loaded, or required.
Check distribution security advisories for backported fixes in installed packages.
Document any systems deferred from patching and their business justification.
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-38530 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Aug 16, 2025, 11:12 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.