Reference page — cumulative record through Wednesday, August 19, 2026 UTC. Reference pages update as the archive grows; only dated daily editions are immutable pages of record.
Linux Linux — fsdax: dax_unshare_iter needs to copy entire blocks
AV AC PR UI S C I A CVSS EPSS %ile KEV
L L L N U H H N 7.1 .0023 13.9 —
AFFECTED
Product Versions Fixed
Linux 1bec6782a25c9b92c203ea7a1b3e3dc6a468cbc4 – —
Linux 6.2 – 6.1.116
TIMELINE
Oct 21 Reserved by Linux
Nov 9 Published (CNA: Linux)
Aug 4 RESCORED — CVE-2024-50250 (Linux). CVSS 7.8 → 7.1 (NVD).
Description
In the Linux kernel, the following vulnerability has been resolved:
fsdax: dax_unshare_iter needs to copy entire blocks
The code that copies data from srcmap to iomap in dax_unshare_iter is
very very broken, which bfoster's recent fsx changes have exposed.
If the pos and len passed to dax_file_unshare are not aligned to an
fsblock boundary, the iter pos and length in the _iter function will
reflect this unalignment.
dax_iomap_direct_access always returns a pointer to the start of the
kmapped fsdax page, even if its pos argument is in the middle of that
page. This is catastrophic for data integrity when iter->pos is not
aligned to a page, because daddr/saddr do not point to the same byte in
the file as iter->pos. Hence we corrupt user data by copying it to the
wrong place.
If iter->pos + iomap_length() in the _iter function not aligned to a
page, then we fail to copy a full block, and only partially populate the
destination block. This is catastrophic for data confidentiality
because we expose stale pmem contents.
Fix both of these issues by aligning copy_pos/copy_len to a page
boundary (remember, this is fsdax so 1 fsblock == 1 base page) so that
we always copy full blocks.
We're not done yet -- there's no call to invalidate_inode_pages2_range,
so programs that have the file range mmap'd will continue accessing the
old memory mapping after the file metadata updates have completed.
Be careful with the return value -- if the unshare succeeds, we still
need to return the number of bytes that the iomap iter thinks we're
operating on.
Lifecycle
Complete event history — 3 events, chronological
| Date | Event | Detail |
| October 21, 2024 | Reserved | Reserved by Linux |
| November 9, 2024 | Published | Published (CNA: Linux) |
| August 4, 2026 | RESCORED | RESCORED — CVE-2024-50250 (Linux). CVSS 7.8 → 7.1 (NVD). |
Affected
Affected products and packages — 2 rows
| Vendor | Product / Package | Ecosystem | Version introduced | Fixed |
| Linux | Linux | — | 1bec6782a25c9b92c203ea7a1b3e3dc6a468cbc4 | — |
| Linux | Linux | — | 6.2 | 6.1.116 |
About this page
This is a reference page, not a dated page of record. It assembles the complete lifecycle of CVE-2024-50250 from the CVE Program record, NVD enrichment, the CISA KEV catalog, EPSS, and OSV advisories. The box score's numbers (CVSS, EPSS, KEV status) are current as of Wednesday, August 19, 2026 UTC and are re-derived as the archive grows; only dated daily editions are immutable pages of record. The authoritative source for this identifier is cve.org.