Skip to content
Noroxi
CVE.org (no NVD analysis yet)· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
  • Fixed version: Linux Linux 454b67fcc28c18502e47dfb9f067b04c28628ada, 6.13, 6.18.58.

Low priority for now. Upgrade to Linux Linux 454b67fcc28c18502e47dfb9f067b04c28628ada, 6.13, 6.18.58 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: dm-integrity: validate the superblock on resume dm_integrity_resume() re-reads the superblock from the device so that it picks up the flags and the recalculate position. It performs no validation on the result, while the constructor validates the superblock it reads and sizes all the in-memory structures according to it. The user may modify the superblock on the underlying device while the dm-integrity device is suspended, so that the two no longer agree. In particular, access_journal_data() shifts the journal entry index by ic->sb->log2_sectors_per_block, while ic->journal_section_sectors and the journal page list were computed with the value that was present at constructor time. Increasing log2_sectors_per_block makes the index run past the end of the journal, and dm-integrity then writes 512 bytes through lowmem_page_address(NULL). Snapshot the validated superblock in the constructor and refuse to resume if any of the fields that describe the on-disk geometry changed.

—No exploit Fix available
Published
Oct 23, 2026
Updated
Oct 23, 2026
EPSS
0.1% · 5th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-99086

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 824b9c27d7b600520b95f0cab95a47d1b08a9483, fb49f209995f729053c6ee728436f98d78a49b6f, c6138af1f5454c2631a837916fda958ea72c0d71, 3ff70e2e31c419e2230d0c66cb2bfb3b1b414b7f, 7.0affected
    • 38625191f32f77a9d5fc7cc15f4f9b78768bfb33 and later · before 454b67fcc28c18502e47dfb9f067b04c28628adaaffected · git
    • 118ba36e446c01e3cd34b3eedabf1d9436525e1d and later · before e9ec5cbbaf4dd3a02ae3d81719f4fcb9b609aa8eaffected · git
    • 118ba36e446c01e3cd34b3eedabf1d9436525e1d and later · before fc79aeb86a2c244c1f1894e2d8f2966fe2b60fa2affected · git
    • 6.18.16 and later · before 6.18.58affected · semver
    • 6.1.165 and later · before 6.2affected · semver
    • 6.6.128 and later · before 6.7affected · semver
    • 6.12.75 and later · before 6.13affected · semver
    • 6.19.6 and later · before 6.20affected · semver
    • before 7.0not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxfrom 0—
Debian:14linuxbefore 7.2.12-17.2.12-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-99084Oct 23, 2026 · readdir: take no inode lock on an immutable directory
    0Monitor
  • ← EarlierCVE-2026-99085Oct 23, 2026 · sched_ext: Fix CPU hotplug hang when a dying CPU's tasks sit in the BPF scheduler
    0Monitor
  • Later →CVE-2026-99087Oct 23, 2026 · dm-integrity: fix NULL pointer dereference when the 'R' flag is used
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux454b67fcc28c18502e47dfb9f067b04c28628adaVendor (CNA)
Linux Linux6.13Vendor (CNA)
Linux Linux6.18.58Vendor (CNA)
Linux Linux6.2Vendor (CNA)
Linux Linux6.20Vendor (CNA)
Linux Linux6.7Vendor (CNA)
Linux Linuxe9ec5cbbaf4dd3a02ae3d81719f4fcb9b609aa8eVendor (CNA)
Linux Linuxfc79aeb86a2c244c1f1894e2d8f2966fe2b60fa2Vendor (CNA)
debian:linux7.2.12-1 · Debian:14Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. Fix recordedsame day
  3. TodayNov 2, 2026+10 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Exploit maturity— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records