Skip to main content
VulnerabilityPublished Updated

CVE-2024-50250: Linux kernel · fsdax: dax_unshare_iter needs to copy entire blocks

Source GCVE Database

0
Compare

Not known to be exploited · CVSS 7.1 High.

Data as of 29 Oct 2026, 23:00 UTC

CVSS 3.1 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Nov 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

AI-suggested

A fix has been implemented in the Linux kernel to address this issue by aligning copy operations to page boundaries and adding calls to invalidate inode page ranges after unshare operations. Users and administrators should apply the official kernel updates that include this fix. Since this is not a cloud service, manual patching is required. Patch status is confirmed by the vendor advisory indicating resolution. No additional mitigations are specified beyond applying the patch.

Description

CVE-2024-50250 is a high-severity vulnerability in the Linux kernel's fsdax subsystem involving the dax_unshare_iter function. The flaw causes improper copying of data blocks when file positions and lengths are not aligned to fsblock boundaries, leading to data corruption and exposure of stale persistent memory contents. The issue arises because dax_iomap_direct_access returns pointers to the start of pages regardless of the requested position, causing misaligned copying and partial block updates. Additionally, the lack of invalidation of inode pages after unsharing can cause processes to access outdated memory mappings. The vulnerability has been resolved by ensuring copy operations are aligned to page boundaries and addressing the missing invalidation step.

References

Community reviews

Loading reviews…