LiveActive security incident?Get immediate response
CVE Record

CVE-2024-38582: nilfs2: fix potential hang in nilfs_detach_log_writer()

In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix potential hang in nilfs_detach_log_writer() Syzbot has reported a potential hang in nilfs_detach_log_writer() called during nilfs2 unmount. Analysis revealed that this is because nilfs_segctor_sync(), which synchronizes with the log writer thread, can be called after nilfs_segctor_destroy() terminates that thread, as shown in the call trace below: nilfs_detach_log_writer nilfs_segctor_destroy nilfs_segctor_kill_thread --> Shut down log writer thread flush_work nilfs_iput_work_func nilfs_dispose_list iput nilfs_evict_inode nilfs_transaction_commit nilfs_construct_segment (if inode needs sync) nilfs_segctor_sync --> Attempt to synchronize with log writer thread *** DEADLOCK *** Fix this issue by changing nilfs_segctor_sync() so that the log writer thread returns normally without synchronizing after it terminates, and by forcing tasks that are already waiting to complete once after the thread terminates. The skipped inode metadata flushout will then be processed together in the subsequent cleanup work in nilfs_segctor_destroy().

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Linux kernel flaw can make a system hang while unmounting a NILFS2 filesystem. It is primarily an availability issue, not a data theft or code execution issue. Business urgency depends on whether NILFS2 is used on production Linux systems.

Executive priority

Treat as a moderate operational reliability issue. Patch through normal kernel maintenance, with faster action for systems using NILFS2 where unmount hangs could affect service recovery or maintenance windows.

Technical view

CVE-2024-38582 is a NILFS2 log writer teardown race. During unmount, nilfs_segctor_sync() could wait after nilfs_segctor_destroy() terminated the log writer thread, causing a deadlock. Kernel stable commits change synchronization behavior after thread termination.

Likely exposure

Exposure is likely limited to Linux systems running affected kernel versions where NILFS2 filesystems are mounted or used. The provided data does not identify cloud platforms, appliances, or distributions beyond a Debian LTS advisory.

Exploitation context

The source describes a syzbot-reported potential hang and marks KEV as false. No provided source states active exploitation, public exploit use, or impact beyond low availability loss.

Researcher notes

The affected path is NILFS2 unmount cleanup. The deadlock sequence involves nilfs_segctor_destroy(), flush_work(), inode eviction, nilfs_transaction_commit(), nilfs_construct_segment(), and nilfs_segctor_sync(). Evidence is source-level and advisory-based; exploitation details are not provided.

Mitigation direction

  • Update Linux kernels to versions containing the linked stable NILFS2 fixes.
  • Apply Debian LTS kernel updates where Debian guidance applies.
  • Check your distribution vendor advisory for the exact fixed package version.
  • Prioritize systems that mount NILFS2 filesystems in production or shared environments.

Validation and detection

  • Inventory Linux hosts for NILFS2 filesystem use.
  • Compare running kernel versions against vendor fixed versions or linked stable commits.
  • Confirm patched kernels include the nilfs_detach_log_writer() fix lineage.
  • Review monitoring for repeated unmount hangs or blocked NILFS2 cleanup tasks.
Prepared
Confidence
high
Sources
12

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-38582 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
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

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.

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

SSVC decision data

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

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L3.91.4CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2024-38582Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux7ef3ff2fea8bf5e4a21cef47ad87710a3d0fdb52, 7ef3ff2fea8bf5e4a21cef47ad87710a3d0fdb52, 7ef3ff2fea8bf5e4a21cef47ad87710a3d0fdb52, 7ef3ff2fea8bf5e4a21cef47ad87710a3d0fdb52, 7ef3ff2fea8bf5e4a21cef47ad87710a3d0fdb52, 7ef3ff2fea8bf5e4a21cef47ad87710a3d0fdb52, 7ef3ff2fea8bf5e4a21cef47ad87710a3d0fdb52, 7ef3ff2fea8bf5e4a21cef47ad87710a3d0fdb52, 7ef3ff2fea8bf5e4a21cef47ad87710a3d0fdb52, c23f3a9fa7826af0465b9408b186f6b555991890, 28cd54f27d309bd65db8ff4b8e6275345287484c, ec7cae16b37ab478d6d7e33e8563b24ca189e6cf, d26f2dfa556323787ee1ebd5d03aeaa8650c7404, 52e87609d9d3ea34cadb5676e8ea85d025ac9632, 7bb9e4a06e12583f1418b669dc45bb3ee84496c6unaffected
LinuxLinux3.19, 0, 4.19.316, 5.4.278, 5.10.219, 5.15.161, 6.1.93, 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.