SECUFOCUSNOW
Home›CVE index›CVE-2023-53214
Review reviewHigh

CVE-2023-53214

Linux Linux, linux kernel

In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to avoid potential memory corruption in __update_iostat_latency() Add iotype sanity check to avoid potential memory corruption. This is to fix the compile error below: fs/f2fs/iostat.c:231 __update_iostat_latency() error: buffer overflow 'io_lat->peak_lat[type]' 3 <= 3 vim +228 fs/f2fs/iostat.c 211 static inline void __update_iostat_latency(struct bio_iostat_ctx *iostat_ctx, 212 enum iostat_lat_type type) 213 { 214 unsigned long ts_diff; 215 unsigned int page_type = iostat_ctx->type; 216 struct f2fs_sb_info *sbi =...

CVSS
7.8
EPSS
0.16%
5.73% percentile
CISA KEV
Not listed
Published
2025.09.16
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.16%
Technical severityCVSS 7.8

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to avoid potential memory corruption in __update_iostat_latency() Add iotype sanity check to avoid potential memory corruption. This is to fix the compile error below: fs/f2fs/iostat.c:231 __update_iostat_latency() error: buffer overflow 'io_lat->peak_lat[type]' 3 <= 3 vim +228 fs/f2fs/iostat.c 211 static inline void __update_iostat_latency(struct bio_iostat_ctx *iostat_ctx, 212 enum iostat_lat_type type) 213 { 214 unsigned long ts_diff; 215 unsigned int page_type = iostat_ctx->type; 216 struct f2fs_sb_info *sbi =...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= a4b6817625e71d5d4aee16cacf7a7fec077c6dbe < aa4d726af72a21732ce120484e0b1240674a13b3, >= a4b6817625e71d5d4aee16cacf7a7fec077c6dbe < 22ddbbff116ee7dce5431feb1c0f36a507d2d68d, >= a4b6817625e71d5d4aee16cacf7a7fec077c6dbe < 20b4f3de0f3932f71b4a8daf0671e517a8d98022, >= a4b6817625e71d5d4aee16cacf7a7fec077c6dbe < 0dbbf0fb38d5ec5d4138d1aeaeb43d9217b9a592, >= 5.15, >= 5.15 < 5.15.100, >= 5.16 < 6.1.18, >= 6.2 < 6.2.5
Fixed versions
5.15.100, 6.1.18, 6.2.5

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-787