LiveActive security incident?Get immediate response
CVE Record

CVE-2024-38583: nilfs2: fix use-after-free of timer for log writer thread

In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix use-after-free of timer for log writer thread Patch series "nilfs2: fix log writer related issues". This bug fix series covers three nilfs2 log writer-related issues, including a timer use-after-free issue and potential deadlock issue on unmount, and a potential freeze issue in event synchronization found during their analysis. Details are described in each commit log. This patch (of 3): A use-after-free issue has been reported regarding the timer sc_timer on the nilfs_sc_info structure. The problem is that even though it is used to wake up a sleeping log writer thread, sc_timer is not shut down until the nilfs_sc_info structure is about to be freed, and is used regardless of the thread's lifetime. Fix this issue by limiting the use of sc_timer only while the log writer thread is alive.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2024-38583 is a Linux kernel bug in the nilfs2 filesystem log writer. A timer could remain active beyond the lifetime of the thread it wakes, creating a use-after-free condition. Business risk is mainly for Linux systems that use or allow nilfs2 filesystems, especially older or unpatched kernels.

Executive priority

Schedule remediation through normal kernel security update processes, with higher priority for Linux fleets that use nilfs2 or allow users to mount filesystems. Evidence does not support an emergency active-exploitation posture from the supplied sources.

Technical view

The issue is in nilfs2 sc_timer handling on nilfs_sc_info. The timer was shut down only when nilfs_sc_info was freed and could be used regardless of log writer thread lifetime. The kernel fix limits sc_timer use to the period while the log writer thread is alive.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions where nilfs2 is available and used or mountable. The bundle lists affected Linux versions from 2.6.35 through several stable lines before fixes, but gives no deployment-specific trigger conditions.

Exploitation context

The source bundle does not report active exploitation, and KEV is false. No public exploit status, attacker prerequisites, or impact rating is provided. Treat this as a kernel memory-safety issue requiring normal kernel patch governance, not emergency exploitation response based on the supplied evidence.

Researcher notes

The record describes the root cause and fix direction but does not include CVSS, CWE, exploitability, or precise security impact. Analysis should stay focused on nilfs2 timer lifetime, log writer teardown, and whether downstream kernels include the stable commits.

Mitigation direction

  • Update to a kernel containing the referenced stable nilfs2 fixes.
  • Apply distribution kernel updates, including Debian LTS guidance where applicable.
  • Inventory systems where nilfs2 is enabled, loaded, or used.
  • Restrict unnecessary filesystem mounting where operationally feasible.
  • Monitor vendor advisories for impact ratings or additional mitigations.

Validation and detection

  • Check running kernel versions against vendor-fixed releases.
  • Confirm distribution security updates containing CVE-2024-38583 are installed.
  • Identify whether nilfs2 support is present or loaded on Linux hosts.
  • Review package advisories for each maintained kernel stream.
  • Prioritize validation on systems handling untrusted removable or user-provided filesystems.
Prepared
Confidence
medium
Sources
12

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-38583 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
11Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxfdce895ea5dd4e24edf1f4d693827349a4e5b3b4, fdce895ea5dd4e24edf1f4d693827349a4e5b3b4, fdce895ea5dd4e24edf1f4d693827349a4e5b3b4, fdce895ea5dd4e24edf1f4d693827349a4e5b3b4, fdce895ea5dd4e24edf1f4d693827349a4e5b3b4, fdce895ea5dd4e24edf1f4d693827349a4e5b3b4, fdce895ea5dd4e24edf1f4d693827349a4e5b3b4, fdce895ea5dd4e24edf1f4d693827349a4e5b3b4, fdce895ea5dd4e24edf1f4d693827349a4e5b3b4unaffected
LinuxLinux2.6.35, 0, 4.19.316, 5.4.278, 5.10.219, 5.15.161, 6.1.94, 6.6.33, 6.8.12, 6.9.3, 6.10affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.