In the Linux kernel, the following vulnerability has been resolved:
dm-integrity: Avoid divide by zero in table status in Inline mode
In Inline mode, the journal is unused, and journal_sectors is zero.
Calculating the journal watermark requires dividing by journal_sectors, which should be done only if the journal is configured.
Otherwise, a simple table query (dmsetup table) can cause OOPS.
This bug did not show on some systems, perhaps only due to compiler optimization.
On my 32-bit testing machine, this reliably crashes with the following:
: Oops: divide error: 0000 [#1] PREEMPT SMP : CPU: 0 UID: 0 PID: 2450 Comm: dmsetup Not tainted 6.14.0-rc2+ #959 : EIP: dmintegritystatus+0x2f8/0xab0 [dm_integrity] ...
[
{
"signature_type": "Function",
"deprecated": false,
"digest": {
"length": 4220.0,
"function_hash": "277467431219640690907589682232605333299"
},
"signature_version": "v1",
"source": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git@06d9895f265282e939a8933bb18de82eba2b4dda",
"target": {
"file": "drivers/md/dm-integrity.c",
"function": "dm_integrity_status"
},
"id": "CVE-2025-21874-3aecbbd2"
},
{
"signature_type": "Line",
"deprecated": false,
"digest": {
"line_hashes": [
"308713468096852423892379153026048751750",
"216851023026917724919811382121637307967",
"33366720989713732204722929490141970686",
"321886388463027330063442485511478167589",
"23249630846692683988826481666460529624",
"222706648543472188919583656765426728790",
"147440551330044093064702032843972270802",
"57426014117957108704803381691784296333",
"207181574259721814608558494085236924761",
"198395002344503848355176333678340658738"
],
"threshold": 0.9
},
"signature_version": "v1",
"source": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git@06d9895f265282e939a8933bb18de82eba2b4dda",
"target": {
"file": "drivers/md/dm-integrity.c"
},
"id": "CVE-2025-21874-43944d40"
}
]