CyberSecBulletin
CVE-2023-53065NVD status: Modified

Linux: Out-of-bounds Write

Published Updated By the CyberSecBulletin desk

CVE-2023-53065 is a high-severity out-of-bounds write vulnerability in Linux, with a CVSS 3.1 base score of 7.8 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 ddcf8320003638a06eb1e46412e045d0c5701575, ac5f88642cb211152041f84a985309e9af4baf59, ff8137727a2af4ad5f6e6c8b9f7ec5e8db9da86c 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.21% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Linux to ddcf8320003638a06eb1e46412e045d0c5701575 or ac5f88642cb211152041f84a985309e9af4baf59 or ff8137727a2af4ad5f6e6c8b9f7ec5e8db9da86c or 3a776fddb4e5598c8bfcd4ad094fba34f9856fc9, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 5.10.177 or 5.15.105 or 6.1.22 or 6.2.9, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux267fb27352b6fc9fdbad753127a239f75618ecbc up to, but not including, ddcf8320003638a06eb1e46412e045d0c5701575; 267fb27352b6fc9fdbad753127a239f75618ecbc up to, but not including, ac5f88642cb211152041f84a985309e9af4baf59; 267fb27352b6fc9fdbad753127a239f75618ecbc up to, but not including, ff8137727a2af4ad5f6e6c8b9f7ec5e8db9da86c; 267fb27352b6fc9fdbad753127a239f75618ecbc up to, but not including, 3a776fddb4e5598c8bfcd4ad094fba34f9856fc9; 267fb27352b6fc9fdbad753127a239f75618ecbc up to, but not including, eb81a2ed4f52be831c9fb879752d89645a312c13; 5.10ddcf8320003638a06eb1e46412e045d0c5701575, ac5f88642cb211152041f84a985309e9af4baf59, ff8137727a2af4ad5f6e6c8b9f7ec5e8db9da86c, 3a776fddb4e5598c8bfcd4ad094fba34f9856fc9, eb81a2ed4f52be831c9fb879752d89645a312c13
LinuxLinux Kernel5.10.1 up to, but not including, 5.10.177; 5.11 up to, but not including, 5.15.105; 5.16 up to, but not including, 6.1.22; 6.2 up to, but not including, 6.2.9; 5.10; 6.35.10.177, 5.15.105, 6.1.22, 6.2.9

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
HighData or code can be modified at will.
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:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.17.8HighCNA
CVSS 3.17.8HighNVD

Official description

In the Linux kernel, the following vulnerability has been resolved: perf/core: Fix perf_output_begin parameter is incorrectly invoked in perf_event_bpf_output syzkaller reportes a KASAN issue with stack-out-of-bounds. The call trace is as follows: dump_stack+0x9c/0xd3 print_address_description.constprop.0+0x19/0x170 __kasan_report.cold+0x6c/0x84 kasan_report+0x3a/0x50 __perf_event_header__init_id+0x34/0x290 perf_event_header__init_id+0x48/0x60 perf_output_begin+0x4a4/0x560 perf_event_bpf_output+0x161/0x1e0 perf_iterate_sb_cpu+0x29e/0x340 perf_iterate_sb+0x4c/0xc0 perf_event_bpf_event+0x194/0x2c0 __bpf_prog_put.constprop.0+0x55/0xf0 __cls_bpf_delete_prog+0xea/0x120 [cls_bpf] cls_bpf_delete_prog_work+0x1c/0x30 [cls_bpf] process_one_work+0x3c2/0x730 worker_thread+0x93/0x650 kthread+0x1b8/0x210 ret_from_fork+0x1f/0x30 commit 267fb27352b6 ("perf: Reduce stack usage of perf_output_begin()") use on-stack struct perf_sample_data of the caller function. However, perf_event_bpf_output uses incorrect parameter to convert small-sized data (struct perf_bpf_event) into large-sized data (struct perf_sample_data), which causes memory overwriting occurs in __perf_event_header__init_id.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Out-of-bounds Write

The product writes data past the end, or before the beginning, of the intended buffer.

How developers prevent this class of flaw

  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Examples include the Safe C String Library (SafeStr) by Messier and Viega, and the Strsafe.h library from Microsoft. These libraries provide safer versions of overflow-prone string-handling functions.
  • Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.

More Out-of-bounds Write vulnerabilities (CWE-787)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Out-of-bounds Write vulnerabilities

Spotted an error? Tell us.