LiveActive security incident?Get immediate response
CVE Record

CVE-2025-39940: dm-stripe: fix a possible integer overflow

In the Linux kernel, the following vulnerability has been resolved: dm-stripe: fix a possible integer overflow There's a possible integer overflow in stripe_io_hints if we have too large chunk size. Test if the overflow happened, and if it did, don't set limits->io_min and limits->io_opt;

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue affects the device-mapper stripe code. With an excessively large stripe chunk size, an integer overflow could occur while setting I/O hint limits. The public sources do not provide CVSS, impact details, or evidence of active exploitation.

Executive priority

Treat this as a patch-tracking item unless your environment relies heavily on dm-stripe. There is not enough public evidence to justify emergency response, but kernel storage-path bugs should be remediated through normal maintenance windows.

Technical view

The flaw is in dm-stripe's stripe_io_hints path. If chunk size is too large, arithmetic used for limits->io_min and limits->io_opt can overflow. The fix tests for overflow and skips setting those limits when overflow is detected.

Likely exposure

Exposure is most likely on Linux systems using dm-stripe configurations on affected kernel versions. The bundle marks Linux kernel versions as affected but does not provide complete downstream distribution package status.

Exploitation context

CISA KEV status is false in the bundle, and no cited source states active exploitation. The available material describes a kernel correctness fix, not a public exploit or weaponized attack path.

Researcher notes

The key evidence is limited to the CVE description and upstream stable commits. Public data does not state memory corruption, privilege escalation, denial of service, or trigger prerequisites beyond overly large chunk size. Avoid assuming exploitability without further kernel analysis.

Mitigation direction

  • Apply kernel updates containing the referenced stable fixes.
  • Check Linux distribution advisories for fixed kernel package versions.
  • Prioritize systems using dm-stripe or unusual large stripe chunk sizes.
  • If patching is delayed, seek vendor guidance for mitigations.

Validation and detection

  • Inventory running Linux kernel versions across servers.
  • Identify systems using dm-stripe device-mapper targets.
  • Compare kernels against distribution fixed-version advisories.
  • Confirm updated kernels include the referenced stable commits.
  • Document any unpatched dm-stripe systems for exception tracking.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-39940 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
4Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux40bea431274c247425e7f5970d796ff7b37a2b22, 40bea431274c247425e7f5970d796ff7b37a2b22, 40bea431274c247425e7f5970d796ff7b37a2b22unaffected
LinuxLinux2.6.31, 0, 6.12.49, 6.16.9, 6.17affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.