ghsa-fx68-rvxh-32hf
Vulnerability from github
Published
2024-05-01 15:30
Modified
2024-11-06 21:30
Details

In the Linux kernel, the following vulnerability has been resolved:

f2fs: fix to avoid potential panic during recovery

During recovery, if FAULT_BLOCK is on, it is possible that f2fs_reserve_new_block() will return -ENOSPC during recovery, then it may trigger panic.

Also, if fault injection rate is 1 and only FAULT_BLOCK fault type is on, it may encounter deadloop in loop of block reservation.

Let's change as below to fix these issues: - remove bug_on() to avoid panic. - limit the loop count of block reservation to avoid potential deadloop.

Show details on source website


{
   affected: [],
   aliases: [
      "CVE-2024-27032",
   ],
   database_specific: {
      cwe_ids: [
         "CWE-835",
      ],
      github_reviewed: false,
      github_reviewed_at: null,
      nvd_published_at: "2024-05-01T13:15:49Z",
      severity: "MODERATE",
   },
   details: "In the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: fix to avoid potential panic during recovery\n\nDuring recovery, if FAULT_BLOCK is on, it is possible that\nf2fs_reserve_new_block() will return -ENOSPC during recovery,\nthen it may trigger panic.\n\nAlso, if fault injection rate is 1 and only FAULT_BLOCK fault\ntype is on, it may encounter deadloop in loop of block reservation.\n\nLet's change as below to fix these issues:\n- remove bug_on() to avoid panic.\n- limit the loop count of block reservation to avoid potential\ndeadloop.",
   id: "GHSA-fx68-rvxh-32hf",
   modified: "2024-11-06T21:30:54Z",
   published: "2024-05-01T15:30:35Z",
   references: [
      {
         type: "ADVISORY",
         url: "https://nvd.nist.gov/vuln/detail/CVE-2024-27032",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/21ec68234826b1b54ab980a8df6e33c74cfbee58",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/8844b2f8a3f0c428b74672f9726f9950b1a7764c",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/d034810d02a5af8eb74debe29877dcaf5f00fdd1",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/f26091a981318b5b7451d61f99bc073a6af8db67",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/fe4de493572a4263554903bf9c3afc5c196e15f0",
      },
   ],
   schema_version: "1.4.0",
   severity: [
      {
         score: "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:H",
         type: "CVSS_V3",
      },
   ],
}


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.


Loading…

Loading…

Loading…

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.