Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-68335: comedi: pcl818: fix null-ptr-deref in pcl818_ai_cancel()

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
  • Fixed version: Linux Linux 5caa40e7c6a43e08e3574f990865127705c22861, 877adccfacb32687b90714a27cfb09f444fdfa16, 88d99ca5adbd01ff088f5fb2ddeba5755e085e52.

Low priority for now. Upgrade to Linux Linux 5caa40e7c6a43e08e3574f990865127705c22861, 877adccfacb32687b90714a27cfb09f444fdfa16, 88d99ca5adbd01ff088f5fb2ddeba5755e085e52 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: comedi: pcl818: fix null-ptr-deref in pcl818_ai_cancel() Syzbot identified an issue [1] in pcl818_ai_cancel(), which stems from the fact that in case of early device detach via pcl818_detach(), subdevice dev->read_subdev may not have initialized its pointer to &struct comedi_async as intended. Thus, any such dereferencing of &s->async->cmd will lead to general protection fault and kernel crash. Mitigate this problem by removing a call to pcl818_ai_cancel() from pcl818_detach() altogether. This way, if the subdevice setups its support for async commands, everything async-related will be handled via subdevice's own ->cancel() function in comedi_device_detach_locked() even before pcl818_detach(). If no support for asynchronous commands is provided, there is no need to cancel anything either. [1] Syzbot crash: Oops: general protection fault, probably for non-canonical address 0xdffffc0000000005: 0000 [#1] SMP KASAN PTI KASAN: null-ptr-deref in range [0x0000000000000028-0x000000000000002f] CPU: 1 UID: 0 PID: 6050 Comm: syz.0.18 Not tainted syzkaller #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025 RIP: 0010:pcl818_ai_cancel+0x69/0x3f0 drivers/comedi/drivers/pcl818.c:762 ... Call Trace: <TASK> pcl818_detach+0x66/0xd0 drivers/comedi/drivers/pcl818.c:1115 comedi_device_detach_locked+0x178/0x750 drivers/comedi/drivers.c:207 do_devconfig_ioctl drivers/comedi/comedi_fops.c:848 [inline] comedi_unlocked_ioctl+0xcde/0x1020 drivers/comedi/comedi_fops.c:2178 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:597 [inline] ...

—No exploit Fix available
Published
Dec 22, 2025
Updated
Oct 19, 2026
EPSS
0.1% · 8th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-68335

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 3.15affected
    • 00aba6e7b5653a6607238ecdab7172318059d984 and later · before b2a5b172dc05be6c4f2c5542c1bbc6b14d60ff16affected · git
    • 00aba6e7b5653a6607238ecdab7172318059d984 and later · before 935ad4b3c325c24fff2c702da403283025ffc722affected · git
    • 00aba6e7b5653a6607238ecdab7172318059d984 and later · before 88d99ca5adbd01ff088f5fb2ddeba5755e085e52affected · git
    • 00aba6e7b5653a6607238ecdab7172318059d984 and later · before 5caa40e7c6a43e08e3574f990865127705c22861affected · git
    • 00aba6e7b5653a6607238ecdab7172318059d984 and later · before d948c53dec36dafe182631457597c49c1f1df5eaaffected · git
    • 00aba6e7b5653a6607238ecdab7172318059d984 and later · before 877adccfacb32687b90714a27cfb09f444fdfa16affected · git
    • 00aba6e7b5653a6607238ecdab7172318059d984 and later · before a51f025b5038abd3d22eed2ede4cd46793d89565affected · git
    • before 3.15not affected · semver
    • 5.15.198 and later · up to and including 5.15.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.162-16.1.162-1
Debian:13linuxbefore 6.12.63-16.12.63-1
Debian:14linuxbefore 6.17.12-16.17.12-1
openSUSE:Tumbleweedkernel-sourcebefore 6.18.5-1.16.18.5-1.1

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2025-68332Dec 22, 2025 · comedi: c6xdigio: Fix invalid PNP driver unregistration
    0Monitor
  • ← EarlierCVE-2025-68334Dec 22, 2025 · platform/x86/amd/pmc: Add support for Van Gogh SoC
    0Monitor
  • Later →CVE-2025-68336Dec 22, 2025 · locking/spinlock/debug: Fix data-race in do_raw_write_lock
    30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux5caa40e7c6a43e08e3574f990865127705c22861Vendor (CNA)
Linux Linux877adccfacb32687b90714a27cfb09f444fdfa16Vendor (CNA)
Linux Linux88d99ca5adbd01ff088f5fb2ddeba5755e085e52Vendor (CNA)
Linux Linux935ad4b3c325c24fff2c702da403283025ffc722Vendor (CNA)
Linux Linuxa51f025b5038abd3d22eed2ede4cd46793d89565Vendor (CNA)
Linux Linuxb2a5b172dc05be6c4f2c5542c1bbc6b14d60ff16Vendor (CNA)
Linux Linuxd948c53dec36dafe182631457597c49c1f1df5eaVendor (CNA)
debian:linux6.1.162-1 · Debian:12Package registry (OSV)
opensuse:kernel-source6.18.5-1.1 · openSUSE:TumbleweedPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records