# CVE-2026-99098: dm-integrity: fix buffer overflow in inline mode with large tag size


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** BELL-CVE-2026-99098, DEBIAN-CVE-2026-99098, GHSA-wfqx-5v3g-mpcg, UBUNTU-CVE-2026-99098

## What is CVE-2026-99098?

CVE-2026-99098 is a vulnerability in Linux, published on 26 Oct 2026. 

### Official description

In the Linux kernel, the following vulnerability has been resolved:

dm-integrity: fix buffer overflow in inline mode with large tag size

In inline mode, dm_integrity_check and dm_integrity_inline_recheck
compute the checksum of each block into an on-stack buffer of
HASH_MAX_DIGESTSIZE bytes. integrity_sector_checksum pads its result
with zeroes up to the tag size, so if the tag size is larger than
HASH_MAX_DIGESTSIZE, the padding runs past the end of the buffer. With
CONFIG_STACKPROTECTOR the kernel panics in dm_integrity_check on the
first read.

Enlarge both buffers to hold MAX_TAG_SIZE bytes, as commit b93b6643e9b5
("dm integrity: fix a crash with unusually large tag size") did for
integrity_metadata.

Note that this is not a security bug because the buffer overflow can only
be triggered by root.

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


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

Upgrade to a fixed version.

## Is CVE-2026-99098 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-99098 is a vulnerability in Linux, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-99098 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-99098/ (Markdown: https://insights.sbomify.com/CVE-2026-99098/index.md)
```

## Sources

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

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