CyberSecBulletin
CVE-2023-52682NVD status: Modified

Linux: Out-of-bounds Read

CVE-2023-52682 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 2bfe8fdb674f71747553a65f2ef27e14c8880655, 9bfd5ea71521d0e522ba581c6ccc5db93759c0c3, 4535be48780431753505e74e1b1ad4836a189bc2 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.23% 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 2bfe8fdb674f71747553a65f2ef27e14c8880655 or 9bfd5ea71521d0e522ba581c6ccc5db93759c0c3 or 4535be48780431753505e74e1b1ad4836a189bc2 or f904c156d8011d8291ffd5b6b398f3747e294986, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 6.1.75 or 6.6.14 or 6.7.2, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux4c8ff7095bef64fc47e996a938f7d57f9e077da3 up to, but not including, 2bfe8fdb674f71747553a65f2ef27e14c8880655; 4c8ff7095bef64fc47e996a938f7d57f9e077da3 up to, but not including, 9bfd5ea71521d0e522ba581c6ccc5db93759c0c3; 4c8ff7095bef64fc47e996a938f7d57f9e077da3 up to, but not including, 4535be48780431753505e74e1b1ad4836a189bc2; 4c8ff7095bef64fc47e996a938f7d57f9e077da3 up to, but not including, f904c156d8011d8291ffd5b6b398f3747e294986; 4c8ff7095bef64fc47e996a938f7d57f9e077da3 up to, but not including, 55fdc1c24a1d6229fe0ecf31335fb9a2eceaaa00; 5.62bfe8fdb674f71747553a65f2ef27e14c8880655, 9bfd5ea71521d0e522ba581c6ccc5db93759c0c3, 4535be48780431753505e74e1b1ad4836a189bc2, f904c156d8011d8291ffd5b6b398f3747e294986, 55fdc1c24a1d6229fe0ecf31335fb9a2eceaaa00
LinuxLinux Kernel5.6 up to, but not including, 6.1.75; 6.2 up to, but not including, 6.6.14; 6.7 up to, but not including, 6.7.26.1.75, 6.6.14, 6.7.2

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: f2fs: fix to wait on block writeback for post_read case If inode is compressed, but not encrypted, it missed to call f2fs_wait_on_block_writeback() to wait for GCed page writeback in IPU write path. Thread A GC-Thread - f2fs_gc - do_garbage_collect - gc_data_segment - move_data_block - f2fs_submit_page_write migrate normal cluster's block via meta_inode's page cache - f2fs_write_single_data_page - f2fs_do_write_data_page - f2fs_inplace_write_data - f2fs_submit_page_bio IRQ - f2fs_read_end_io IRQ old data overrides new data due to out-of-order GC and common IO. - f2fs_read_end_io

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.

More Out-of-bounds Read vulnerabilities (CWE-125)

Timeline

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

References

Recent Out-of-bounds Read vulnerabilities

Spotted an error? Tell us.