GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux kernel IMA: file signature silently downgraded to a hash when another security xattr is written

CVSS 7.8CVE-2025-68183Kernel, userspace & hypervisorcurated

Impact

IMA clears the IMA_DIGSIG flag when any other security xattr is set or removed on a file that already carries an IMA signature. On close, IMA then writes a plain hash into security.ima instead of keeping the signature. With IMA and EVM in fix mode - the provisioning mode used to generate reference values - installing packages produces hash-only labels, so the fleet-wide appraisal baseline is built without real signatures and signature-enforcing policies have nothing to verify against. The effect is a weakened integrity baseline on nodes that rely on IMA appraisal for boot-time and runtime attestation, not a direct code-execution path. Setting security.selinux, removing security.evm, or setting an ACL after the signature is enough to trigger it.

Who can reach it

Local, on a host with IMA appraisal configured. Any process that can write a security xattr or an ACL on a file after its IMA signature has been set can cause the signature to be replaced by a hash. Operators hit it unintentionally during package installs on nodes booted with ima_appraise=fix evm=fix.

What to do

Patch the kernel to a stable release that stops IMA_DIGSIG from being reset, then reboot. Nodes that do not enable IMA appraisal are unaffected. Any reference IMA labels generated on an unpatched kernel in fix mode should be regenerated after the patch, since existing security.ima values may be hashes where signatures were intended; the advisory does not list a userspace mitigation.

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.