CVE-2026-74592
Linux IMA missing truncation hooks could allow integrity checks to be bypassed on file truncation.
Is CVE-2026-74592 being exploited?
Not confirmed. CVE-2026-74592 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.34% probability of exploitation in the next 30 days.
How severe is CVE-2026-74592?
CVE-2026-74592 is rated High with a CVSS score of 8.1. 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-74592?
Yes. A fix has been recorded for CVE-2026-74592. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-74592 affect?
CVE-2026-74592 affects Linux kernel (IMA enabled), Integrity Measurement Architecture (IMA) subsystem. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-74592?
Install kernel update that adds file_truncate/path_truncate hooks; restrict local write/truncate rights.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Local attacker with file write/truncate ability can bypass IMA integrity/audit, enabling undetected file tampering and persistence.
Patch when possible
- affected>= 3323eec921efd815178a23107ab63588c605c0b2 and < 5f46705d96eb60587aa7035acfcbec977e08d620
- affected>= 3323eec921efd815178a23107ab63588c605c0b2 and < dd21c96a71e876c8df9ec546b885a2c5f47bbb05
- affected>= 3323eec921efd815178a23107ab63588c605c0b2 and < 0baed1fa2184c81e4baf76f445d3faa4b738c8f7
- affected>= 3323eec921efd815178a23107ab63588c605c0b2 and < b80bed5c871a80151351342c065579405ce77145
- affected2.6.30
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.