GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux kernel IMA: truncation does not invalidate cached measurements, leaving stale appraisal state

CVE-2026-74592Kernel, userspace & hypervisorcurated

Impact

IMA caches per-inode action flags (IMA_DONE_MASK) so a file is not re-measured on every access. The truncate paths did not reset those flags, so a file modified by truncation kept its earlier measurement, audit record and appraisal verdict. Where IMA is the mechanism behind measured boot, remote attestation or appraisal-enforced binaries, the log and the PCR quote can describe content that no longer matches what is on disk. On attested GPU fleets - confidential-computing tenants, regulated HPC sites - that weakens exactly the guarantee the measurement chain is deployed to provide.

Who can reach it

Local, and only on hosts that actually run an IMA policy. A user who can truncate a file covered by that policy gets a modified file whose cached measurement or appraisal verdict is not refreshed on the next access.

What to do

Take the patched kernel from the linked stable commits, which instantiate the file_truncate and path_truncate hooks so the cache is invalidated at truncation time. Deploy the kernel and reboot each node; policy edits cannot substitute, because the missing hook is what the policy would have keyed off. Hosts with no IMA policy in force are not affected.

References

Related entries

All Kernel, userspace & hypervisor entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.