CVE-2025-71195
Segmentation Fault in Linux dmaengine xdma regmap DebugFS
Publication date: 2026-02-04
Last updated on: 2026-02-04
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| xilinx | xdma | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the Linux kernel's dmaengine driver for Xilinx xdma devices. The issue is that the max_register field is incorrectly assigned the size of the register memory region instead of the offset of the last register.
Because of this incorrect assignment, when reading from the regmap via debugfs, it can cause a segmentation fault, leading to a kernel crash or instability.
How can this vulnerability impact me? :
The vulnerability can cause a segmentation fault when accessing the regmap registers through debugfs, which can lead to a kernel crash or system instability.
This may result in denial of service conditions on affected systems using the Xilinx xdma driver, potentially disrupting normal operations.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by attempting to read the regmap registers via debugfs for the xilinx xdma device. Specifically, running the command to read the registers file under /sys/kernel/debug/regmap/xdma.1.auto/registers may trigger the issue.
- Use the command: tail /sys/kernel/debug/regmap/xdma.1.auto/registers
If the vulnerability is present, this command may cause a segmentation fault with kernel paging request errors and a kernel trace similar to the one described in the CVE.
What immediate steps should I take to mitigate this vulnerability?
I don't know