ghsa-pm64-f9ff-xc6w
Vulnerability from github
Published
2024-12-27 15:31
Modified
2025-01-14 18:31
Severity ?
5.5 (Medium) - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Details

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

isofs: avoid memory leak in iocharset

A memleak was found as below:

unreferenced object 0xffff0000d10164d8 (size 8): comm "pool-udisksd", pid 108217, jiffies 4295408555 hex dump (first 8 bytes): 75 74 66 38 00 cc cc cc utf8.... backtrace (crc de430d31): [] kmemleak_alloc+0xb8/0xc8 [] __kmalloc_node_track_caller_noprof+0x380/0x474 [] kstrdup+0x70/0xfc [] isofs_parse_param+0x228/0x2c0 [isofs] [] vfs_parse_fs_param+0xf4/0x164 [] vfs_parse_fs_string+0x8c/0xd4 [] vfs_parse_monolithic_sep+0xb0/0xfc [] generic_parse_monolithic+0x30/0x3c [] parse_monolithic_mount_data+0x40/0x4c [] path_mount+0x6c4/0x9ec [] do_mount+0xac/0xc4 [] __arm64_sys_mount+0x16c/0x2b0 [] invoke_syscall+0x7c/0x104 [] el0_svc_common.constprop.1+0xe0/0x104 [] do_el0_svc+0x2c/0x38 [] el0_svc+0x3c/0x1b8

The opt->iocharset is freed inside the isofs_fill_super function, But there may be situations where it's not possible to enter this function.

For example, in the get_tree_bdev_flags function,when encountering the situation where "Can't mount, would change RO state," In such a case, isofs_fill_super will not have the opportunity to be called,which means that opt->iocharset will not have the chance to be freed,ultimately leading to a memory leak.

Let's move the memory freeing of opt->iocharset into isofs_free_fc function.

Show details on source website

To clipboard 

{
   affected: [],
   aliases: [
      "CVE-2024-56534",
   ],
   database_specific: {
      cwe_ids: [
         "CWE-401",
      ],
      github_reviewed: false,
      github_reviewed_at: null,
      nvd_published_at: "2024-12-27T14:15:32Z",
      severity: "MODERATE",
   },
   details: "In the Linux kernel, the following vulnerability has been resolved:\n\nisofs: avoid memory leak in iocharset\n\nA memleak was found as below:\n\nunreferenced object 0xffff0000d10164d8 (size 8):\n  comm \"pool-udisksd\", pid 108217, jiffies 4295408555\n  hex dump (first 8 bytes):\n    75 74 66 38 00 cc cc cc                          utf8....\n  backtrace (crc de430d31):\n    [<ffff800081046e6c>] kmemleak_alloc+0xb8/0xc8\n    [<ffff8000803e6c3c>] __kmalloc_node_track_caller_noprof+0x380/0x474\n    [<ffff800080363b74>] kstrdup+0x70/0xfc\n    [<ffff80007bb3c6a4>] isofs_parse_param+0x228/0x2c0 [isofs]\n    [<ffff8000804d7f68>] vfs_parse_fs_param+0xf4/0x164\n    [<ffff8000804d8064>] vfs_parse_fs_string+0x8c/0xd4\n    [<ffff8000804d815c>] vfs_parse_monolithic_sep+0xb0/0xfc\n    [<ffff8000804d81d8>] generic_parse_monolithic+0x30/0x3c\n    [<ffff8000804d8bfc>] parse_monolithic_mount_data+0x40/0x4c\n    [<ffff8000804b6a64>] path_mount+0x6c4/0x9ec\n    [<ffff8000804b6e38>] do_mount+0xac/0xc4\n    [<ffff8000804b7494>] __arm64_sys_mount+0x16c/0x2b0\n    [<ffff80008002b8dc>] invoke_syscall+0x7c/0x104\n    [<ffff80008002ba44>] el0_svc_common.constprop.1+0xe0/0x104\n    [<ffff80008002ba94>] do_el0_svc+0x2c/0x38\n    [<ffff800081041108>] el0_svc+0x3c/0x1b8\n\nThe opt->iocharset is freed inside the isofs_fill_super function,\nBut there may be situations where it's not possible to\nenter this function.\n\nFor example, in the get_tree_bdev_flags function,when\nencountering the situation where \"Can't mount, would change RO state,\"\nIn such a case, isofs_fill_super will not have the opportunity\nto be called,which means that opt->iocharset will not have the chance\nto be freed,ultimately leading to a memory leak.\n\nLet's move the memory freeing of opt->iocharset into\nisofs_free_fc function.",
   id: "GHSA-pm64-f9ff-xc6w",
   modified: "2025-01-14T18:31:54Z",
   published: "2024-12-27T15:31:53Z",
   references: [
      {
         type: "ADVISORY",
         url: "https://nvd.nist.gov/vuln/detail/CVE-2024-56534",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/0b5bbeee4de616a268db77e2f40f19ab010a367b",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/0fbab266ca8000333c966f5b58cb9b9cac658573",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/34f090ddb3630a26e5a6b220bf3bfaf5c7b70393",
      },
   ],
   schema_version: "1.4.0",
   severity: [
      {
         score: "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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.




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.