CVE-2024-35925: block: prevent division by zero in blk_rq_stat_sum()
In the Linux kernel, the following vulnerability has been resolved:
block: prevent division by zero in blk_rq_stat_sum()
The expression dst->nr_samples + src->nr_samples may
have zero value on overflow. It is necessary to add
a check to avoid division by zero.
Found by Linux Verification Center (linuxtesting.org) with Svace.
Security readout for executives and security teams
Plain-English summary
CVE-2024-35925 is a Linux kernel block-layer flaw where an internal statistics calculation can divide by zero after a counter overflow. The public record does not provide CVSS, CWE, or impact detail. Treat it as a kernel stability risk until your Linux distribution or appliance vendor confirms exposure and fix status.
Executive priority
Handle through normal kernel patch governance unless vendor advisories raise the severity for your environment. The evidence supports remediation tracking, but not emergency response based on active exploitation or public weaponization.
Technical view
The issue is in blk_rq_stat_sum(). The sum of dst->nr_samples and src->nr_samples can overflow to zero, leading to division by zero. The kernel stable references are fixes that add a guard for this condition. The CVE lists Linux kernel versions including 4.15 through 6.9 as affected context.
Likely exposure
Exposure is most likely on systems running affected Linux kernel builds or downstream kernels derived from them. The bundle names Linux as the affected product and includes Debian LTS advisories, so distribution-packaged kernels should be checked against vendor security updates.
Exploitation context
The bundle does not report active exploitation, and KEV status is false. No exploitability details, required privileges, attack vector, or trigger conditions are provided beyond the internal overflow-to-zero condition in kernel block request statistics.
Researcher notes
Evidence is limited to the CVE description, affected Linux version context, stable kernel fix references, and Debian LTS advisories. The bundle does not include CVSS, CWE, proof-of-concept status, or detailed reachability analysis, so exposure validation depends on kernel provenance and vendor backports.
Mitigation direction
Apply kernel updates from your Linux distribution or device vendor.
Prioritize internet-facing, multi-tenant, and high-availability Linux systems for kernel review.
Check Debian LTS advisories if managing Debian-based long-term-support hosts.
Track the referenced kernel stable commits for backport confirmation.
If no vendor fix is available, monitor vendor guidance before making operational changes.
Validation and detection
Inventory Linux kernel versions across servers, containers hosts, appliances, and embedded systems.
Compare running kernels against your vendor advisory and fixed package versions.
Confirm whether the referenced stable commits are present in custom kernels.
Review Debian LTS notices where Debian-based systems are in scope.
Document exceptions where vendors state the product is unaffected.
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-2024-35925 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.