fkie_cve-2023-53256
Vulnerability from fkie_nvd
Published
2025-09-15 15:15
Modified
2025-09-15 15:22
Severity ?
Summary
In the Linux kernel, the following vulnerability has been resolved: firmware: arm_ffa: Fix FFA device names for logical partitions Each physical partition can provide multiple services each with UUID. Each such service can be presented as logical partition with a unique combination of VM ID and UUID. The number of distinct UUID in a system will be less than or equal to the number of logical partitions. However, currently it fails to register more than one logical partition or service within a physical partition as the device name contains only VM ID while both VM ID and UUID are maintained in the partition information. The kernel complains with the below message: | sysfs: cannot create duplicate filename '/devices/arm-ffa-8001' | CPU: 1 PID: 1 Comm: swapper/0 Not tainted 6.3.0-rc7 #8 | Hardware name: FVP Base RevC (DT) | Call trace: | dump_backtrace+0xf8/0x118 | show_stack+0x18/0x24 | dump_stack_lvl+0x50/0x68 | dump_stack+0x18/0x24 | sysfs_create_dir_ns+0xe0/0x13c | kobject_add_internal+0x220/0x3d4 | kobject_add+0x94/0x100 | device_add+0x144/0x5d8 | device_register+0x20/0x30 | ffa_device_register+0x88/0xd8 | ffa_setup_partitions+0x108/0x1b8 | ffa_init+0x2ec/0x3a4 | do_one_initcall+0xcc/0x240 | do_initcall_level+0x8c/0xac | do_initcalls+0x54/0x94 | do_basic_setup+0x1c/0x28 | kernel_init_freeable+0x100/0x16c | kernel_init+0x20/0x1a0 | ret_from_fork+0x10/0x20 | kobject_add_internal failed for arm-ffa-8001 with -EEXIST, don't try to | register things with the same name in the same directory. | arm_ffa arm-ffa: unable to register device arm-ffa-8001 err=-17 | ARM FF-A: ffa_setup_partitions: failed to register partition ID 0x8001 By virtue of being random enough to avoid collisions when generated in a distributed system, there is no way to compress UUID keys to the number of bits required to identify each. We can eliminate '-' in the name but it is not worth eliminating 4 bytes and add unnecessary logic for doing that. Also v1.0 doesn't provide the UUID of the partitions which makes it hard to use the same for the device name. So to keep it simple, let us alloc an ID using ida_alloc() and append the same to "arm-ffa" to make up a unique device name. Also stash the id value in ffa_dev to help freeing the ID later when the device is destroyed.
References
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/19b8766459c41c6f318f8a548cc1c66dffd18363
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/93d0cbe88118fcef234d3ebcbdadcb9ebe9d34f1
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/c2f65991097a62efbdb2bed3c06fc86b08c9593b
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/dfc5aaa57f52a5800c339369d235fa30fb734feb
Impacted products
Vendor Product Version


To clipboard 

{
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nfirmware: arm_ffa: Fix FFA device names for logical partitions\n\nEach physical partition can provide multiple services each with UUID.\nEach such service can be presented as logical partition with a unique\ncombination of VM ID and UUID. The number of distinct UUID in a system\nwill be less than or equal to the number of logical partitions.\n\nHowever, currently it fails to register more than one logical partition\nor service within a physical partition as the device name contains only\nVM ID while both VM ID and UUID are maintained in the partition information.\nThe kernel complains with the below message:\n\n  | sysfs: cannot create duplicate filename \u0027/devices/arm-ffa-8001\u0027\n  | CPU: 1 PID: 1 Comm: swapper/0 Not tainted 6.3.0-rc7 #8\n  | Hardware name: FVP Base RevC (DT)\n  | Call trace:\n  |  dump_backtrace+0xf8/0x118\n  |  show_stack+0x18/0x24\n  |  dump_stack_lvl+0x50/0x68\n  |  dump_stack+0x18/0x24\n  |  sysfs_create_dir_ns+0xe0/0x13c\n  |  kobject_add_internal+0x220/0x3d4\n  |  kobject_add+0x94/0x100\n  |  device_add+0x144/0x5d8\n  |  device_register+0x20/0x30\n  |  ffa_device_register+0x88/0xd8\n  |  ffa_setup_partitions+0x108/0x1b8\n  |  ffa_init+0x2ec/0x3a4\n  |  do_one_initcall+0xcc/0x240\n  |  do_initcall_level+0x8c/0xac\n  |  do_initcalls+0x54/0x94\n  |  do_basic_setup+0x1c/0x28\n  |  kernel_init_freeable+0x100/0x16c\n  |  kernel_init+0x20/0x1a0\n  |  ret_from_fork+0x10/0x20\n  | kobject_add_internal failed for arm-ffa-8001 with -EEXIST, don\u0027t try to\n  | register things with the same name in the same directory.\n  | arm_ffa arm-ffa: unable to register device arm-ffa-8001 err=-17\n  | ARM FF-A: ffa_setup_partitions: failed to register partition ID 0x8001\n\nBy virtue of being random enough to avoid collisions when generated in a\ndistributed system, there is no way to compress UUID keys to the number\nof bits required to identify each. We can eliminate \u0027-\u0027 in the name but\nit is not worth eliminating 4 bytes and add unnecessary logic for doing\nthat. Also v1.0 doesn\u0027t provide the UUID of the partitions which makes\nit hard to use the same for the device name.\n\nSo to keep it simple, let us alloc an ID using ida_alloc() and append the\nsame to \"arm-ffa\" to make up a unique device name. Also stash the id value\nin ffa_dev to help freeing the ID later when the device is destroyed."
    }
  ],
  "id": "CVE-2023-53256",
  "lastModified": "2025-09-15T15:22:27.090",
  "metrics": {},
  "published": "2025-09-15T15:15:52.980",
  "references": [
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/19b8766459c41c6f318f8a548cc1c66dffd18363"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/93d0cbe88118fcef234d3ebcbdadcb9ebe9d34f1"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/c2f65991097a62efbdb2bed3c06fc86b08c9593b"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/dfc5aaa57f52a5800c339369d235fa30fb734feb"
    }
  ],
  "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
  "vulnStatus": "Awaiting Analysis"
}


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