Vulnerability in Kernel (CVE-2025-68332)

Summary

Vulnerability in Kernel (CVE-2025-68332). Risk of unauthorized operations or information disclosure. Exploitable via name. Mitigation: upgrade to 5.10.248, 5.15.198, 6.1.160, 6.6.120, 6.12.62, 6.17.12, 6.18.1 or later.

Original description

The description as published by the source.

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

comedi: c6xdigio: Fix invalid PNP driver unregistration

The Comedi low-level driver "c6xdigio" seems to be for a parallel port
connected device. When the Comedi core calls the driver's Comedi
"attach" handler c6xdigio_attach() to configure a Comedi to use this
driver, it tries to enable the parallel port PNP resources by
registering a PNP driver with pnp_register_driver(), but ignores the
return value. (The struct pnp_driver it uses has only the name and
id_table members filled in.) The driver's Comedi "detach" handler
c6xdigio_detach() unconditionally unregisters the PNP driver with
pnp_unregister_driver().

It is possible for c6xdigio_attach() to return an error before it
calls pnp_register_driver() and it is possible for the call to
pnp_register_driver() to return an error (that is ignored). In both
cases, the driver should not be calling pnp_unregister_driver() as it
does in c6xdigio_detach(). (Note that c6xdigio_detach() will be
called by the Comedi core if c6xdigio_attach() returns an error, or if
the Comedi core decides to detach the Comedi device from the driver for
some other reason.)

The unconditional call to pnp_unregister_driver() without a previous
successful call to pnp_register_driver() will cause
driver_unregister() to issue a warning "Unexpected driver
unregister!". This was detected by Syzbot [1].

Also, the PNP driver registration and unregistratio…

Source: OSV.dev (Open Source Vulnerabilities) NVD OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2025-68332 has been found in Kernel.
Attackers can target a specific entry point like name over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade Kernel to 5.10.248, 5.15.198, 6.1.160, 6.6.120, 6.12.62, 6.17.12, 6.18.1 or later.
If unsure, ask your IT team or search "Kernel CVE-2025-68332" on the vendor's site.

CVE-2025-68332 (Kernel)
Attack surface: name / id_table / comedi_legacy_detach
Patched: 5.10.248, 5.15.198, 6.1.160, 6.6.120, 6.12.62, 6.17.12, 6.18.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) exists in Kernel. Attackers reach the vulnerable code path via name.

📍 Affected scope

Check the vendor advisory for the affected versions of Kernel. Attack surface: name / id_table / comedi_legacy_detach.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 5.10.248, 5.15.198, 6.1.160, 6.6.120, 6.12.62, 6.17.12, 6.18.1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Kernel' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
grep -r 'Kernel' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で Kernel を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade Kernel to 5.10.248, 5.15.198, 6.1.160, 6.6.120, 6.12.62, 6.17.12, 6.18.1
```
ステージング環境で 5.10.248, 5.15.198, 6.1.160, 6.6.120, 6.12.62, 6.17.12, 6.18.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Linux Kernel

[{"type":"ECOSYSTEM","events":[{"introduced":"2.6.30"},{"fixed":"5.10.248"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.11.0"},{"fixed":"5.15.198"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.16.0"},{"fixed":"6.1.160"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.2.0"},{"fixed":"6.6.120"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.12.62"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.17.12"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.18.0"},{"fixed":"6.18.1"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

BellSoft Alpaquita BELL-CVE-2025-68332 linux-lts Fixed in: 6.1.161-r0
Debian DEBIAN-CVE-2025-68332 linux Fixed in: 5.10.249-1
Ubuntu UBUNTU-CVE-2025-68332 linux