ghsa-v738-pvhm-mhvp
Vulnerability from github
Published
2024-07-29 15:30
Modified
2024-07-29 15:30
Details

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

Show details on source website

To clipboard 

{
   affected: [],
   aliases: [
      "CVE-2024-41034",
   ],
   database_specific: {
      cwe_ids: [],
      github_reviewed: false,
      github_reviewed_at: null,
      nvd_published_at: "2024-07-29T15:15:11Z",
      severity: null,
   },
   details: "In the Linux kernel, the following vulnerability has been resolved:\n\nnilfs2: fix kernel bug on rename operation of broken directory\n\nSyzbot reported that in rename directory operation on broken directory on\nnilfs2, __block_write_begin_int() called to prepare block write may fail\nBUG_ON check for access exceeding the folio/page size.\n\nThis is because nilfs_dotdot(), which gets parent directory reference\nentry (\"..\") of the directory to be moved or renamed, does not check\nconsistency enough, and may return location exceeding folio/page size for\nbroken directories.\n\nFix this issue by checking required directory entries (\".\" and \"..\") in\nthe first chunk of the directory in nilfs_dotdot().",
   id: "GHSA-v738-pvhm-mhvp",
   modified: "2024-07-29T15:30:40Z",
   published: "2024-07-29T15:30:40Z",
   references: [
      {
         type: "ADVISORY",
         url: "https://nvd.nist.gov/vuln/detail/CVE-2024-41034",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/1a8879c0771a68d70ee2e5e66eea34207e8c6231",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/24c1c8566a9b6be51f5347be2ea76e25fc82b11e",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/298cd810d7fb687c90a14d8f9fd1b8719a7cb8a5",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/60f61514374e4a0c3b65b08c6024dd7e26150bfd",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/7000b438dda9d0f41a956fc9bffed92d2eb6be0d",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/a9a466a69b85059b341239766a10efdd3ee68a4b",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/a9e1ddc09ca55746079cc479aa3eb6411f0d99d4",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/ff9767ba2cb949701e45e6e4287f8af82986b703",
      },
   ],
   schema_version: "1.4.0",
   severity: [],
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.