Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

MediumCVSS 5.3 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 21/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.86% (FIRST EPSS); higher than 58.9% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 06afce714d87c7cd1dcfccbcd800c5c5d2cf1cfd, 1c3844c5f4eac043954ebf6403fa9fd1f0e9c1c0, 3.11.

Low priority for now. Upgrade to Linux Linux 06afce714d87c7cd1dcfccbcd800c5c5d2cf1cfd, 1c3844c5f4eac043954ebf6403fa9fd1f0e9c1c0, 3.11 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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().

Published
Jun 19, 2024
Updated
Jun 17, 2026
EPSS
0.8% · 58th percentile

Report tools

JSON

Action score

21

Monitor

Low priority for now.

CVSS
21 / 40 · 5.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.8%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-38582

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • c23f3a9fa7826af0465b9408b186f6b555991890, 28cd54f27d309bd65db8ff4b8e6275345287484c, ec7cae16b37ab478d6d7e33e8563b24ca189e6cf, d26f2dfa556323787ee1ebd5d03aeaa8650c7404, 52e87609d9d3ea34cadb5676e8ea85d025ac9632, 7bb9e4a06e12583f1418b669dc45bb3ee84496c6, 3.19affected
    • 7ef3ff2fea8bf5e4a21cef47ad87710a3d0fdb52 and later · before 911d38be151921a5d152bb55e81fd752384c6830affected · git
    • 7ef3ff2fea8bf5e4a21cef47ad87710a3d0fdb52 and later · before bc9cee50a4a4ca23bdc49f75ea8242d8a2193b3baffected · git
    • 7ef3ff2fea8bf5e4a21cef47ad87710a3d0fdb52 and later · before eff7cdf890b02596b8d73e910bdbdd489175dbdbaffected · git
    • 7ef3ff2fea8bf5e4a21cef47ad87710a3d0fdb52 and later · before 06afce714d87c7cd1dcfccbcd800c5c5d2cf1cfdaffected · git
    • 7ef3ff2fea8bf5e4a21cef47ad87710a3d0fdb52 and later · before 1c3844c5f4eac043954ebf6403fa9fd1f0e9c1c0affected · git
    • 7ef3ff2fea8bf5e4a21cef47ad87710a3d0fdb52 and later · before a8799662fed1f8747edae87a1937549288baca6aaffected · git
    • 7ef3ff2fea8bf5e4a21cef47ad87710a3d0fdb52 and later · before 6e5c8e8e024e147b834f56f2115aad241433679baffected · git
    • 7ef3ff2fea8bf5e4a21cef47ad87710a3d0fdb52 and later · before c516db6ab9eabbedbc430b4f93b0d8728e9b427faffected · git
    • 7ef3ff2fea8bf5e4a21cef47ad87710a3d0fdb52 and later · before eb85dace897c5986bc2f36b3c783c6abb8a4292eaffected · git
Affected versions · NVD (8)

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernelbefore 4.19.316
  • linux linux kernel4.20 and later · before 5.4.278
  • linux linux kernel5.5 and later · before 5.10.219
  • linux linux kernel5.11 and later · before 5.15.161
  • linux linux kernel5.16 and later · before 6.1.93
  • linux linux kernel6.2 and later · before 6.6.33
  • linux linux kernel6.7 and later · before 6.8.12
  • linux linux kernel6.9 and later · before 6.9.3

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.94-16.1.94-1
Debian:13linuxbefore 6.8.12-16.8.12-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-38580Jun 19, 2024 · epoll: be better about file lifetimes
    18Monitor
  • ← EarlierCVE-2024-38581Jun 19, 2024 · drm/amdgpu/mes: fix use-after-free issue
    31Monitor
  • Later →CVE-2024-38583Jun 19, 2024 · nilfs2: fix use-after-free of timer for log writer thread
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux06afce714d87c7cd1dcfccbcd800c5c5d2cf1cfdVendor (CNA)
Linux Linux1c3844c5f4eac043954ebf6403fa9fd1f0e9c1c0Vendor (CNA)
Linux Linux3.11Vendor (CNA)
Linux Linux3.13Vendor (CNA)
Linux Linux3.15Vendor (CNA)
Linux Linux3.19Vendor (CNA)
Linux Linux3.3Vendor (CNA)
Linux Linux3.5Vendor (CNA)
Linux Linux6e5c8e8e024e147b834f56f2115aad241433679bVendor (CNA)
Linux Linux911d38be151921a5d152bb55e81fd752384c6830Vendor (CNA)
Linux Linuxa8799662fed1f8747edae87a1937549288baca6aVendor (CNA)
Linux Linuxbc9cee50a4a4ca23bdc49f75ea8242d8a2193b3bVendor (CNA)
Linux Linuxc516db6ab9eabbedbc430b4f93b0d8728e9b427fVendor (CNA)
Linux Linuxeb85dace897c5986bc2f36b3c783c6abb8a4292eVendor (CNA)
Linux Linuxeff7cdf890b02596b8d73e910bdbdd489175dbdbVendor (CNA)
debian:linux6.1.94-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
low · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
Low

Weakness class (CWE)

CWE-667 · Improper Locking

CVSS vector

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

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

References

Show all references (9 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records