CVE-2026-99087 — dm-integrity: fix NULL pointer dereference when the 'R' flag is used
In the Linux kernel, the following vulnerability has been resolved: dm-integrity: fix NULL pointer dereference when the 'R' flag is used If the dm-integrity device has the SB_FLAG_DIRTY_BITMAP flag set and the user activates the device in the 'R' mode, a crash in dm_integrity_resume happens because the function attempts to read the journal containing the bitmap. This patch makes dm-integrity skip any writes to the device in dm_integrity_resume if the device is activated in the 'R' mode.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- No scoring signals.
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux | ≥ 468dfca38b1a6fbdccd195d875599cb7c8875cd9 and < 2e25842f0e4423e0efb243f56153d842ed6b933f≥ 468dfca38b1a6fbdccd195d875599cb7c8875cd9 and < 69ed43ed8a174465fca1ba6bfbde53e4618c8956≥ 468dfca38b1a6fbdccd195d875599cb7c8875cd9 and < 7d4d4f3b668d708d94f62ecdd33ac330a6fd8a84version 5.2 | Vulnerable | CVE Program (cve.org) e CISA ADP |
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 23, 2026 – Oct 23, 2026
- 1× Official description updated · Oct 23, 2026 – Oct 23, 2026
References
3 on the record
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-99086 dm-integrity: validate the superblock on resume 8h
- Unknown CVE-2026-99079 net/mlx5e: Prevent stale XSK buffer release on refill retry 8h
- Unknown CVE-2026-99080 fs: Free any excess xarray nodes in clear_inode() 8h
- Unknown CVE-2026-99081 bnxt_en: fix DMA mapping length for padded small packets 8h
- Unknown CVE-2026-99082 KVM: x86: Use active memslots for the per-vCPU MMIO cache 8h
- Unknown CVE-2026-99083 ksmbd: fix heap out-of-bounds write in krb5_authenticate() 8h
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No FIRST EPSS score.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-99087 is "dm-integrity: fix NULL pointer dereference when the 'R' flag is used", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.