cve-2024-56565
Vulnerability from cvelistv5
Published
2024-12-27 14:23
Modified
2025-01-20 06:23
Severity ?
EPSS score ?
0.03% (0.06317)
Summary
In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to drop all discards after creating snapshot on lvm device Piergiorgio reported a bug in bugzilla as below: ------------[ cut here ]------------ WARNING: CPU: 2 PID: 969 at fs/f2fs/segment.c:1330 RIP: 0010:__submit_discard_cmd+0x27d/0x400 [f2fs] Call Trace: __issue_discard_cmd+0x1ca/0x350 [f2fs] issue_discard_thread+0x191/0x480 [f2fs] kthread+0xcf/0x100 ret_from_fork+0x31/0x50 ret_from_fork_asm+0x1a/0x30 w/ below testcase, it can reproduce this bug quickly: - pvcreate /dev/vdb - vgcreate myvg1 /dev/vdb - lvcreate -L 1024m -n mylv1 myvg1 - mount /dev/myvg1/mylv1 /mnt/f2fs - dd if=/dev/zero of=/mnt/f2fs/file bs=1M count=20 - sync - rm /mnt/f2fs/file - sync - lvcreate -L 1024m -s -n mylv1-snapshot /dev/myvg1/mylv1 - umount /mnt/f2fs The root cause is: it will update discard_max_bytes of mounted lvm device to zero after creating snapshot on this lvm device, then, __submit_discard_cmd() will pass parameter @nr_sects w/ zero value to __blkdev_issue_discard(), it returns a NULL bio pointer, result in panic. This patch changes as below for fixing: 1. Let's drop all remained discards in f2fs_unfreeze() if snapshot of lvm device is created. 2. Checking discard_max_bytes before submitting discard during __submit_discard_cmd().
References
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/15136c3861a3341db261ebdbb6ae4ae1765635e2
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/bc8aeb04fd80cb8cfae3058445c84410fd0beb5e
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/ed24ab98242f8d22b66fbe0452c97751b5ea4e22
Impacted products
Vendor Product Version
Linux Linux Version: 35ec7d5748849762008e8ae9f8ad2766229d5794
Version: 35ec7d5748849762008e8ae9f8ad2766229d5794
Version: 35ec7d5748849762008e8ae9f8ad2766229d5794
 Create a notification for this product.
   Linux Linux Version: 4.19
 Create a notification for this product.
Show details on NVD website

To clipboard 

