CVE-2026-74567
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.
CSIRTS triage
- What
- The keyring_get_key_chunk function reads beyond allocated bounds, leaking kernel memory.
- Who is affected
- Systems using kernel keyring functionality running affected Linux kernel versions.
- Urgency
- Low priority; information disclosure risk but requires local access to keyring operations.
- Action
- Apply kernel patches to add bounds checking in keyring_get_key_chunk().
AI-assisted analysis generated from the source advisory — verify against the original.
⚡ Watch CVE-2026-74567
Get an email if CVE-2026-74567 is added to CISA KEV, gains public exploit code, or a new advisory cites it — max one per day, one-click unsubscribe.
Exploitation outlook
- Low exploitation risk0.12% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 2% of all EPSS-scored CVEs.
Advisory coverage (2)
External references
Embed the live status
— this badge updates automatically when the KEV or exploit status changes. How to embed it →
[](https://www.csirts.com/cve/CVE-2026-74567)