LiveActive security incident?Get immediate response
CVE Record

CVE-2024-38604: block: refine the EOF check in blkdev_iomap_begin

In the Linux kernel, the following vulnerability has been resolved: block: refine the EOF check in blkdev_iomap_begin blkdev_iomap_begin rounds down the offset to the logical block size before stashing it in iomap->offset and checking that it still is inside the inode size. Check the i_size check to the raw pos value so that we don't try a zero size write if iter->pos is unaligned.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2024-38604 is a Linux kernel block-layer bug involving how an end-of-file boundary is checked for unaligned block-device writes. The public record does not state business impact, CVSS, or exploitation. Treat it as a kernel maintenance issue requiring vendor update tracking, not as confirmed active exploitation.

Executive priority

Set priority based on Linux estate exposure and patch windows. There is not enough source evidence to justify emergency response, but kernel vulnerabilities should be handled through normal security update processes and tracked to completion.

Technical view

In blkdev_iomap_begin, the code rounded the offset down to logical block size before storing iomap->offset and checking inode size. The fix checks the raw pos value against i_size, avoiding a zero-size write path when iter->pos is unaligned.

Likely exposure

Exposure is limited to systems running affected Linux kernel builds. The source lists Linux kernel version markers including 6.6, 6.6.33, 6.8.12, 6.9.3, and 6.10. Exact exposure depends on distribution backports and kernel packaging.

Exploitation context

The bundle shows KEV is false and provides no cited evidence of active exploitation, public exploit availability, attack vector, or privilege requirements. Do not classify this as exploited in the wild from these sources alone.

Researcher notes

The key code issue is an EOF check using a rounded-down offset instead of raw pos. The record does not provide CVSS, CWE, crash details, privilege boundaries, or a reproducer, so impact analysis remains constrained.

Mitigation direction

  • Apply Linux vendor kernel updates that include the referenced stable fixes.
  • Check distribution advisories for CVE-2024-38604 backport status.
  • Prioritize systems running affected kernel branches or custom kernels.
  • Avoid direct wrangler or deployment assumptions; this is kernel-side remediation.
  • If patch timing is unclear, request vendor guidance before declaring risk closed.

Validation and detection

  • Inventory running kernel versions across Linux hosts.
  • Map each kernel package to vendor advisories for CVE-2024-38604.
  • Confirm whether referenced stable commits are included or backported.
  • Document any systems awaiting kernel updates and reboot completion.
  • Verify post-update kernel version after reboot.
Prepared
Confidence
medium
Sources
6

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-38604 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
5Source 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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux487c607df790d366e67a7d6a30adf785cdd98e55, 487c607df790d366e67a7d6a30adf785cdd98e55, 487c607df790d366e67a7d6a30adf785cdd98e55, 487c607df790d366e67a7d6a30adf785cdd98e55unaffected
LinuxLinux6.6, 0, 6.6.33, 6.8.12, 6.9.3, 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.