LiveActive security incident?Get immediate response
CVE Record

CVE-2025-71195: dmaengine: xilinx: xdma: Fix regmap max_register

In the Linux kernel, the following vulnerability has been resolved: dmaengine: xilinx: xdma: Fix regmap max_register The max_register field is assigned the size of the register memory region instead of the offset of the last register. The result is that reading from the regmap via debugfs can cause a segmentation fault: tail /sys/kernel/debug/regmap/xdma.1.auto/registers Unable to handle kernel paging request at virtual address ffff800082f70000 Mem abort info: ESR = 0x0000000096000007 EC = 0x25: DABT (current EL), IL = 32 bits SET = 0, FnV = 0 EA = 0, S1PTW = 0 FSC = 0x07: level 3 translation fault [...] Call trace: regmap_mmio_read32le+0x10/0x30 _regmap_bus_reg_read+0x74/0xc0 _regmap_read+0x68/0x198 regmap_read+0x54/0x88 regmap_read_debugfs+0x140/0x380 regmap_map_read_file+0x30/0x48 full_proxy_read+0x68/0xc8 vfs_read+0xcc/0x310 ksys_read+0x7c/0x120 __arm64_sys_read+0x24/0x40 invoke_syscall.constprop.0+0x64/0x108 do_el0_svc+0xb0/0xd8 el0_svc+0x38/0x130 el0t_64_sync_handler+0x120/0x138 el0t_64_sync+0x194/0x198 Code: aa1e03e9 d503201f f9400000 8b214000 (b9400000) ---[ end trace 0000000000000000 ]--- note: tail[1217] exited with irqs disabled note: tail[1217] exited with preempt_count 1 Segmentation fault

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can crash a system path when the Xilinx XDMA driver exposes registers through debugfs. The bug is a bounds mistake: the driver treats a memory-region size as the last valid register offset. Business impact is mainly local denial of service on systems using this driver, not confirmed data theft or remote compromise.

Executive priority

Prioritize as a controlled maintenance fix for exposed Linux systems using Xilinx XDMA. Escalate if those systems are production-critical, multi-user, or allow broad local shell access. Current evidence supports denial-of-service risk, not active exploitation or remote compromise.

Technical view

In dmaengine/xilinx/xdma, regmap max_register is set incorrectly. A debugfs regmap read can reach past the mapped MMIO register area and trigger a kernel paging fault, as shown by the supplied crash trace in regmap_mmio_read32le and regmap_read_debugfs.

Likely exposure

Exposure appears limited to Linux systems running affected kernels with the Xilinx XDMA driver present and its regmap debugfs interface accessible. The source bundle does not identify specific distributions, hardware products, or cloud images beyond Linux kernel versions and stable kernel commits.

Exploitation context

The bundle shows a local debugfs read causing a crash. It does not cite CISA KEV listing, active exploitation, remote reachability, privilege escalation, or public weaponization. Treat exploitation status as unconfirmed beyond the demonstrated crash condition.

Researcher notes

The root cause is an off-by-boundary register range definition in regmap configuration. The record supplies crash evidence and stable commit references, but no CVSS, CWE, distribution mapping, exploit maturity, or fixed package versions. Avoid broader impact claims without vendor advisories.

Mitigation direction

  • Apply vendor or stable-kernel updates containing the referenced fixes.
  • Check Linux distribution advisories for packaged kernel availability.
  • Restrict or disable debugfs access on affected systems where operationally possible.
  • Prioritize systems using Xilinx XDMA hardware or driver modules.
  • Monitor vendor guidance for corrected affected-version mapping.

Validation and detection

  • Inventory kernels and confirm whether the xdma driver is present.
  • Check whether debugfs is mounted and accessible on production systems.
  • Compare installed kernel sources or packages with referenced stable fixes.
  • Review logs for kernel paging faults involving regmap or xdma.
  • Validate remediation in staging before production kernel rollout.
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-2025-71195 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
0ADP providers
5Source links

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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux17ce252266c7f016ece026492c45838f852ddc79, 17ce252266c7f016ece026492c45838f852ddc79, 17ce252266c7f016ece026492c45838f852ddc79, 17ce252266c7f016ece026492c45838f852ddc79unaffected
LinuxLinux6.3, 0, 6.6.122, 6.12.67, 6.18.7, 6.19affected
Weakness

CWE details

No CWE listed

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