Skip to content
Systems

CVE-2026-74608

9.8
Critical
EPSS 0.48%Patch availableAug 25, 2026

Use-after-free in Linux CIFS/SMB client can cause kernel memory corruption.

common questions

Is CVE-2026-74608 being exploited?

Not confirmed. CVE-2026-74608 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.48% probability of exploitation in the next 30 days.

How severe is CVE-2026-74608?

CVE-2026-74608 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-74608?

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

What does CVE-2026-74608 affect?

CVE-2026-74608 affects Linux kernel (CIFS/SMB client), Hosts mounting SMB/CIFS shares. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-74608?

Apply vendor kernel security updates immediately; avoid untrusted SMB servers.

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

executive summary
technical analysis
affected
Linux kernel (CIFS/SMB client)Hosts mounting SMB/CIFS shares
impact

Malicious SMB server can trigger a kernel use-after-free in the CIFS client, enabling kernel memory corruption with potential code execution, privilege escalation, or DoS.

action required

Immediate action required

affected versions
Linux Linux
  • affected>= cbc53148cc0946b72d62a3c53870cb22ce4ec284 and < 64d7584e62ac8cdc750455c5fdc6008fc2de4f06
  • affected>= cff97d683a083b862a8bb24309e0f4d2d928128a and < c292d4686f717c03e5022fc4ae7c782f39a94915
  • affected>= 6aac002bcfd554aff6d3ebb55e1660d078d70ab0 and < 47dfac48bce7198ad4f1a388fc8c9491f878ac3b
  • affected>= 6aac002bcfd554aff6d3ebb55e1660d078d70ab0 and < 1ffacbadc14530e55b8d86f7b917524f6a0fb891
  • affected>= 6aac002bcfd554aff6d3ebb55e1660d078d70ab0 and < 1305eadc6a7d78a8d0a52eee29ddd2d9e8a27805
  • affected>= 6aac002bcfd554aff6d3ebb55e1660d078d70ab0 and < 4986410316b1ae0e63c6ce418e4eb196723626e7
  • affected22a6c5b3425f327e7f4c3606a72277dce82c7d83
  • affected>= 6.1.78 and < 6.1.183
  • affected>= 6.6.17 and < 6.6.152
  • affected>= 6.7.5 and < 6.8
  • affected6.8
vendor says fixed in< 6.8, >= 6.1.183 and <= 6.1.*, >= 6.6.152 and <= 6.6.*, >= 6.12.104 and <= 6.12.*, >= 6.18.45 and <= 6.18.*, >= 7.1.9 and <= 7.1.*, >= 7.2 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