Answer in brief
CVE-2023-53608 records a High severity (CVSS 7.8) vulnerability in nilfs2: fix potential UAF of struct nilfs_sc_info in nilfs_segctor_thread(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2023-53608 records a High severity (CVSS 7.8) vulnerability in nilfs2: fix potential UAF of struct nilfs_sc_info in nilfs_segctor_thread(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.3:rc1:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.3:rc2:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.3:rc3:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.3:rc4:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.3:rc5:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 <034cce77d52ba013ce62b4f5258c29907eb1ada5 || >=9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 <0dbf0e64b91ee8fcb278aea93eb06fc7d56ecbcc || >=9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 <613bf23c070d11c525268f2945aa594704a9b764 || >=9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 <f32297dba338dc06d62286dedb3cdbd5175b1719 || >=9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 <92684e02654c91a61a0b0561433b710bcece19fe || >=9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 <bae009a2f1b7c2011d2e92d8c84868d315c0b97e || >=9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 <b4d80bd6370b81a1725b6b8f7894802c23a14e9f || >=9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 <6be49d100c22ffea3287a4b19d7639d259888e33 | 034cce77d52ba013ce62b4f5258c29907eb1ada5, 0dbf0e64b91ee8fcb278aea93eb06fc7d56ecbcc, 613bf23c070d11c525268f2945aa594704a9b764, f32297dba338dc06d62286dedb3cdbd5175b1719, 92684e02654c91a61a0b0561433b710bcece19fe, bae009a2f1b7c2011d2e92d8c84868d315c0b97e, b4d80bd6370b81a1725b6b8f7894802c23a14e9f, 6be49d100c22ffea3287a4b19d7639d259888e33 |
| Linux/Linuxgeneric | 2.6.30 | Not reported |
Published upstream
Oct 4, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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.
Quoted source text, attributed separately from HOL analysis.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.3:rc1:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.3:rc2:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.3:rc3:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.3:rc4:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.3:rc5:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 <034cce77d52ba013ce62b4f5258c29907eb1ada5 || >=9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 <0dbf0e64b91ee8fcb278aea93eb06fc7d56ecbcc || >=9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 <613bf23c070d11c525268f2945aa594704a9b764 || >=9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 <f32297dba338dc06d62286dedb3cdbd5175b1719 || >=9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 <92684e02654c91a61a0b0561433b710bcece19fe || >=9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 <bae009a2f1b7c2011d2e92d8c84868d315c0b97e || >=9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 <b4d80bd6370b81a1725b6b8f7894802c23a14e9f || >=9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 <6be49d100c22ffea3287a4b19d7639d259888e33 | 034cce77d52ba013ce62b4f5258c29907eb1ada5, 0dbf0e64b91ee8fcb278aea93eb06fc7d56ecbcc, 613bf23c070d11c525268f2945aa594704a9b764, f32297dba338dc06d62286dedb3cdbd5175b1719, 92684e02654c91a61a0b0561433b710bcece19fe, bae009a2f1b7c2011d2e92d8c84868d315c0b97e, b4d80bd6370b81a1725b6b8f7894802c23a14e9f, 6be49d100c22ffea3287a4b19d7639d259888e33 |
| Linux/Linuxgeneric | 2.6.30 | Not reported |
Published upstream
Oct 4, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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.
Quoted source text, attributed separately from HOL analysis.