# CVE-2026-98222: KEYS: encrypted: fix integer overflow of datablob_len

> An integer overflow in the Linux kernel encrypted key subsystem allows local attackers to trigger a slab-out-of-bounds write, potentially leading to code execution or privilege escalation.

- **Severity:** Not scored
- **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:** 6 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-106092, BELL-CVE-2026-98222, DEBIAN-CVE-2026-98222, GHSA-8jg9-f732-244h, UBUNTU-CVE-2026-98222

## What is CVE-2026-98222?

CVE-2026-98222 is a vulnerability in Linux, published on 6 Oct 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: encrypted: fix integer overflow of datablob_len

encrypted_key_alloc() stores datablob_len in a u16. It is computed from
multiple string and payload lengths. If the result exceeds U16_MAX, the
assignment truncates the allocation size. KASAN reports a 32760-byte
slab-out-of-bounds write when __ekey_init() copies the master key
description into the undersized buffer.

The total payload length stored in key->datalen is also a u16. Use
check_add_overflow() to reject values that do not fit either destination,
and use kzalloc_flex() for the flexible-array allocation.

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


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

Apply the vendor's patch.

## Is CVE-2026-98222 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-98222 is a vulnerability in Linux, published on 6 Oct 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-98222 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-98222/ (Markdown: https://insights.sbomify.com/CVE-2026-98222/index.md)
```

## Sources

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

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