{
   containers: {
      cna: {
         affected: [
            {
               defaultStatus: "unaffected",
               product: "Linux",
               programFiles: [
                  "fs/f2fs/segment.c",
                  "fs/f2fs/super.c",
               ],
               repo: "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
               vendor: "Linux",
               versions: [
                  {
                     lessThan: "ed24ab98242f8d22b66fbe0452c97751b5ea4e22",
                     status: "affected",
                     version: "35ec7d5748849762008e8ae9f8ad2766229d5794",
                     versionType: "git",
                  },
                  {
                     lessThan: "15136c3861a3341db261ebdbb6ae4ae1765635e2",
                     status: "affected",
                     version: "35ec7d5748849762008e8ae9f8ad2766229d5794",
                     versionType: "git",
                  },
                  {
                     lessThan: "bc8aeb04fd80cb8cfae3058445c84410fd0beb5e",
                     status: "affected",
                     version: "35ec7d5748849762008e8ae9f8ad2766229d5794",
                     versionType: "git",
                  },
               ],
            },
            {
               defaultStatus: "affected",
               product: "Linux",
               programFiles: [
                  "fs/f2fs/segment.c",
                  "fs/f2fs/super.c",
               ],
               repo: "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
               vendor: "Linux",
               versions: [
                  {
                     status: "affected",
                     version: "4.19",
                  },
                  {
                     lessThan: "4.19",
                     status: "unaffected",
                     version: "0",
                     versionType: "semver",
                  },
                  {
                     lessThanOrEqual: "6.6.*",
                     status: "unaffected",
                     version: "6.6.66",
                     versionType: "semver",
                  },
                  {
                     lessThanOrEqual: "6.12.*",
                     status: "unaffected",
                     version: "6.12.4",
                     versionType: "semver",
                  },
                  {
                     lessThanOrEqual: "*",
                     status: "unaffected",
                     version: "6.13",
                     versionType: "original_commit_for_fix",
                  },
               ],
            },
         ],
         descriptions: [
            {
               lang: "en",
               value: "In the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: fix to drop all discards after creating snapshot on lvm device\n\nPiergiorgio reported a bug in bugzilla as below:\n\n------------[ cut here ]------------\nWARNING: CPU: 2 PID: 969 at fs/f2fs/segment.c:1330\nRIP: 0010:__submit_discard_cmd+0x27d/0x400 [f2fs]\nCall Trace:\n __issue_discard_cmd+0x1ca/0x350 [f2fs]\n issue_discard_thread+0x191/0x480 [f2fs]\n kthread+0xcf/0x100\n ret_from_fork+0x31/0x50\n ret_from_fork_asm+0x1a/0x30\n\nw/ below testcase, it can reproduce this bug quickly:\n- pvcreate /dev/vdb\n- vgcreate myvg1 /dev/vdb\n- lvcreate -L 1024m -n mylv1 myvg1\n- mount /dev/myvg1/mylv1 /mnt/f2fs\n- dd if=/dev/zero of=/mnt/f2fs/file bs=1M count=20\n- sync\n- rm /mnt/f2fs/file\n- sync\n- lvcreate -L 1024m -s -n mylv1-snapshot /dev/myvg1/mylv1\n- umount /mnt/f2fs\n\nThe root cause is: it will update discard_max_bytes of mounted lvm\ndevice to zero after creating snapshot on this lvm device, then,\n__submit_discard_cmd() will pass parameter @nr_sects w/ zero value\nto __blkdev_issue_discard(), it returns a NULL bio pointer, result\nin panic.\n\nThis patch changes as below for fixing:\n1. Let's drop all remained discards in f2fs_unfreeze() if snapshot\nof lvm device is created.\n2. Checking discard_max_bytes before submitting discard during\n__submit_discard_cmd().",
            },
         ],
         providerMetadata: {
            dateUpdated: "2025-01-20T06:23:11.317Z",
            orgId: "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            shortName: "Linux",
         },
         references: [
            {
               url: "https://git.kernel.org/stable/c/ed24ab98242f8d22b66fbe0452c97751b5ea4e22",
            },
            {
               url: "https://git.kernel.org/stable/c/15136c3861a3341db261ebdbb6ae4ae1765635e2",
            },
            {
               url: "https://git.kernel.org/stable/c/bc8aeb04fd80cb8cfae3058445c84410fd0beb5e",
            },
         ],
         title: "f2fs: fix to drop all discards after creating snapshot on lvm device",
         x_generator: {
            engine: "bippy-5f407fcff5a0",
         },
      },
   },
   cveMetadata: {
      assignerOrgId: "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      assignerShortName: "Linux",
      cveId: "CVE-2024-56565",
      datePublished: "2024-12-27T14:23:09.350Z",
      dateReserved: "2024-12-27T14:03:05.995Z",
      dateUpdated: "2025-01-20T06:23:11.317Z",
      state: "PUBLISHED",
   },
   dataType: "CVE_RECORD",
   dataVersion: "5.1",
   "vulnerability-lookup:meta": {
      nvd: "{\"cve\":{\"id\":\"CVE-2024-56565\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2024-12-27T15:15:15.400\",\"lastModified\":\"2024-12-27T15:15:15.400\",\"vulnStatus\":\"Received\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nf2fs: fix to drop all discards after creating snapshot on lvm device\\n\\nPiergiorgio reported a bug in bugzilla as below:\\n\\n------------[ cut here ]------------\\nWARNING: CPU: 2 PID: 969 at fs/f2fs/segment.c:1330\\nRIP: 0010:__submit_discard_cmd+0x27d/0x400 [f2fs]\\nCall Trace:\\n __issue_discard_cmd+0x1ca/0x350 [f2fs]\\n issue_discard_thread+0x191/0x480 [f2fs]\\n kthread+0xcf/0x100\\n ret_from_fork+0x31/0x50\\n ret_from_fork_asm+0x1a/0x30\\n\\nw/ below testcase, it can reproduce this bug quickly:\\n- pvcreate /dev/vdb\\n- vgcreate myvg1 /dev/vdb\\n- lvcreate -L 1024m -n mylv1 myvg1\\n- mount /dev/myvg1/mylv1 /mnt/f2fs\\n- dd if=/dev/zero of=/mnt/f2fs/file bs=1M count=20\\n- sync\\n- rm /mnt/f2fs/file\\n- sync\\n- lvcreate -L 1024m -s -n mylv1-snapshot /dev/myvg1/mylv1\\n- umount /mnt/f2fs\\n\\nThe root cause is: it will update discard_max_bytes of mounted lvm\\ndevice to zero after creating snapshot on this lvm device, then,\\n__submit_discard_cmd() will pass parameter @nr_sects w/ zero value\\nto __blkdev_issue_discard(), it returns a NULL bio pointer, result\\nin panic.\\n\\nThis patch changes as below for fixing:\\n1. Let's drop all remained discards in f2fs_unfreeze() if snapshot\\nof lvm device is created.\\n2. Checking discard_max_bytes before submitting discard during\\n__submit_discard_cmd().\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/15136c3861a3341db261ebdbb6ae4ae1765635e2\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/bc8aeb04fd80cb8cfae3058445c84410fd0beb5e\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/ed24ab98242f8d22b66fbe0452c97751b5ea4e22\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}",
   },
}


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.