Linux: Out-of-bounds Read
CVE-2023-53136 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 f3969427fb06a2c3cd6efd7faab63505cfa76e76, ac1968ac399205fda9ee3b18f7de7416cb3a5d0d, a59d6306263c38e5c0592ea4451ca26a0778c947 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.19% 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 f3969427fb06a2c3cd6efd7faab63505cfa76e76 or ac1968ac399205fda9ee3b18f7de7416cb3a5d0d or a59d6306263c38e5c0592ea4451ca26a0778c947 or 2aab4b96900272885bc157f8b236abf1cdc02e08, whichever matches your release line, or a later version.
- Update Linux Kernel to 5.15.103 or 6.1.20 or 6.2.7, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 314001f0bf927015e459c9d387d62a231fe93af3 up to, but not including, f3969427fb06a2c3cd6efd7faab63505cfa76e76; 314001f0bf927015e459c9d387d62a231fe93af3 up to, but not including, ac1968ac399205fda9ee3b18f7de7416cb3a5d0d; 314001f0bf927015e459c9d387d62a231fe93af3 up to, but not including, a59d6306263c38e5c0592ea4451ca26a0778c947; 314001f0bf927015e459c9d387d62a231fe93af3 up to, but not including, 2aab4b96900272885bc157f8b236abf1cdc02e08; 5.15 | f3969427fb06a2c3cd6efd7faab63505cfa76e76, ac1968ac399205fda9ee3b18f7de7416cb3a5d0d, a59d6306263c38e5c0592ea4451ca26a0778c947, 2aab4b96900272885bc157f8b236abf1cdc02e08 |
| Linux | Linux Kernel | 5.15 up to, but not including, 5.15.103; 5.16 up to, but not including, 6.1.20; 6.2 up to, but not including, 6.2.7; 6.3 | 5.15.103, 6.1.20, 6.2.7 |
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.
Official description
In the Linux kernel, the following vulnerability has been resolved: af_unix: fix struct pid leaks in OOB support syzbot reported struct pid leak [1]. Issue is that queue_oob() calls maybe_add_creds() which potentially holds a reference on a pid. But skb->destructor is not set (either directly or by calling unix_scm_to_skb()) This means that subsequent kfree_skb() or consume_skb() would leak this reference. In this fix, I chose to fully support scm even for the OOB message. [1] BUG: memory leak unreferenced object 0xffff8881053e7f80 (size 128): comm "syz-executor242", pid 5066, jiffies 4294946079 (age 13.220s) hex dump (first 32 bytes): 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace: [<ffffffff812ae26a>] alloc_pid+0x6a/0x560 kernel/pid.c:180 [<ffffffff812718df>] copy_process+0x169f/0x26c0 kernel/fork.c:2285 [<ffffffff81272b37>] kernel_clone+0xf7/0x610 kernel/fork.c:2684 [<ffffffff812730cc>] __do_sys_clone+0x7c/0xb0 kernel/fork.c:2825 [<ffffffff849ad699>] do_syscall_x64 arch/x86/entry/common.c:50 [inline] [<ffffffff849ad699>] do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80 [<ffffffff84a0008b>] entry_SYSCALL_64_after_hwframe+0x63/0xcd
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.1 High severity
- 7.1 High severity
- 7.1 High severity
- 7.1 High severity
- 7.1 High severity
- 8.8 High severity
Spotted an error? Tell us.