CVE-2026-97910ASoC: sprd: validate compress buffer sizes against fixed allocations
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
In the Linux kernel, the following vulnerability has been resolved: ASoC: sprd: validate compress buffer sizes against fixed allocations sprd_platform_compr_open() allocates the stage 0 IRAM buffer (32K data area) and the stage 1 DDR buffer (2M data area) with fixed sizes, but sprd_platform_compr_copy() derives all copy lengths from the user controlled runtime->fragment_size and the write() count, never comparing them against the physical buffer sizes. The compress core only checks fragment_size * fragments for an u32 overflow in snd_compress_check_input(), so a local user can configure a logical buffer of up to ~4GB via SNDRV_COMPRESS_SET_PARAMS, far exceeding the fixed allocations. A fragment_size larger than the 32K IRAM data area makes the stage 0 copy_from_user() overflow past the IRAM allocation, and a buffer_size larger than the 2M DDR buffer makes the wrapping copy at the end of sprd_platform_compr_copy() write fully user controlled data past the buffer. No SNDRV_PCM_TRIGGER_START is needed, a write() in SETUP state reaches the copy callback directly. Reject parameters that do not fit into the fixed buffers in set_params(), and fix the advertised max fragment size: 128K never fitted into the 32K IRAM buffer. The caps values may have been carried over from the qdsp6 driver, which allocates its buffers according to the advertised maxima, unlike this driver. With 32K as max fragment size the advertised limits are self-consistent: 32K * 64 = 2M equals the DDR buffer size. Discovered by Atuin - Automated Vulnerability Discovery Engine.
- CVSS
- 7.8 HIGH (v3.1, CNA)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Oct 19, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from cce1396936ef2b347d622b4d49718818eb32029d before 2fada8276117215407afd1f59de5d2fe22aff01f; from cce1396936ef2b347d622b4d49718818eb32029d before ad796a1bc1875da2ebb616ea9bc1f2994273fd02; from cce1396936ef2b347d622b4d49718818eb32029d before 2e27144ba4b98bb3eb14aaccd4b088e2e69844e3; from cce1396936ef2b347d622b4d49718818eb32029d before 1467e3989c6edf79d3898c78aa47027f31ee5acb; from cce1396936ef2b347d622b4d49718818eb32029d before 38a9bb5221bcdece5507299f739c6751d8fc16b2; from cce1396936ef2b347d622b4d49718818eb32029d before ff63b0adc4f6a5b61c8393d204fac44c594c4d39; from cce1396936ef2b347d622b4d49718818eb32029d before 8064b73997f137c00a7e2e38295a763f9423928b; from cce1396936ef2b347d622b4d49718818eb32029d before 7a4ce92d150b9e7ecf1a710a34d8cdeb590d3751 | CNA record |
References
- https://git.kernel.org/stable/c/2fada8276117215407afd1f59de5d2fe22aff01f
- https://git.kernel.org/stable/c/ad796a1bc1875da2ebb616ea9bc1f2994273fd02
- https://git.kernel.org/stable/c/2e27144ba4b98bb3eb14aaccd4b088e2e69844e3
- https://git.kernel.org/stable/c/1467e3989c6edf79d3898c78aa47027f31ee5acb
- https://git.kernel.org/stable/c/38a9bb5221bcdece5507299f739c6751d8fc16b2
- https://git.kernel.org/stable/c/ff63b0adc4f6a5b61c8393d204fac44c594c4d39
- https://git.kernel.org/stable/c/8064b73997f137c00a7e2e38295a763f9423928b
- https://git.kernel.org/stable/c/7a4ce92d150b9e7ecf1a710a34d8cdeb590d3751
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.