Linux: Out-of-bounds Read
CVE-2022-48827 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 1726a39b0879acfb490b22dca643f26f4f907da9, c6eff5c4277146a78b4fb8c9b668dd64542c41b0, 44502aca8e02ab32d6b0eb52e006a5ec9402719b 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.62% chance of exploitation within 30 days, higher than 50% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Linux to 1726a39b0879acfb490b22dca643f26f4f907da9 or c6eff5c4277146a78b4fb8c9b668dd64542c41b0 or 44502aca8e02ab32d6b0eb52e006a5ec9402719b or 0cb4d23ae08c48f6bf3c29a8e5c4a74b8388b960, whichever matches your release line, or a later version.
- Update SIMATIC S7-1500 TM MFP - GNU/Linux subsystem to V1.1.1 or a later version.
- Update Linux Kernel to 5.10.220 or 5.15.24 or 5.16.10, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, 1726a39b0879acfb490b22dca643f26f4f907da9; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, c6eff5c4277146a78b4fb8c9b668dd64542c41b0; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, 44502aca8e02ab32d6b0eb52e006a5ec9402719b; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, 0cb4d23ae08c48f6bf3c29a8e5c4a74b8388b960; 2.6.12 | 1726a39b0879acfb490b22dca643f26f4f907da9, c6eff5c4277146a78b4fb8c9b668dd64542c41b0, 44502aca8e02ab32d6b0eb52e006a5ec9402719b, 0cb4d23ae08c48f6bf3c29a8e5c4a74b8388b960 |
| Siemens | SIMATIC S7-1500 TM MFP - GNU/Linux subsystem | before V1.1.1 | V1.1.1 |
| Linux | Linux Kernel | before 5.10.220; 5.11 up to, but not including, 5.15.24; 5.16 up to, but not including, 5.16.10; 5.17 | 5.10.220, 5.15.24, 5.16.10 |
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.5 | High | CNA |
| CVSS 3.1 | 7.1 | High | NVD |
Official description
In the Linux kernel, the following vulnerability has been resolved: NFSD: Fix the behavior of READ near OFFSET_MAX Dan Aloni reports: > Due to commit 8cfb9015280d ("NFS: Always provide aligned buffers to > the RPC read layers") on the client, a read of 0xfff is aligned up > to server rsize of 0x1000. > > As a result, in a test where the server has a file of size > 0x7fffffffffffffff, and the client tries to read from the offset > 0x7ffffffffffff000, the read causes loff_t overflow in the server > and it returns an NFS code of EINVAL to the client. The client as > a result indefinitely retries the request. The Linux NFS client does not handle NFS?ERR_INVAL, even though all NFS specifications permit servers to return that status code for a READ. Instead of NFS?ERR_INVAL, have out-of-range READ requests succeed and return a short result. Set the EOF flag in the result to prevent the client from retrying the READ request. This behavior appears to be consistent with Solaris NFS servers. Note that NFSv3 and NFSv4 use u64 offset values on the wire. These must be converted to loff_t internally before use -- an implicit type cast is not adequate for this purpose. Otherwise VFS checks against sb->s_maxbytes do not work properly.
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
Other references
Recent Out-of-bounds Read vulnerabilities
- 7.1 High severity
- 7.8 High severity
- 7.1 High severity
- 7.1 High severity
- 9.1 Critical severity
- 8.8 High severity
Spotted an error? Tell us.