Answer in brief
CVE-2026-74567 records a Unknown severity vulnerability in keys: fix out-of-bounds read in keyring_get_key_chunk(). 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 | >=f771fde82051976a6fc0fd570f8b86de4a92124b <d1933e03e8c74a018550c31a393b79c4d95bff40 || >=f771fde82051976a6fc0fd570f8b86de4a92124b <3a744838453fb9309ce5a5526d3252e211d60152 || >=f771fde82051976a6fc0fd570f8b86de4a92124b <e9417d21a22ad2ec398e78fcf084b717ce92cf2f || >=f771fde82051976a6fc0fd570f8b86de4a92124b <8dba33c1e779d0fb9a2acb31e354cf0fc0229111 || >=f771fde82051976a6fc0fd570f8b86de4a92124b <63918731f9ae25b5deb022f118e941e6dddfcef4 | d1933e03e8c74a018550c31a393b79c4d95bff40, 3a744838453fb9309ce5a5526d3252e211d60152, e9417d21a22ad2ec398e78fcf084b717ce92cf2f, 8dba33c1e779d0fb9a2acb31e354cf0fc0229111, 63918731f9ae25b5deb022f118e941e6dddfcef4 |
| Linux/Linuxgeneric | 5.3 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
In the Linux kernel, the following vulnerability has been resolved: keys: fix out-of-bounds read in keyring_get_key_chunk() For description-level chunks keyring_get_key_chunk() advances the read pointer by level * sizeof(long) past the inline prefix but only bounds-checks the prefix, so a long enough key description is read past its kmemdup(desc, desc_len + 1) allocation. Compute the full byte offset and bounds-check the description against it before reading. The walk only reaches a description-level chunk when two keys collide through the hash, x, type and domain_tag chunks, so this is reached from an unprivileged add_key(2) with a crafted pair of same-type keys whose index hashes collide; KASAN reports a slab-out-of-bounds read.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-74567 records a Unknown severity vulnerability in keys: fix out-of-bounds read in keyring_get_key_chunk(). 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 | >=f771fde82051976a6fc0fd570f8b86de4a92124b <d1933e03e8c74a018550c31a393b79c4d95bff40 || >=f771fde82051976a6fc0fd570f8b86de4a92124b <3a744838453fb9309ce5a5526d3252e211d60152 || >=f771fde82051976a6fc0fd570f8b86de4a92124b <e9417d21a22ad2ec398e78fcf084b717ce92cf2f || >=f771fde82051976a6fc0fd570f8b86de4a92124b <8dba33c1e779d0fb9a2acb31e354cf0fc0229111 || >=f771fde82051976a6fc0fd570f8b86de4a92124b <63918731f9ae25b5deb022f118e941e6dddfcef4 | d1933e03e8c74a018550c31a393b79c4d95bff40, 3a744838453fb9309ce5a5526d3252e211d60152, e9417d21a22ad2ec398e78fcf084b717ce92cf2f, 8dba33c1e779d0fb9a2acb31e354cf0fc0229111, 63918731f9ae25b5deb022f118e941e6dddfcef4 |
| Linux/Linuxgeneric | 5.3 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
In the Linux kernel, the following vulnerability has been resolved: keys: fix out-of-bounds read in keyring_get_key_chunk() For description-level chunks keyring_get_key_chunk() advances the read pointer by level * sizeof(long) past the inline prefix but only bounds-checks the prefix, so a long enough key description is read past its kmemdup(desc, desc_len + 1) allocation. Compute the full byte offset and bounds-check the description against it before reading. The walk only reaches a description-level chunk when two keys collide through the hash, x, type and domain_tag chunks, so this is reached from an unprivileged add_key(2) with a crafted pair of same-type keys whose index hashes collide; KASAN reports a slab-out-of-bounds read.
Quoted source text, attributed separately from HOL analysis.