GHSA-H7FH-M822-XW4C

Vulnerability from github – Published: 2024-10-21 15:32 – Updated: 2024-10-21 15:32
VLAI?
Details

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

dm-verity: restart or panic on an I/O error

Maxim Suhanov reported that dm-verity doesn't crash if an I/O error happens. In theory, this could be used to subvert security, because an attacker can create sectors that return error with the Write Uncorrectable command. Some programs may misbehave if they have to deal with EIO.

This commit fixes dm-verity, so that if "panic_on_corruption" or "restart_on_corruption" was specified and an I/O error happens, the machine will panic or restart.

This commit also changes kernel_restart to emergency_restart - kernel_restart calls reboot notifiers and these reboot notifiers may wait for the bio that failed. emergency_restart doesn't call the notifiers.

Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2024-47725"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2024-10-21T13:15:02Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\ndm-verity: restart or panic on an I/O error\n\nMaxim Suhanov reported that dm-verity doesn\u0027t crash if an I/O error\nhappens. In theory, this could be used to subvert security, because an\nattacker can create sectors that return error with the Write Uncorrectable\ncommand. Some programs may misbehave if they have to deal with EIO.\n\nThis commit fixes dm-verity, so that if \"panic_on_corruption\" or\n\"restart_on_corruption\" was specified and an I/O error happens, the\nmachine will panic or restart.\n\nThis commit also changes kernel_restart to emergency_restart -\nkernel_restart calls reboot notifiers and these reboot notifiers may wait\nfor the bio that failed. emergency_restart doesn\u0027t call the notifiers.",
  "id": "GHSA-h7fh-m822-xw4c",
  "modified": "2024-10-21T15:32:26Z",
  "published": "2024-10-21T15:32:26Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47725"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/338b32a232bbee39e52dd1486cbc0c9f458d4d69"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/b332bcca59143cfdd000957f8b78c28dd2ac1da4"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/cada2646b7483cce370eb3b046659df31d9d34d1"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/e6a3531dd542cb127c8de32ab1e54a48ae19962b"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Detection rules are retrieved from Rulezet.