Skip to content
Systems

CVE-2026-74522

8.8
High
EPSS 0.43%Patch availableAug 17, 2026

Linux ksmbd use-after-free in file close causing kernel memory corruption

common questions

Is CVE-2026-74522 being exploited?

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

How severe is CVE-2026-74522?

CVE-2026-74522 is rated High with a CVSS score of 8.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-74522?

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

What does CVE-2026-74522 affect?

CVE-2026-74522 affects Linux kernel (ksmbd subsystem), SMB servers using ksmbd, Linux distributions with ksmbd enabled. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-74522?

Apply vendor kernel updates with ksmbd fix and restrict SMB access until patched.

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

executive summary
technical analysis
affected
Linux kernel (ksmbd subsystem)SMB servers using ksmbdLinux distributions with ksmbd enabled
impact

Remote SMB interaction can trigger kernel use-after-free, enabling crashes (DoS) and potential privilege escalation or arbitrary kernel code execution.

action required

Patch when possible

affected versions
Linux Linux
  • affected>= 8510a043d334ecdf83d4604782f288db6bf21d60 and < 19bfd90d5aaf63217735d81964585c5306158e5f
  • affected>= 8510a043d334ecdf83d4604782f288db6bf21d60 and < 67aaec2a1fdce3e1dde46c45b5d1ef8cf22f65cd
  • affected>= 8510a043d334ecdf83d4604782f288db6bf21d60 and < 0c3918c2cee62ec6c9de8d5c73ebfe6f833961ac
  • affected>= 8510a043d334ecdf83d4604782f288db6bf21d60 and < 9be4a66f019ea90bd9deca70511f4f9ffebf5c6f
  • affected>= 8510a043d334ecdf83d4604782f288db6bf21d60 and < cffbdc86393b0235383a20c8c59bc32f16036459
  • affected>= 8510a043d334ecdf83d4604782f288db6bf21d60 and < e7188199eff46a636f3436356f0aae039be6dd66
  • affecteddf30cbfd3d8a70e61ce59f63ce5ed2261799ac10
  • affectedaaf1d5ebb358f546414965b39da90107a7ca7ce5
  • affected>= 5.15.38 and < 5.16
  • affected>= 5.17.6 and < 5.18
  • affected5.18
vendor says fixed in< 5.18, >= 6.1.183 and <= 6.1.*, >= 6.6.151 and <= 6.6.*, >= 6.12.103 and <= 6.12.*, >= 6.18.44 and <= 6.18.*, >= 7.1.8 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