Linux: Out-of-bounds Read
CVE-2025-71101 is a high-severity out-of-bounds read vulnerability in Linux, with a CVSS 3.1 base score of 7.1 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists versions cf7ae870560b988247a4bbbe5399edd326632680, db4c26adf7117b1a4431d1197ae7109fee3230ad, 79cab730dbaaac03b946c7f5681bd08c986e2abd as the first without the flaw, so updating Linux to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.14% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Linux to cf7ae870560b988247a4bbbe5399edd326632680 or db4c26adf7117b1a4431d1197ae7109fee3230ad or 79cab730dbaaac03b946c7f5681bd08c986e2abd or e44c42c830b7ab36e3a3a86321c619f24def5206, whichever matches your release line, or a later version.
- Update Linux Kernel to 6.6.120 or 6.12.64 or 6.18.4, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | e6c7b3e15559699a30646dd45195549c7db447bd up to, but not including, cf7ae870560b988247a4bbbe5399edd326632680; e6c7b3e15559699a30646dd45195549c7db447bd up to, but not including, db4c26adf7117b1a4431d1197ae7109fee3230ad; e6c7b3e15559699a30646dd45195549c7db447bd up to, but not including, 79cab730dbaaac03b946c7f5681bd08c986e2abd; e6c7b3e15559699a30646dd45195549c7db447bd up to, but not including, e44c42c830b7ab36e3a3a86321c619f24def5206; 6.6 | cf7ae870560b988247a4bbbe5399edd326632680, db4c26adf7117b1a4431d1197ae7109fee3230ad, 79cab730dbaaac03b946c7f5681bd08c986e2abd, e44c42c830b7ab36e3a3a86321c619f24def5206 |
| Linux | Linux Kernel | 6.6.1 up to, but not including, 6.6.120; 6.7 up to, but not including, 6.12.64; 6.13 up to, but not including, 6.18.4; 6.6; 6.19 | 6.6.120, 6.12.64, 6.18.4 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- NoneNothing can be modified.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.1 | High | CNA |
| CVSS 3.1 | 7.1 | High | NVD |
Official description
In the Linux kernel, the following vulnerability has been resolved: platform/x86: hp-bioscfg: Fix out-of-bounds array access in ACPI package parsing The hp_populate_*_elements_from_package() functions in the hp-bioscfg driver contain out-of-bounds array access vulnerabilities. These functions parse ACPI packages into internal data structures using a for loop with index variable 'elem' that iterates through enum_obj/integer_obj/order_obj/password_obj/string_obj arrays. When processing multi-element fields like PREREQUISITES and ENUM_POSSIBLE_VALUES, these functions read multiple consecutive array elements using expressions like 'enum_obj[elem + reqs]' and 'enum_obj[elem + pos_values]' within nested loops. The bug is that the bounds check only validated elem, but did not consider the additional offset when accessing elem + reqs or elem + pos_values. The fix changes the bounds check to validate the actual accessed index.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Out-of-bounds Read
The product reads data past the end, or before the beginning, of the intended buffer.
How developers prevent this class of flaw
- Use a language that provides appropriate memory abstractions.
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Recent Out-of-bounds Read vulnerabilities
- 7.5 High severity
- 7.1 High severity
- 7.8 High severity
- 9.8 Critical severity
- 7.1 High severity
- 7.8 High severity
Spotted an error? Tell us.