[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025041602-CVE-2025-22049-4f6b@gregkh>
Date: Wed, 16 Apr 2025 16:12:20 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2025-22049: LoongArch: Increase ARCH_DMA_MINALIGN up to 16
Description
===========
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.
The Linux kernel CVE team has assigned CVE-2025-22049 to this issue.
Affected and fixed versions
===========================
Fixed in 6.1.134 with commit f39af67f03b564b763b06e44cb960c10a382d54a
Fixed in 6.6.87 with commit 279ec25c2df49fba1cd9488f2ddd045d9cb2112e
Fixed in 6.12.23 with commit 1d0def2d1658666ec1f32c9495df60e7411e3c82
Fixed in 6.13.11 with commit bfff341cac7c650e6ca8d10503725992f5564d0f
Fixed in 6.14.2 with commit 8b82aea3666f8f2c78f86148d78aea99c46e0f82
Fixed in 6.15-rc1 with commit 4103cfe9dcb88010ae4911d3ff417457d1b6a720
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2025-22049
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
arch/loongarch/include/asm/cache.h
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/f39af67f03b564b763b06e44cb960c10a382d54a
https://git.kernel.org/stable/c/279ec25c2df49fba1cd9488f2ddd045d9cb2112e
https://git.kernel.org/stable/c/1d0def2d1658666ec1f32c9495df60e7411e3c82
https://git.kernel.org/stable/c/bfff341cac7c650e6ca8d10503725992f5564d0f
https://git.kernel.org/stable/c/8b82aea3666f8f2c78f86148d78aea99c46e0f82
https://git.kernel.org/stable/c/4103cfe9dcb88010ae4911d3ff417457d1b6a720
Powered by blists - more mailing lists