NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 31/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.25% (FIRST EPSS).
Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: Linux Linux 2f12b2c03c5dae1a0de0a9e5853177e3d6eee3c6, 67fa90d4a2ccd9ebb0e1e168c7d0b5d0cf3c7148, 68e738be5c518fc3c4e9146b66f67c8fee0135fb.

Low priority for now. Upgrade to Linux Linux 2f12b2c03c5dae1a0de0a9e5853177e3d6eee3c6, 67fa90d4a2ccd9ebb0e1e168c7d0b5d0cf3c7148, 68e738be5c518fc3c4e9146b66f67c8fee0135fb 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 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.

HighCVSS 7.8 · v3.1—No exploit Fix available

Memory safety

BDU:2024-07638

Published: Jun 19, 2024
Updated: Aug 5, 2026
EPSS: 0.2% · 17th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 31 / 40 · 7.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.2%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 7.8
CNA · Linux: 7.8; agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

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.

Running WordPress? Scan your site free with WP Lens

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.

Vendor	Product	CPE
linux	linux kernel	cpe:2.3:o:linux:linux_kernel

Affected versions

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

linux linux kernel2.6.35 and later · before 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.94
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

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
- 2.6.35affected
- fdce895ea5dd4e24edf1f4d693827349a4e5b3b4 and later · before 822ae5a8eac30478578a75f7e064f0584931bf2daffected · git
- fdce895ea5dd4e24edf1f4d693827349a4e5b3b4 and later · before 82933c84f188dcfe89eb26b0b48ab5d1ca99d164affected · git
- fdce895ea5dd4e24edf1f4d693827349a4e5b3b4 and later · before 67fa90d4a2ccd9ebb0e1e168c7d0b5d0cf3c7148affected · git
- fdce895ea5dd4e24edf1f4d693827349a4e5b3b4 and later · before e65ccf3a4de4f0c763d94789615b83e11f204438affected · git
- fdce895ea5dd4e24edf1f4d693827349a4e5b3b4 and later · before 86a30d6302deddb9fb97ba6fc4b04d0e870b582aaffected · git
- fdce895ea5dd4e24edf1f4d693827349a4e5b3b4 and later · before f9186bba4ea282b07293c1c892441df3a5441cb0affected · git
- fdce895ea5dd4e24edf1f4d693827349a4e5b3b4 and later · before 2f12b2c03c5dae1a0de0a9e5853177e3d6eee3c6affected · git
- fdce895ea5dd4e24edf1f4d693827349a4e5b3b4 and later · before 68e738be5c518fc3c4e9146b66f67c8fee0135fbaffected · git
- fdce895ea5dd4e24edf1f4d693827349a4e5b3b4 and later · before f5d4e04634c9cf68bdf23de08ada0bb92e8befe7affected · git

Package-level exposure

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

Ecosystem	Package	Affected range	Fix
Debian:12	linux	before 6.1.94-1	6.1.94-1
Debian:13	linux	before 6.8.12-1	6.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-38581Jun 19, 2024 · drm/amdgpu/mes: fix use-after-free issue
31Monitor
← EarlierCVE-2024-38582Jun 19, 2024 · nilfs2: fix potential hang in nilfs_detach_log_writer()
21Monitor
Later →CVE-2024-38584Jun 19, 2024 · net: ti: icssg_prueth: Fix NULL pointer dereference in prueth_probe()
22Monitor

Remediation

Which version to upgrade to

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

Product / package	Fixed version	Source
Linux Linux	2f12b2c03c5dae1a0de0a9e5853177e3d6eee3c6	Vendor (CNA)
Linux Linux	67fa90d4a2ccd9ebb0e1e168c7d0b5d0cf3c7148	Vendor (CNA)
Linux Linux	68e738be5c518fc3c4e9146b66f67c8fee0135fb	Vendor (CNA)
Linux Linux	822ae5a8eac30478578a75f7e064f0584931bf2d	Vendor (CNA)
Linux Linux	82933c84f188dcfe89eb26b0b48ab5d1ca99d164	Vendor (CNA)
Linux Linux	86a30d6302deddb9fb97ba6fc4b04d0e870b582a	Vendor (CNA)
Linux Linux	e65ccf3a4de4f0c763d94789615b83e11f204438	Vendor (CNA)
Linux Linux	f5d4e04634c9cf68bdf23de08ada0bb92e8befe7	Vendor (CNA)
Linux Linux	f9186bba4ea282b07293c1c892441df3a5441cb0	Vendor (CNA)
debian:linux	6.1.94-1 · Debian:12	Package 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.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Someone with local access to the system can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Local
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

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

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

Attack context

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

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

Fix✗ → ✓Sep 28, 2026, 10:11 PM UTC

For records you follow, these changes also arrive as notifications. →

References

git.kernel.org/stable/c/2f12b2c03c5dae1a0de0a9e5853177e3d6eee3c6

Show all references (9 more)

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

All records