CVE-2026-64109
Local Linux kernel UAF in AF_UNIX stream sockets allowing kernel corruption or escalation.
Is CVE-2026-64109 being exploited?
Not confirmed. CVE-2026-64109 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.13% probability of exploitation in the next 30 days.
How severe is CVE-2026-64109?
CVE-2026-64109 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-64109?
Yes. A fix has been recorded for CVE-2026-64109. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-64109 affect?
CVE-2026-64109 affects Linux kernel (AF_UNIX / unix_stream sockets), Kernels with sendpage/splice support (post-6.5 changes). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-64109?
Apply vendor/kernel updates to a fixed kernel release immediately.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Local use-after-free via AF_UNIX recv/MSG_PEEK race can crash the kernel or enable local privilege escalation / kernel memory corruption.
Patch when possible
- affected>= 2b514574f7e88c8498027ee366fd6e7aae5aa4b5 and < 26342087fac93b3932e6af61dc91ec029cb8a623
- affected>= 2b514574f7e88c8498027ee366fd6e7aae5aa4b5 and < 38bccb927d83d7d52e5b20015a172a0b6101d11e
- affected>= 2b514574f7e88c8498027ee366fd6e7aae5aa4b5 and < acdff9907478e82208475b1151700d0b71dcdc63
- affected>= 2b514574f7e88c8498027ee366fd6e7aae5aa4b5 and < 5f162f95a95834f06a8ec6140889272ad12e842f
- affected>= 2b514574f7e88c8498027ee366fd6e7aae5aa4b5 and < be309f8eae8b474a4a617eaae01324da996fc719
- affected4.2
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.