SecOps SignalSecurity Intelligence Workspace
Loading collection status
Vulnerabilities/CVE-2026-64341Public Intelligence Dossier
Source: linux · Limited verification•Last verified: •Collection Running
CVE-2026-64341Unknown / EvaluatingHIGH (raw)CVSS 7.8CWE-416

In the Linux kernel, the following vulnerability has been resolved: USB: iowarrior: fix use-after-free on disconnect race mutex_unlock() may access the mutex structure after releasing the lock and therefore cannot be used to manage lifetime of objects directly (unlike spinlocks and refcounts)

Published: 25 Jul 2026•Last updated: 21 Oct 2026, 06:49 PM IST•Source identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Dossier completeness: source-provided sections 2 / 3 · rule guidance available. Missing source facts count as incomplete.
Official source
CISA KEV catalog
Unknown
KEV status was not determined.
CVSS score
7.8HIGH (raw)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Metric sourcenvd@nist.gov
EPSS probability
0.1%0.001
Percentile2nd
Weakness type
CWE-416
No further CWE recorded
Remediation
Patch status unknown
No fixed version or KB recorded

Why It Matters

Analysis dossier

Why It Matters

In the Linux kernel, the following vulnerability has been resolved: USB: iowarrior: fix use-after-free on disconnect race mutex_unlock() may access the mutex structure after releasing the lock and therefore cannot be used to manage lifetime of objects directly (unlike spinlocks and refcounts). [1][2] Use a kref to release the driver data to avoid use-after-free in mutex_unlock() when release() races with disconnect(). [1] a51749ab34d9 ("locking/mutex: Document that mutex_unlock() is non-atomic") [2] 2b9d9e0a9ba0 ("locking/mutex: Clarify that mutex_unlock(), and most other sleeping locks, can still use the lock object after it's unlocked")

SOC priority

High

Actively exploited (source statement)

Unknown

Publicly disclosed

Unknown

Risk basis: SOC ecosystem technology relevance; HIGH severity; No confirmed exploitation signal in current enrichment; Source severity; no confirmed exploitation signal

Affected Products & Remediation

1 source-backed product
Affected products and versions (source)
  • linux linux kernel · >= 2.6.21.1 < 6.12.97; >= 6.13 < 7.1.4; 2.6.21; 7.2 · NVD CPE · Source
Recorded patch / KBNot provided by source

Vendor or catalog guidance (source)

Not provided by source

Known exploitation (source facts)

Only what a source states. Unknown means no source has said either way; it is not "not exploited".

CISA KEV
Unknown
Exploited (source statement)
Unknown
Publicly disclosed (source)
Unknown

Suggested hunting (rule-based inference)

SecOps Signal recommendation (rule-based inference). These steps are hunting hypotheses from the vulnerability class; they do not state or imply that exploitation occurred here or anywhere.

Matched local-access-review (CVSS AV:L, CVSS PR:L)

Exposure

  1. Identify hosts reporting this CVE, prioritising shared or multi-user systems.Telemetry: DeviceTvmSoftwareVulnerabilities · A local, low-privilege vector matters most where untrusted users can run code. · Rule local-access-review

Exploitation evidence

  1. Review source-stated impact and relevant application errors on affected hosts; local access alone does not establish privilege escalation.Telemetry: DeviceProcessEvents · The vector establishes local access and low privileges only. Confirm the impact from the advisory before choosing a specific hunt. · Rule local-access-review

Response

  1. Confirm the source-stated update on affected hosts.Telemetry: DeviceTvmSoftwareVulnerabilities · Host inventory can verify remediation. · Rule local-access-review

CISA KEV Record

CISA KEV status was not determined for this record.

Change History & Source Data

— No recorded material change

CNA / source
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Record status · verification
UPDATED · NVD API
CPE
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*, cpe:2.3:o:linux:linux_kernel:2.6.21:-:*:*:*:*:*:*, cpe:2.3:o:linux:linux_kernel:2.6.21:rc2:*:*:*:*:*:*, cpe:2.3:o:linux:linux_kernel:2.6.21:rc3:*:*:*:*:*:*, cpe:2.3:o:linux:linux_kernel:2.6.21:rc4:*:*:*:*:*:*, cpe:2.3:o:linux:linux_kernel:2.6.21:rc5:*:*:*:*:*:*, cpe:2.3:o:linux:linux_kernel:2.6.21:rc6:*:*:*:*:*:*, cpe:2.3:o:linux:linux_kernel:2.6.21:rc7:*:*:*:*:*:*, cpe:2.3:o:linux:linux_kernel:7.2:rc1:*:*:*:*:*:*, cpe:2.3:o:linux:linux_kernel:7.2:rc2:*:*:*:*:*:*

Evidence & Provenance

3 public sources
git.kernel.orgSource recordnvd.nist.govSource recordgit.kernel.orgSource record

Linked by the query's stored exact CVE association. Review required tables and validation status before use.

Detection Hunting Query
Target: DeviceTvmSoftwareVulnerabilities•Defender XDR
Detect endpoints exposed to CVE-2026-64341
Purpose: Exposure assessment (Category: Exposure Check)Why linked: Query metadata names CVE-2026-64341
DeviceTvmSoftwareVulnerabilities| where CveId == "CVE-2026-64341"| project DeviceId, DeviceName, OSPlatform, OSVersion, SoftwareVendor, SoftwareName, SoftwareVersion, CveId, VulnerabilitySeverityLevel, RecommendedSecurityUpdate, RecommendedSecurityUpdateId| sort by VulnerabilitySeverityLevel desc
Schema Checked · Not runtime validatedSource: SecOps Signal deterministic template · Limited verificationStatic screening: Passed structure and schema checks; tenant execution is not verified.
Open KQL Library

Looking up related community queries…

Loading related intelligence

Correlated briefings

SecOps Signal surfaces public advisory facts only. A missing value means the source has not published it, not that your environment is unaffected. No tenant inventory is connected.