Linux: Out-of-bounds Read
CVE-2022-49551 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 bf2558bbdce3ab1d6bcba09f354914e4515d0a2b, 47d39cb57e8669e507d17d9e0d067d2b3e3a87ae, 463bddd3ff1acf4036ddb80c34a715eb99debf46 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.27% 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 bf2558bbdce3ab1d6bcba09f354914e4515d0a2b or 47d39cb57e8669e507d17d9e0d067d2b3e3a87ae or 463bddd3ff1acf4036ddb80c34a715eb99debf46 or 26ae2c942b5702f2e43d36b2a4389cfb7d616b6a, whichever matches your release line, or a later version.
- Update Linux Kernel to 5.15.46 or 5.17.14 or 5.18.3, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 1da9e1c06873350c99ba49a052f92de85f2c69f2 up to, but not including, bf2558bbdce3ab1d6bcba09f354914e4515d0a2b; 1da9e1c06873350c99ba49a052f92de85f2c69f2 up to, but not including, 47d39cb57e8669e507d17d9e0d067d2b3e3a87ae; 1da9e1c06873350c99ba49a052f92de85f2c69f2 up to, but not including, 463bddd3ff1acf4036ddb80c34a715eb99debf46; 1da9e1c06873350c99ba49a052f92de85f2c69f2 up to, but not including, 26ae2c942b5702f2e43d36b2a4389cfb7d616b6a; 5.14 | bf2558bbdce3ab1d6bcba09f354914e4515d0a2b, 47d39cb57e8669e507d17d9e0d067d2b3e3a87ae, 463bddd3ff1acf4036ddb80c34a715eb99debf46, 26ae2c942b5702f2e43d36b2a4389cfb7d616b6a |
| Linux | Linux Kernel | 5.14 up to, but not including, 5.15.46; 5.16 up to, but not including, 5.17.14; 5.18 up to, but not including, 5.18.3 | 5.15.46, 5.17.14, 5.18.3 |
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 | NVD |
| CVSS 3.1 | 7.1 | High | CISA (ADP) |
Official description
In the Linux kernel, the following vulnerability has been resolved: usb: isp1760: Fix out-of-bounds array access Running the driver through kasan gives an interesting splat: BUG: KASAN: global-out-of-bounds in isp1760_register+0x180/0x70c Read of size 20 at addr f1db2e64 by task swapper/0/1 (...) isp1760_register from isp1760_plat_probe+0x1d8/0x220 (...) This happens because the loop reading the regmap fields for the different ISP1760 variants look like this: for (i = 0; i < HC_FIELD_MAX; i++) { ... } Meaning it expects the arrays to be at least HC_FIELD_MAX - 1 long. However the arrays isp1760_hc_reg_fields[], isp1763_hc_reg_fields[], isp1763_hc_volatile_ranges[] and isp1763_dc_volatile_ranges[] are dynamically sized during compilation. Fix this by putting an empty assignment to the [HC_FIELD_MAX] and [DC_FIELD_MAX] array member at the end of each array. This will make the array one member longer than it needs to be, but avoids the risk of overwriting whatever is inside [HC_FIELD_MAX - 1] and is simple and intuitive to read. Also add comments explaining what is going on.
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.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Recent Out-of-bounds Read vulnerabilities
- 7.1 High severity
- 7.1 High severity
- 7.1 High severity
- 7.1 High severity
- 7.1 High severity
- 7.1 High severity
Spotted an error? Tell us.