LiveActive security incident?Get immediate response
CVE Record

CVE-2024-35787: md/md-bitmap: fix incorrect usage for sb_index

In the Linux kernel, the following vulnerability has been resolved: md/md-bitmap: fix incorrect usage for sb_index Commit d7038f951828 ("md-bitmap: don't use ->index for pages backing the bitmap file") removed page->index from bitmap code, but left wrong code logic for clustered-md. current code never set slot offset for cluster nodes, will sometimes cause crash in clustered env. Call trace (partly): md_bitmap_file_set_bit+0x110/0x1d8 [md_mod] md_bitmap_startwrite+0x13c/0x240 [md_mod] raid1_make_request+0x6b0/0x1c08 [raid1] md_handle_request+0x1dc/0x368 [md_mod] md_submit_bio+0x80/0xf8 [md_mod] __submit_bio+0x178/0x300 submit_bio_noacct_nocheck+0x11c/0x338 submit_bio_noacct+0x134/0x614 submit_bio+0x28/0xdc submit_bh_wbc+0x130/0x1cc submit_bh+0x1c/0x28

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux software RAID bitmap defect can sometimes crash systems using clustered multidisk configurations. The issue is local rather than remotely reachable and requires limited privileges, but disruption to clustered storage could affect critical services. The supplied CVSS 3.1 score is 7.8 (High).

Executive priority

Treat as a high-priority, targeted infrastructure issue rather than an internet-wide emergency. Identify clustered MD deployments promptly and schedule vendor-supported kernel updates, prioritizing storage nodes whose failure would interrupt critical services. There is no supplied evidence of active exploitation.

Technical view

Earlier bitmap changes removed reliance on page indexing but left incorrect sb_index handling for clustered MD. Cluster nodes consequently may not receive the required slot offset, and bitmap writes can trigger a kernel crash through the MD and RAID1 request path. The supplied record identifies fixes in four Linux stable commits.

Likely exposure

Exposure appears limited to Linux systems using clustered MD with bitmap-backed RAID. The bundle marks Linux 6.6, versions through 6.6.24, 6.7.12, 6.8.3, and 6.9 as affected, but its version data is ambiguous. Confirm exact distribution kernel status with the vendor.

Exploitation context

The CVSS vector indicates local access, low complexity, limited privileges, and no user interaction. CISA KEV status is false, and the supplied sources provide no evidence of active exploitation. The record demonstrates a crash condition, not a documented public exploitation method.

Researcher notes

The affected boundary is incompletely expressed: duplicate introducing commit entries and mixed version values prevent precise package-level conclusions. No CWE is assigned. Review the four stable commits and downstream backports to establish branch-specific exposure. The source record supports intermittent kernel crashing in clustered environments but does not establish additional exploitation outcomes.

Mitigation direction

  • Apply the distribution kernel update containing the applicable Linux stable fix.
  • Consult distribution advisories to confirm fixed package versions for each deployed kernel.
  • Prioritize clustered MD hosts supporting critical or highly available storage.
  • If patching is delayed, assess whether affected clustered MD configurations can be safely reduced or isolated.

Validation and detection

  • Inventory kernel versions on systems using clustered MD and RAID bitmaps.
  • Compare each distribution kernel build with its vendor advisory or backport status.
  • Confirm the applicable stable fix commit is included in deployed kernel source or package metadata.
  • After updating, verify systems boot normally and clustered RAID bitmap operations remain healthy.
Prepared
Confidence
medium
Sources
6

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-35787 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
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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.

1CVSS vectors
3Timeline events
2ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2024-35787Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxd7038f951828da19fa9aafddfa087b69032c9687, d7038f951828da19fa9aafddfa087b69032c9687, d7038f951828da19fa9aafddfa087b69032c9687, d7038f951828da19fa9aafddfa087b69032c9687unaffected
LinuxLinux6.6, 0, 6.6.24, 6.7.12, 6.8.3, 6.9affected
Weakness

CWE details

No CWE listed

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