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

CVE-2023-53608

Linux Linux, linux kernel

In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix potential UAF of struct nilfs_sc_info in nilfs_segctor_thread() The finalization of nilfs_segctor_thread() can race with nilfs_segctor_kill_thread() which terminates that thread, potentially causing a use-after-free BUG as KASAN detected. At the end of nilfs_segctor_thread(), it assigns NULL to "sc_task" member of "struct nilfs_sc_info" to indicate the thread has finished, and then notifies nilfs_segctor_kill_thread() of this using waitqueue "sc_wait_task" on the struct nilfs_sc_info. However, here, immediately...

CVSS
7.8
EPSS
0.14%
3.71% percentile
CISA KEV
Not listed
Published
2025.10.05
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

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

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix potential UAF of struct nilfs_sc_info in nilfs_segctor_thread() The finalization of nilfs_segctor_thread() can race with nilfs_segctor_kill_thread() which terminates that thread, potentially causing a use-after-free BUG as KASAN detected. At the end of nilfs_segctor_thread(), it assigns NULL to "sc_task" member of "struct nilfs_sc_info" to indicate the thread has finished, and then notifies nilfs_segctor_kill_thread() of this using waitqueue "sc_wait_task" on the struct nilfs_sc_info. However, here, immediately...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 < 034cce77d52ba013ce62b4f5258c29907eb1ada5, >= 9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 < 0dbf0e64b91ee8fcb278aea93eb06fc7d56ecbcc, >= 9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 < 613bf23c070d11c525268f2945aa594704a9b764, >= 9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 < f32297dba338dc06d62286dedb3cdbd5175b1719, >= 9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 < 92684e02654c91a61a0b0561433b710bcece19fe, >= 9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 < bae009a2f1b7c2011d2e92d8c84868d315c0b97e, >= 9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 < b4d80bd6370b81a1725b6b8f7894802c23a14e9f, >= 9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 < 6be49d100c22ffea3287a4b19d7639d259888e33, >= 2.6.30, >= 2.6.30 < 4.14.313, >= 4.15 < 4.19.281, >= 4.20 < 5.4.241, >= 5.5 < 5.10.178, >= 5.11 < 5.15.107, >= 5.16 < 6.1.24, >= 6.2 < 6.2.11, 6.3
Fixed versions
4.14.313, 4.19.281, 5.4.241, 5.10.178, 5.15.107, 6.1.24, 6.2.11

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-416