LiveActive security incident?Get immediate response
CVE Record

CVE-2024-57875: block: RCU protect disk->conv_zones_bitmap

In the Linux kernel, the following vulnerability has been resolved: block: RCU protect disk->conv_zones_bitmap Ensure that a disk revalidation changing the conventional zones bitmap of a disk does not cause invalid memory references when using the disk_zone_is_conv() helper by RCU protecting the disk->conv_zones_bitmap pointer. disk_zone_is_conv() is modified to operate under the RCU read lock and the function disk_set_conv_zones_bitmap() is added to update a disk conv_zones_bitmap pointer using rcu_replace_pointer() with the disk zone_wplugs_lock spinlock held. disk_free_zone_resources() is modified to call disk_update_zone_resources() with a NULL bitmap pointer to free the disk conv_zones_bitmap. disk_set_conv_zones_bitmap() is also used in disk_update_zone_resources() to set the new (revalidated) bitmap and free the old one.

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux kernel race can leave code reading an obsolete conventional-zones bitmap while a disk is being revalidated, causing invalid memory access. A local, low-privileged attacker may be able to affect confidentiality, integrity, or availability, although the supplied sources do not describe a practical exploit.

Executive priority

Treat as a high-priority kernel maintenance issue, especially on multi-user or zoned-storage systems. Schedule prompt patching through normal change controls. Emergency isolation is not supported by the supplied evidence because active exploitation is unconfirmed and exploitation requires local access.

Technical view

The block layer did not safely synchronize access to disk->conv_zones_bitmap during disk revalidation. The fix places disk_zone_is_conv() reads under RCU protection and replaces or frees the bitmap through a locked RCU-aware update path, preventing readers from dereferencing retired memory.

Likely exposure

The bundle marks Linux kernel versions including 6.10, 6.12.5, and 6.13 as affected; its additional version value "0" is ambiguous. Risk is most relevant where zoned block-device functionality and disk revalidation are exercised. Confirm exposure against distribution advisories and backport records.

Exploitation context

The CVSS 3.1 vector is 7.8 and requires local access, low privileges, low complexity, and no user interaction. The CVE is not listed as KEV in the supplied bundle, and no provided source reports active exploitation or a public proof of concept.

Researcher notes

The defect is a lifetime race around replacement and freeing of disk->conv_zones_bitmap. The remediation uses RCU read-side protection, rcu_replace_pointer(), and zone_wplugs_lock. The bundle does not identify vulnerable configurations, triggering operations beyond revalidation, confirmed impacts, or precise distribution package ranges.

Mitigation direction

  • Install a vendor-supported kernel package containing the CVE fix or an equivalent backport.
  • Compare vendor patch notes with the two supplied stable-kernel fix commits.
  • Prioritize systems using zoned block devices or permitting untrusted local users.
  • If updates are unavailable, obtain mitigation guidance from the Linux distribution vendor.

Validation and detection

  • Record each system's running kernel and distribution package version.
  • Check distribution advisories and changelogs for CVE-2024-57875 or equivalent backports.
  • Determine whether affected systems use zoned block-device functionality.
  • Verify the updated kernel is running after remediation, not merely installed.
Prepared
Confidence
high
Sources
4

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-2024-57875 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
0ADP providers
3Source links

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-57875Attack 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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxdd291d77cc90eb6a86e9860ba8e6e38eebd57d12, dd291d77cc90eb6a86e9860ba8e6e38eebd57d12unaffected
LinuxLinux6.10, 0, 6.12.5, 6.13affected
Weakness

CWE details

No CWE listed

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