LiveActive security incident?Get immediate response
CVE Record

CVE-2024-38663: blk-cgroup: fix list corruption from resetting io stat

In the Linux kernel, the following vulnerability has been resolved: blk-cgroup: fix list corruption from resetting io stat Since commit 3b8cc6298724 ("blk-cgroup: Optimize blkcg_rstat_flush()"), each iostat instance is added to blkcg percpu list, so blkcg_reset_stats() can't reset the stat instance by memset(), otherwise the llist may be corrupted. Fix the issue by only resetting the counter part.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can corrupt an internal block I/O accounting list when statistics are reset. The public sources do not describe remote attack paths, business impact, or exploitation. Treat it as a kernel integrity issue that should be handled through normal kernel patch governance, especially on systems using cgroups or block I/O accounting.

Executive priority

Handle through routine to elevated kernel patching, not emergency response, unless your vendor rates it higher for your environment. The main uncertainty is impact: sources confirm a kernel bug fix but do not establish severity, exploitability, or active abuse.

Technical view

CVE-2024-38663 fixes blk-cgroup list corruption introduced after commit 3b8cc6298724 optimized blkcg_rstat_flush(). blkcg_reset_stats() used memset() on iostat instances that are now linked into a blkcg per-CPU list, risking llist corruption. The fix resets only counter fields instead of the full structure.

Likely exposure

Exposure is limited to Linux kernels containing the affected blk-cgroup change and lacking the referenced stable fixes. The provided affected-version data is incomplete and ambiguous, so validate against distribution kernel advisories and package changelogs rather than assuming exact upstream version boundaries.

Exploitation context

No active exploitation is supported by the provided sources, and the CVE is not listed as KEV. The bundle provides no exploitability assessment, CVSS score, privilege requirements, or proof-of-concept details. Do not infer exploitation from the existence of kernel fix commits alone.

Researcher notes

The key code behavior is structural: iostat objects became members of blkcg per-CPU llist state, so full memset during stat reset could corrupt list pointers. Analysis should focus on kernel versions carrying commit 3b8cc6298724 without the stable patches.

Mitigation direction

  • Check Linux distribution advisories for CVE-2024-38663 coverage.
  • Upgrade to a vendor kernel containing the referenced stable fixes.
  • Prioritize hosts using cgroups, containers, or block I/O accounting.
  • Schedule reboots where required for kernel update activation.
  • Monitor vendor guidance for corrected affected-version statements.

Validation and detection

  • Inventory running kernel versions across Linux assets.
  • Map installed kernel packages to vendor CVE advisories.
  • Confirm the blk-cgroup fix is present in source or package changelogs.
  • Identify workloads using cgroups or block I/O accounting.
  • Review kernel logs for related list corruption symptoms.
Prepared
Confidence
medium
Sources
5

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-38663 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
3Timeline events
2ADP providers
4Source links

SSVC decision data

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

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
LinuxLinux3b8cc6298724021da845f2f9fd7dd4b6829a6817, 3b8cc6298724021da845f2f9fd7dd4b6829a6817, 3b8cc6298724021da845f2f9fd7dd4b6829a6817unaffected
LinuxLinux6.2, 0, 6.6.33, 6.9.4, 6.10affected
Weakness

CWE details

No CWE listed

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