0.0
NA
CVE-2024-41034
"Linux Nilfs2 Directory Renaming Privilege Bug"
Description

In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix kernel bug on rename operation of broken directory Syzbot reported that in rename directory operation on broken directory on nilfs2, __block_write_begin_int() called to prepare block write may fail BUG_ON check for access exceeding the folio/page size. This is because nilfs_dotdot(), which gets parent directory reference entry ("..") of the directory to be moved or renamed, does not check consistency enough, and may return location exceeding folio/page size for broken directories. Fix this issue by checking required directory entries ("." and "..") in the first chunk of the directory in nilfs_dotdot().

INFO

Published Date :

July 29, 2024, 3:15 p.m.

Last Modified :

Nov. 21, 2024, 9:32 a.m.

Source :

416baaa9-dc9f-4396-8d5f-8c081fb06d67

Remotely Exploitable :

No

Impact Score :

Exploitability Score :

Affected Products

The following products are affected by CVE-2024-41034 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Linux linux_kernel

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2024-41034 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2024-41034 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • CVE Modified by af854a3a-2127-422b-91ae-364da2661108

    Nov. 21, 2024

    Action Type Old Value New Value
    Added Reference https://git.kernel.org/stable/c/1a8879c0771a68d70ee2e5e66eea34207e8c6231
    Added Reference https://git.kernel.org/stable/c/24c1c8566a9b6be51f5347be2ea76e25fc82b11e
    Added Reference https://git.kernel.org/stable/c/298cd810d7fb687c90a14d8f9fd1b8719a7cb8a5
    Added Reference https://git.kernel.org/stable/c/60f61514374e4a0c3b65b08c6024dd7e26150bfd
    Added Reference https://git.kernel.org/stable/c/7000b438dda9d0f41a956fc9bffed92d2eb6be0d
    Added Reference https://git.kernel.org/stable/c/a9a466a69b85059b341239766a10efdd3ee68a4b
    Added Reference https://git.kernel.org/stable/c/a9e1ddc09ca55746079cc479aa3eb6411f0d99d4
    Added Reference https://git.kernel.org/stable/c/ff9767ba2cb949701e45e6e4287f8af82986b703
  • CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Jul. 29, 2024

    Action Type Old Value New Value
    Added Description In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix kernel bug on rename operation of broken directory Syzbot reported that in rename directory operation on broken directory on nilfs2, __block_write_begin_int() called to prepare block write may fail BUG_ON check for access exceeding the folio/page size. This is because nilfs_dotdot(), which gets parent directory reference entry ("..") of the directory to be moved or renamed, does not check consistency enough, and may return location exceeding folio/page size for broken directories. Fix this issue by checking required directory entries ("." and "..") in the first chunk of the directory in nilfs_dotdot().
    Added Reference kernel.org https://git.kernel.org/stable/c/ff9767ba2cb949701e45e6e4287f8af82986b703 [No types assigned]
    Added Reference kernel.org https://git.kernel.org/stable/c/24c1c8566a9b6be51f5347be2ea76e25fc82b11e [No types assigned]
    Added Reference kernel.org https://git.kernel.org/stable/c/a9a466a69b85059b341239766a10efdd3ee68a4b [No types assigned]
    Added Reference kernel.org https://git.kernel.org/stable/c/7000b438dda9d0f41a956fc9bffed92d2eb6be0d [No types assigned]
    Added Reference kernel.org https://git.kernel.org/stable/c/1a8879c0771a68d70ee2e5e66eea34207e8c6231 [No types assigned]
    Added Reference kernel.org https://git.kernel.org/stable/c/60f61514374e4a0c3b65b08c6024dd7e26150bfd [No types assigned]
    Added Reference kernel.org https://git.kernel.org/stable/c/298cd810d7fb687c90a14d8f9fd1b8719a7cb8a5 [No types assigned]
    Added Reference kernel.org https://git.kernel.org/stable/c/a9e1ddc09ca55746079cc479aa3eb6411f0d99d4 [No types assigned]
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2024-41034 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2024-41034 weaknesses.

NONE - Vulnerability Scoring System
© cvefeed.io
Latest DB Update: May. 12, 2025 18:22