Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2025-38687 high CVSS 7.3

Vulnerability in Linux kernel (CVE-2025-38687)

Summary

Vulnerability in Linux kernel (CVE-2025-38687). Successful exploitation can lead to full system takeover. Exploitable via COMEDI_DEVCONFIG.

Original description

The description as published by the source.

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

comedi: fix race between polling and detaching

syzbot reports a use-after-free in comedi in the below link, which is
due to comedi gladly removing the allocated async area even though poll
requests are still active on the wait_queue_head inside of it. This can
cause a use-after-free when the poll entries are later triggered or
removed, as the memory for the wait_queue_head has been freed. We need
to check there are no tasks queued on any of the subdevices' wait queues
before allowing the device to be detached by the COMEDI_DEVCONFIG
ioctl.

Tasks will read-lock dev->attach_lock before adding themselves to the
subdevice wait queue, so fix the problem in the COMEDI_DEVCONFIG ioctl
handler by write-locking dev->attach_lock before checking that all of
the subdevices are safe to be deleted. This includes testing for any
sleepers on the subdevices' wait queues. It remains locked until the
device has been detached. This requires the comedi_device_detach()
function to be refactored slightly, moving the bulk of it into new
function comedi_device_detach_locked().

Note that the refactor of comedi_device_detach() results in
comedi_device_cancel_all() now being called while dev->attach_lock
is write-locked, which wasn't the case previously, but that does not
matter.

Thanks to Jens Axboe for diagnosing the problem and co-developing this
patch.

Source: NIST National Vulnerability Database NVD GitHub Advisory

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-38687 has been found in Linux kernel.
Attackers can target a specific entry point like COMEDI_DEVCONFIG over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 7.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Linux kernel CVE-2025-38687" on the vendor's site.

CVE-2025-38687 (Linux kernel) — CWE-362 / CVSS v3 7.3
Attack vector: local
Attack surface: COMEDI_DEVCONFIG
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 (CWE-362) exists in Linux kernel. Attackers reach the vulnerable code path via COMEDI_DEVCONFIG.

📍 Affected scope

Check the vendor advisory for the affected versions of Linux kernel. Attack surface: COMEDI_DEVCONFIG.

🔥 Severity

Severity: High (CVSS 7.3/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ 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. Audit SBOM/dependencies to find affected services.

Response actions

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

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで Linux kernel を使っているサービスとバージョンを洗い出す。

  2. 2
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Linux Kernel
[{"type":"ECOSYSTEM","events":[{"introduced":"3.14.0"},{"fixed":"5.4.297"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.5.0"},{"fixed":"5.10.241"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.11.0"},{"fixed":"5.15.190"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.16.0"},{"fixed":"6.1.149"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.2.0"},{"fixed":"6.6.103"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.12.43"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.15.11"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.16.0"},{"fixed":"6.16.2"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details