data built 2026-10-19T13:16:53Z

Look up another CVE · open CVE-2025-39940 in the interactive tracker

CVE-2025-39940

dm-stripe: fix a possible integer overflow

EPSS 0.1%

Published 2025-10-04 (12 months ago) by the Linux kernel CNA. Subsystem drivers/md. Debian urgency: not yet assigned.

What to do, per Debian release

Debian's own status for CVE-2025-39940 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source

ReleaseStatus VersionWhat this means
Debian 12bookwormvulnerable6.1.190-1No fix published anywhere yet, neither in Debian nor upstream for the series bookworm tracks. Watch the Debian tracker page for this CVE. Advisories for bookworm have historically landed a median of 23 days after publication.
Debian 13trixiefixed6.12.57-1Update the kernel and reboot. Fixed in 6.12.57-1. A running kernel keeps the old code until the machine restarts.
Debian 14forkyfixed6.16.9-1Update the kernel and reboot. Fixed in 6.16.9-1. A running kernel keeps the old code until the machine restarts.
Debian unstablesidfixed6.16.9-1Update the kernel and reboot. Fixed in 6.16.9-1. A running kernel keeps the old code until the machine restarts.

The vulnerability

What the bug is

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;

Where it lives

The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.

drivers/md/dm-stripe.c

What this is
DEVICE-MAPPER (LVM)MAINTAINERS section matched on drivers/md/dm* · dm-devel@lists.linux.dev · Maintained
Kernel module
dm_mod

Check it on the machine

grep -wE 'CONFIG_BLK_DEV_DM|CONFIG_MD' /boot/config-$(uname -r)

Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.

lsmod | grep -w dm_mod

Prints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.

Show whether Debian builds this, per release

Debian builds this as a loadable module. Every release below compiles it as a module on every flavour, so whether the code is in the running kernel depends on whether that module is loaded.

  • bookworm, trixie, forky, sidm
m
a loadable module on every flavour - check lsmod, can be blacklisted
Build switches
CONFIG_BLK_DEV_DM, CONFIG_MD
Reads as
all on means the file is compiled; any one off means it is not.

From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages

Signals

Published
2025-10-04 (12 months ago)source
CVSS
no vector published, unrated
Attack vector
not published
EPSS
0.14%, higher than 3.2% of all CVEssource
CISA KEV
not listedthe KEV catalogue
Debian urgency
not yet assignedsource
Subsystem
drivers/md

Upstream fixes

The versions the CNA records as introducing and fixing this, and the commit for each. source

IntroducedFixed inCommit
2.6.316.12.49f8f64254bca5
2.6.316.16.9ee27658c239b
2.6.316.171071d560afb4

Why the CNA scored it this way

The kernel CNA published no CVSS vector and no reasoning for CVE-2025-39940, which is why it is shown as unrated rather than given an invented score. 6,405 of the 20,413 CVEs here carry reasoning; this is not one of them.