Answer in brief
CVE-2026-74671 records a Unknown severity vulnerability in ima: fix out-of-bounds read in xattr_verify(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=3ea7a56067e663278470c04fd655adf809e72d4d <d823b5f4557083d1dd92096f796a78a2b1b06d10 || >=3ea7a56067e663278470c04fd655adf809e72d4d <caeb105c15ea2431fa8da7ecfa242d0c68272426 || >=3ea7a56067e663278470c04fd655adf809e72d4d <a784b4732ac7e51862b9b210c2d8b2ab9e83568c || >=3ea7a56067e663278470c04fd655adf809e72d4d <b6cb134707a2127d90a58d69dd818679cae8033c || >=3ea7a56067e663278470c04fd655adf809e72d4d <7e515b6c9aab452a4f0734bd7208e4e780e164ca || >=3ea7a56067e663278470c04fd655adf809e72d4d <27f3924061592d0ef6b04e16f48754b6cb6adf27 || >=3ea7a56067e663278470c04fd655adf809e72d4d <dd04114af0d451091f7b8cbd26d9e37d011e9131 || >=3ea7a56067e663278470c04fd655adf809e72d4d <5ff232d31106f45ac87c3b64e1d35a0667777797 | d823b5f4557083d1dd92096f796a78a2b1b06d10, caeb105c15ea2431fa8da7ecfa242d0c68272426, a784b4732ac7e51862b9b210c2d8b2ab9e83568c, b6cb134707a2127d90a58d69dd818679cae8033c, 7e515b6c9aab452a4f0734bd7208e4e780e164ca, 27f3924061592d0ef6b04e16f48754b6cb6adf27, dd04114af0d451091f7b8cbd26d9e37d011e9131, 5ff232d31106f45ac87c3b64e1d35a0667777797 |
| Linux/Linuxgeneric | 3.13 | Not reported |
Published upstream
Aug 22, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 22, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 22, 2026
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.
Quoted source text, attributed separately from HOL analysis.