cve.bz

CVE-2026-110036 Year 2038 problem, Y2K38, Y2038, Epochalypse

3.3 lowEPSS 0.2%

Low (3.3). EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
A flaw was found in device-mapper-persistent-data. A local attacker can cause a Denial of Service (DoS) by inducing a user or system tool to process crafted device metadata containing an excessively large block index. An arithmetic error in the synchronous block reading logic causes the application to panic and unexpectedly terminate.

Severity

CVSS 3.1

3.3 low
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L
EPSS
0.2% (unchanged from 0.2% a week ago; 0.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 8th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-10-14. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-190 Integer Overflow or Wraparound (Year 2038 problem, Y2K38, Y2038, Epochalypse)
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-110036 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-110036?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-110036?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-110036 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Red Hat

Red Hat rates this Low.

Red Hat's statement

Red Hat rates this vulnerability as Low impact because exploitation requires a user to process maliciously crafted metadata with persistent data tools, resulting only in a localized process panic. The issue does not affect running kernel components, grant elevated privileges, or compromise data confidentiality or integrity. In standard Red Hat Enterprise Linux deployments, these utilities are invoked on demand for administrative storage maintenance on trusted devices, significantly limiting practical exposure.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10device-mapper-persistent-dataFix deferred
Red Hat Enterprise Linux 6device-mapper-persistent-dataOut of support scope
Red Hat Enterprise Linux 7device-mapper-persistent-dataFix deferred
Red Hat Enterprise Linux 8device-mapper-persistent-dataFix deferred
Red Hat Enterprise Linux 9device-mapper-persistent-dataOut of support scope
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Fix deferred
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Fix deferred
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-9Fix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-110036.

Attack patterns (CAPEC)

  • CAPEC-92 Forced Integer Overflow Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON