🛡️ AZL-66935 — kernel

⚪ Unknown ✅ No Known Exploit OSV
N/A
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

CVE-2025-39685 affecting package kernel for versions less than 6.6.104.2-1

In the Linux kernel, the following vulnerability has been resolved:

comedi: pcl726: Prevent invalid irq number

The reproducer passed in an irq number(0x80008000) that was too large,

which triggered the oob.

Added an interrupt number check to prevent users from passing in an irq

number that was too large.

If it->options[1] is 31, then 1 << it->options[1] is still invalid

because it shifts a 1-bit into the sign bit (which is UB in C).

Possible solutions include reducing the upper bound on the

it->options[1] value to 30 or lower, or using 1U << it->options[1].

The old code would just not attempt to request the IRQ if the

options[1] value were invalid. And it would still configure the

device without interrupts even if the call to request_irq returned an

error. So it would be better to combine this test with the test below.

Affected software

AZL-66935 is recorded against 1 package.

  • kernel (fixed in 6.6.104.2-1)

Timeline and source

Published on 5 September 2025 and last revised on 21 April 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.

References

nvd.nist.gov (Web)

Details

Severity Unknown
CVSS Score N/A
CVSS Vector N/A
CWE N/A
Public Exploit ✅ No
Source OSV
Published 2025-09-05
Updated 2026-08-12
Modified 2026-04-21
Fix URL N/A

Affected Packages

Software From version Fixed in
kernel 6.6.104.2-1

Similar Threats

Free Vulnerability Check

Is your site affected by AZL-66935?

BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against AZL-66935 and other known CVE records.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.