CVE-2025-23159 Details
Description
In the Linux kernel, the following vulnerability has been resolved: media: venus: hfi: add a check to handle OOB in sfr region sfr->buf_size is in shared memory and can be modified by malicious user. OOB write is possible when the size is made higher than actual sfr data buffer. Cap the size to allocated size for such cases.
An out-of-bounds write vulnerability has been identified in the Linux kernel's Venus media component, specifically within the HFI (Hardware Frame Interface) handling. The issue arises because the 'buf_size' parameter, located in shared memory, can be manipulated by a malicious user. This manipulation allows for an out-of-bounds write when the specified size exceeds the actual data buffer allocated for the SFR (Streaming Frame Rate) region. The vulnerability has been addressed by adding a check to ensure that the size does not exceed the allocated buffer capacity.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-787 | Out-of-bounds Write | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 4.13, < 5.4.293 >= 5.5, < 5.10.237 >= 5.11, < 5.15.181 >= 5.16, < 6.1.135 >= 6.2, < 6.6.88 >= 6.7, < 6.12.24 >= 6.13, < 6.13.12 >= 6.14, < 6.14.3 |
CPE
Remediation
| |
| debian debian linux | 11.0 |
CPE
Remediation
| |
Change History
6 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jul 30, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Nov 5, 2025 | Initial Analysis | [email protected] |
| Nov 3, 2025 | CVE Modified | CVE |
| May 2, 2025 | CVE Modified | kernel.org |
| May 1, 2025 | New CVE Received | kernel.org |