Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2024-38583

7.8 · HIGH

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

Published Jun 19, 2024CWE-416EPSS 0.26%

Overview

CVE-2024-38583 is a high-severity vulnerability. It was published on June 19, 2024 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refgit.kernel.org/stable/c/2f12b2c03c5dae1a0de0a9e5853177e3d6eee3c6Refgit.kernel.org/stable/c/67fa90d4a2ccd9ebb0e1e168c7d0b5d0cf3c7148Refgit.kernel.org/stable/c/68e738be5c518fc3c4e9146b66f67c8fee0135fbRefgit.kernel.org/stable/c/822ae5a8eac30478578a75f7e064f0584931bf2dRefgit.kernel.org/stable/c/82933c84f188dcfe89eb26b0b48ab5d1ca99d164Refgit.kernel.org/stable/c/86a30d6302deddb9fb97ba6fc4b04d0e870b582aRefgit.kernel.org/stable/c/e65ccf3a4de4f0c763d94789615b83e11f204438Refgit.kernel.org/stable/c/f5d4e04634c9cf68bdf23de08ada0bb92e8befe7Refgit.kernel.org/stable/c/f9186bba4ea282b07293c1c892441df3a5441cb0Refgit.kernel.org/stable/c/2f12b2c03c5dae1a0de0a9e5853177e3d6eee3c6

How CyberStrike helps

Frequently asked questions

What is CVE-2024-38583?

CVE-2024-38583 is a high-severity vulnerability. It was published on June 19, 2024 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2024-38583?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2024-38583?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2024-38583?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2024-38583 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2024

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999