CVE-2026-74671
CVE CVE-2026-74671EUVD EUVD-2026-64358Published 2026-08-22T15:32:41.000Z
What the advisory describes
In the Linux kernel, the following vulnerability has been resolved: ima: fix out-of-bounds read in xattr_verify() The digest-length check in xattr_verify() mixes int and size_t: if (xattr_len - sizeof(xattr_value->type) - hash_start >= iint->ima_hash->length) sizeof() yields size_t, so the usual arithmetic conversions promote the whole left-hand side to unsigned 64-bit before the subtraction runs. For a truncated xattr this underflows instead of going negative: a 1-byte IMA_XATTR_DIGEST_NG xattr (xattr_len == 1, hash_start == 1) turns "1 - 1 - 1" into SIZE_MAX, which is trivially >= ima_hash->length. The check then passes and the following memcmp() reads iint->ima_hash->length bytes starting past the end of the buffer vfs_getxattr_alloc() allocated for it. Nothing upstream clamps xattr_len back into a safe range first: ima_get_hash_algo() only special-cases xattr_len < 2 to pick a default algorithm, and evm_verifyxattr() returns INTEGRITY_UNKNOWN rather than failing when no HMAC key is loaded, so a truncated security.ima value reaches the length check as-is. Rewrite the comparison so every operand stays a signed int and no implicit conversion to size_t can occur.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux 3ea7a56067e663278470c04fd655adf809e72d4d <7e515b6c9aab452a4f0734bd7208e4e780e164ca; patch: 7.2; 3.13; 3ea7a56067e663278470c04fd655adf809e72d4d <d823b5f4557083d1dd92096f796a78a2b1b06d10; 3ea7a56067e663278470c04fd655adf809e72d4d <a784b4732ac7e51862b9b210c2d8b2ab9e83568c; 3ea7a56067e663278470c04fd655adf809e72d4d <b6cb134707a2127d90a58d69dd818679cae8033c; patch: 6.18.45; patch: 0; patch: 6.1.183; patch: 5.10.265; patch: 5.15.216; 3ea7a56067e663278470c04fd655adf809e72d4d <dd04114af0d451091f7b8cbd26d9e37d011e9131; patch: 6.12.104; 3ea7a56067e663278470c04fd655adf809e72d4d <5ff232d31106f45ac87c3b64e1d35a0667777797; patch: 7.1.9; 3ea7a56067e663278470c04fd655adf809e72d4d <caeb105c15ea2431fa8da7ecfa242d0c68272426; 3ea7a56067e663278470c04fd655adf809e72d4d <27f3924061592d0ef6b04e16f48754b6cb6adf27; patch: 6.6.152
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.