CVE-2025-22049
What it is
In the Linux kernel, the following vulnerability has been resolved: LoongArch: Increase ARCH_DMA_MINALIGN up to 16 ARCH_DMA_MINALIGN is 1 by default, but some LoongArch-specific devices (such as APBDMA) require 16 bytes alignment. When the data buffer length is too small, the hardware may make an error writing cacheline. Thus, it is dangerous to allocate a small memory buffer for DMA. It's always safe to define ARCH_DMA_MINALIGN as L1_CACHE_BYTES but unnecessary (kmalloc() need small memory objects). Therefore, just increase it to 16.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: 7.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Record status
- Modified
Affected
- Linux Kernel < 6.1.134
- Linux Kernel < 6.6.87
- Linux Kernel < 6.12.23
- Linux Kernel < 6.13.11
- Linux Kernel < 6.14.2
Attack profile CVSS 3.1 · 7.8
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2025-22049.md and follow it. Check whether this project is affected by CVE-2025-22049. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/1d0def2d1658666ec1f32c9495df60e7411e3c82
- https://git.kernel.org/stable/c/279ec25c2df49fba1cd9488f2ddd045d9cb2112e
- https://git.kernel.org/stable/c/4103cfe9dcb88010ae4911d3ff417457d1b6a720
- https://git.kernel.org/stable/c/8b82aea3666f8f2c78f86148d78aea99c46e0f82
- https://git.kernel.org/stable/c/bfff341cac7c650e6ca8d10503725992f5564d0f
- https://git.kernel.org/stable/c/f39af67f03b564b763b06e44cb960c10a382d54a
References
- https://git.kernel.org/stable/c/1d0def2d1658666ec1f32c9495df60e7411e3c82
- https://git.kernel.org/stable/c/279ec25c2df49fba1cd9488f2ddd045d9cb2112e
- https://git.kernel.org/stable/c/4103cfe9dcb88010ae4911d3ff417457d1b6a720
- https://git.kernel.org/stable/c/8b82aea3666f8f2c78f86148d78aea99c46e0f82
- https://git.kernel.org/stable/c/bfff341cac7c650e6ca8d10503725992f5564d0f
- https://git.kernel.org/stable/c/f39af67f03b564b763b06e44cb960c10a382d54a
- https://lists.debian.org/debian-lts-announce/2025/05/msg00045.html