# CVE-2026-74567: keys: fix out-of-bounds read in keyring_get_key_chunk()

> An out-of-bounds read in the Linux kernel keyring allows local attackers to disclose sensitive memory contents via crafted key descriptions.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2026
- **Updated:** 16 Oct 2026
- **Also known as:** AZL-96132, BELL-CVE-2026-74567, DEBIAN-CVE-2026-74567, GHSA-fp4g-wh5w-9xf4, UBUNTU-CVE-2026-74567

## What is CVE-2026-74567?

CVE-2026-74567 is a high-severity memory corruption vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2026-74567?


## How do I fix CVE-2026-74567?

Apply the vendor's patch.

## Is CVE-2026-74567 being exploited?

There is no known exploitation of CVE-2026-74567 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-74567 and fix it if it is affected.

What it is: CVE-2026-74567 is a high-severity memory corruption vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-74567 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-74567/ (Markdown: https://insights.sbomify.com/CVE-2026-74567/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-74567
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-74567
- OSV: https://osv.dev/vulnerability/CVE-2026-74567

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-74567/
Summaries are generated and may contain mistakes; the official description above is the record.