Linux kernel vulnerability can corrupt kernel memory, crash systems, or enable privilege escalation; kernel is core infrastructure used widely across organizations.
CVE-2026-74591
Linux kernel pagecache bug can corrupt memory, crash systems, or allow privilege escalation.
Is CVE-2026-74591 being exploited?
Not confirmed. CVE-2026-74591 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.44% probability of exploitation in the next 30 days.
How severe is CVE-2026-74591?
CVE-2026-74591 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-74591?
Yes. A fix has been recorded for CVE-2026-74591. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-74591 affect?
CVE-2026-74591 affects Linux kernel (mm/filemap::__filemap_add_folio), All Linux distributions using affected kernels. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-74591?
Install vendor kernel updates and reboot affected hosts; audit for recent crashes.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Local kernel pagecache flaw can corrupt kernel memory, cause SIGSEGV/SIGILL, crash systems or enable privilege escalation/kernel RCE.
Immediate action required
- affected>= 200a89c159a7a416115e6e309183c82183bf98aa and < 4917e3ebcab50f0265e8ca01c8567de4c4a47511
- affected>= 200a89c159a7a416115e6e309183c82183bf98aa and < 267ecd2eb7759c26f1a026eb0a5b231071534c9c
- affected>= 200a89c159a7a416115e6e309183c82183bf98aa and < 86da3f7e1e609e1e8bfbab198af68467c5a015a5
- affected6.15
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.