CVE-2023-53608

nilfs2: fix potential UAF of struct nilfs_sc_info in nilfs_segctor_thread()

HIGH
7.8
CVSS Score
Published: October 4, 2025 at 03:44 PM UTC
Updated: August 5, 2026 at 10:24 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%

Description

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 after the NULL assignment to "sc_task", it is possible that nilfs_segctor_kill_thread() will detect it and return to continue the deallocation, freeing the nilfs_sc_info structure before the thread does the notification. This fixes the issue by protecting the NULL assignment to "sc_task" and its notification, with spinlock "sc_state_lock" of the struct nilfs_sc_info. Since nilfs_segctor_kill_thread() does a final check to see if "sc_task" is NULL with "sc_state_lock" locked, this can eliminate the race.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.30 ≤ v < 4.14.3132.6.30 ≤ v < 4.19.2812.6.30 ≤ v < 5.10.1782.6.30 ≤ v < 5.15.1072.6.30 ≤ v < 5.4.2412.6.30 ≤ v < 6.1.242.6.30 ≤ v < 6.2.112.6.30 ≤ v < 6.34.15 ≤ v < 4.19.2814.20 ≤ v < 5.4.2415.11 ≤ v < 5.15.1075.16 ≤ v < 6.1.245.5 ≤ v < 5.10.1786.2 ≤ v < 6.2.116.3 rc16.3 rc26.3 rc36.3 rc46.3 rc59ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453
Vendor states this is fixed in 034cce77d52ba013ce62b4f5258c29907eb1ada5 (fixed)
Vendor states this is fixed in 0dbf0e64b91ee8fcb278aea93eb06fc7d56ecbcc (fixed)
Vendor states this is fixed in 613bf23c070d11c525268f2945aa594704a9b764 (fixed)
Vendor states this is fixed in 6be49d100c22ffea3287a4b19d7639d259888e33 (fixed)
Vendor states this is fixed in 92684e02654c91a61a0b0561433b710bcece19fe (fixed)
Vendor states this is fixed in b4d80bd6370b81a1725b6b8f7894802c23a14e9f (fixed)
Vendor states this is fixed in bae009a2f1b7c2011d2e92d8c84868d315c0b97e (fixed)
Vendor states this is fixed in f32297dba338dc06d62286dedb3cdbd5175b1719 (fixed)
Vendor states this is fixed in 2.6.30 (unaffected)
Vendor states this is fixed in 4.14.313 (unaffected)
Vendor states this is fixed in 4.19.281 (unaffected)
Vendor states this is fixed in 5.10.178 (unaffected)
Vendor states this is fixed in 5.15.107 (unaffected)
Vendor states this is fixed in 5.4.241 (unaffected)
Vendor states this is fixed in 6.1.24 (unaffected)
Vendor states this is fixed in 6.2.11 (unaffected)
Vendor states this is fixed in 6.3 (unaffected)

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-416

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card