VulnerabilityPublished 26 Oct 2026Updated 27 Oct 2026

CVE-2026-99086: Linux kernel · dm-integrity: validate the superblock on resume

Affects Linux kernelSource GCVE Database

Authoritative record:CVE-2026-99086· High

Not known to be exploited.

Data as of 28 Oct 2026, 01:30 UTC

Severity

High

Rated by Threat Radar · CVSS not yet scored by NVD

Exploitation evidence

Disclosed: evidence found.
CVE published 23 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Ubuntu 26.10linux`pkg:deb/ubuntu/linux?arch=source&distro=stonking`Other threats	Affected 7.0.0-14.14 – 7.3.0-9.9 6 affected builds	Fixed in–
Ubuntu 26.10linux-aws`pkg:deb/ubuntu/linux-aws?arch=source&distro=stonking`Other threats	Affected 7.0.0-1004.4 – 7.3.0-1003.3 5 affected builds	Fixed in–
Ubuntu 26.10linux-azure`pkg:deb/ubuntu/linux-azure?arch=source&distro=stonking`Other threats	Affected 7.0.0-1004.4 – 7.3.0-1003.3 5 affected builds	Fixed in–
Ubuntu 26.10linux-azure-fde`pkg:deb/ubuntu/linux-azure-fde?arch=source&distro=stonking`Other threats	Affected =7.0.0-1004.4 =7.3.0-1002.3 =7.3.0-1003.4	Fixed in–
Ubuntu 26.10linux-gcp`pkg:deb/ubuntu/linux-gcp?arch=source&distro=stonking`Other threats	Affected 7.0.0-1003.3 – 7.3.0-1003.3 5 affected builds	Fixed in–
Ubuntu 26.10linux-oracle`pkg:deb/ubuntu/linux-oracle?arch=source&distro=stonking`Other threats	Affected 7.0.0-1003.3 – 7.3.0-1003.3 5 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available that snapshots the validated superblock during the constructor and refuses to resume if any on-disk geometry fields have changed. Users should apply the updated Linux kernel versions that include this fix to prevent exploitation.

Description

A vulnerability in the Linux kernel's dm-integrity module allows an attacker to modify the superblock on the underlying device while the dm-integrity device is suspended. This causes a mismatch between the in-memory and on-disk superblock data upon resume, potentially leading to out-of-bounds memory writes.

Impact

This vulnerability can lead to out-of-bounds memory writes during the resume operation of the dm-integrity device, potentially causing system instability or crashes. It arises from a lack of validation of the superblock on resume, allowing malicious or accidental modification of the superblock to corrupt memory.

Summary

The dm_integrity_resume() function in the Linux kernel re-reads the superblock from the device without validating it, while the constructor validates and sizes in-memory structures based on the superblock. If the user modifies the superblock during suspension, the resumed state may have inconsistent geometry fields. Specifically, increasing log2_sectors_per_block causes the journal entry index to exceed the journal boundary, resulting in dm-integrity writing 512 bytes through lowmem_page_address(NULL), a null pointer dereference and memory corruption. The fix involves snapshotting the validated superblock in the constructor and refusing to resume if critical geometry fields have changed.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Oct 2026, 01:30 UTC

Technical details

References

Community reviews

Related threats