Skip to content
Systems

CVE-2026-64162

9.8
Critical
EPSS 0.35%Patch availableJul 21, 2026

Uninitialized spinlock in Linux idpf driver can cause kernel crash/DoS.

common questions

Is CVE-2026-64162 being exploited?

Not confirmed. CVE-2026-64162 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.35% probability of exploitation in the next 30 days.

How severe is CVE-2026-64162?

CVE-2026-64162 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-64162?

Yes. A fix has been recorded for CVE-2026-64162. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-64162 affect?

CVE-2026-64162 affects Linux kernel (idpf driver), Systems with idpf-based NICs, Kernels prior to idpf fix. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-64162?

Apply kernel update containing the idpf spinlock init fix immediately

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Linux kernel (idpf driver)Systems with idpf-based NICsKernels prior to idpf fix
impact

PTP worker can take an uninitialized spinlock, causing lockdep warnings and potential kernel crash or DoS on systems with idpf NICs.

action required

Patch when possible

affected versions
Linux Linux
  • affected>= 5cb8805d2366b20ee4d7afff586d8acf17649330 and < eb5991d4c8ba2e8153dfcda3e66a9608377b7dce
  • affected>= 5cb8805d2366b20ee4d7afff586d8acf17649330 and < 3122d70b7c0101d897fb795658a7b93f854935f2
  • affected>= 5cb8805d2366b20ee4d7afff586d8acf17649330 and < da4f76b6a84ede14a71282ef841768299ead0221
  • affected6.16
vendor says fixed in< 6.16, >= 6.18.34 and <= 6.18.*, >= 7.0.11 and <= 7.0.*, >= 7.1 and <= *

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free