---
id: CVE-2026-93074
title: |-
  In the Linux kernel, the following vulnerability has been resolved:

  dax/fsdev: use __va(phys) for kaddr in direct_access

  Use __va(phys) instead of virt_addr + linear_offset for the kaddr
  return in __fsdev_dax_direct_access()
summary: |-
  In the Linux kernel, the following vulnerability has been resolved:

  dax/fsdev: use __va(phys) for kaddr in direct_access

  Use __va(phys) instead of virt_addr + linear_offset for the kaddr
  return in __fsdev_dax_direct_access(). The previ…
severity: high
cvss: 7.8
cvssVector: 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= 759455848df0b9ac3acabdbedcdc4a55af67935f <
    7b642bd3d39105eef4d5908970726c5fda291b53
  - >-
    Linux >= 759455848df0b9ac3acabdbedcdc4a55af67935f <
    ff7c73fca793bd5c29a15ba735b0886f62f3a840
  - Linux 7.1
published: '2026-09-17'
updated: '2026-09-18'
sourceUpdated: '2026-09-18T18:18:20.197'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-93074'
references:
  - url: 'https://git.kernel.org/stable/c/7b642bd3d39105eef4d5908970726c5fda291b53'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/ff7c73fca793bd5c29a15ba735b0886f62f3a840'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
tags:
  - nvd
  - cve.org
epss: 0.00129
epssPercentile: 0.02925
ingestedAt: '2026-09-17T16:21:47.763Z'
---

## Overview

In the Linux kernel, the following vulnerability has been resolved:

dax/fsdev: use __va(phys) for kaddr in direct_access

Use __va(phys) instead of virt_addr + linear_offset for the kaddr
return in __fsdev_dax_direct_access(). The previous code added a
device-linear byte offset to virt_addr (which is __va of ranges[0]),
but for multi-range devices with physical gaps between ranges, this
linear arithmetic crosses the gap and produces a wrong kernel virtual
address. Using __va(phys) where phys comes from dax_pgoff_to_phys()
is correct for any range layout because the direct map translates
each physical address independently.

This leaves dev_dax->virt_addr write-only, so remove the field
(suggested by Dave Jiang).

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
