fkie_cve-2024-50042
Vulnerability from fkie_nvd
Published
2024-10-21 20:15
Modified
2024-11-22 17:21
Severity ?
7.1 (High) - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
Summary
In the Linux kernel, the following vulnerability has been resolved: ice: Fix increasing MSI-X on VF Increasing MSI-X value on a VF leads to invalid memory operations. This is caused by not reallocating some arrays. Reproducer: modprobe ice echo 0 > /sys/bus/pci/devices/$PF_PCI/sriov_drivers_autoprobe echo 1 > /sys/bus/pci/devices/$PF_PCI/sriov_numvfs echo 17 > /sys/bus/pci/devices/$VF0_PCI/sriov_vf_msix_count Default MSI-X is 16, so 17 and above triggers this issue. KASAN reports: BUG: KASAN: slab-out-of-bounds in ice_vsi_alloc_ring_stats+0x38d/0x4b0 [ice] Read of size 8 at addr ffff8888b937d180 by task bash/28433 (...) Call Trace: (...) ? ice_vsi_alloc_ring_stats+0x38d/0x4b0 [ice] kasan_report+0xed/0x120 ? ice_vsi_alloc_ring_stats+0x38d/0x4b0 [ice] ice_vsi_alloc_ring_stats+0x38d/0x4b0 [ice] ice_vsi_cfg_def+0x3360/0x4770 [ice] ? mutex_unlock+0x83/0xd0 ? __pfx_ice_vsi_cfg_def+0x10/0x10 [ice] ? __pfx_ice_remove_vsi_lkup_fltr+0x10/0x10 [ice] ice_vsi_cfg+0x7f/0x3b0 [ice] ice_vf_reconfig_vsi+0x114/0x210 [ice] ice_sriov_set_msix_vec_count+0x3d0/0x960 [ice] sriov_vf_msix_count_store+0x21c/0x300 (...) Allocated by task 28201: (...) ice_vsi_cfg_def+0x1c8e/0x4770 [ice] ice_vsi_cfg+0x7f/0x3b0 [ice] ice_vsi_setup+0x179/0xa30 [ice] ice_sriov_configure+0xcaa/0x1520 [ice] sriov_numvfs_store+0x212/0x390 (...) To fix it, use ice_vsi_rebuild() instead of ice_vf_reconfig_vsi(). This causes the required arrays to be reallocated taking the new queue count into account (ice_vsi_realloc_stat_arrays()). Set req_txq and req_rxq before ice_vsi_rebuild(), so that realloc uses the newly set queue count. Additionally, ice_vsi_rebuild() does not remove VSI filters (ice_fltr_remove_all()), so ice_vf_init_host_cfg() is no longer necessary.
References
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/bce9af1b030bf59d51bbabf909a3ef164787e44ePatch
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/cbda6197929418fabf0e45ecf9b7a76360944c70Patch
Impacted products
Vendor Product Version
linux linux_kernel *
linux linux_kernel *
linux linux_kernel 6.12
linux linux_kernel 6.12


To clipboard 

{
   configurations: [
      {
         nodes: [
            {
               cpeMatch: [
                  {
                     criteria: "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                     matchCriteriaId: "15130BF0-E913-4EC3-B479-B8FA35896797",
                     versionEndExcluding: "6.8",
                     versionStartIncluding: "6.7.10",
                     vulnerable: true,
                  },
                  {
                     criteria: "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                     matchCriteriaId: "C354E062-80AD-4947-809C-E798BC6AAA39",
                     versionEndExcluding: "6.11.4",
                     versionStartIncluding: "6.8",
                     vulnerable: true,
                  },
                  {
                     criteria: "cpe:2.3:o:linux:linux_kernel:6.12:rc1:*:*:*:*:*:*",
                     matchCriteriaId: "7F361E1D-580F-4A2D-A509-7615F73167A1",
                     vulnerable: true,
                  },
                  {
                     criteria: "cpe:2.3:o:linux:linux_kernel:6.12:rc2:*:*:*:*:*:*",
                     matchCriteriaId: "925478D0-3E3D-4E6F-ACD5-09F28D5DF82C",
                     vulnerable: true,
                  },
               ],
               negate: false,
               operator: "OR",
            },
         ],
      },
   ],
   cveTags: [],
   descriptions: [
      {
         lang: "en",
         value: "In the Linux kernel, the following vulnerability has been resolved:\n\nice: Fix increasing MSI-X on VF\n\nIncreasing MSI-X value on a VF leads to invalid memory operations. This\nis caused by not reallocating some arrays.\n\nReproducer:\n  modprobe ice\n  echo 0 > /sys/bus/pci/devices/$PF_PCI/sriov_drivers_autoprobe\n  echo 1 > /sys/bus/pci/devices/$PF_PCI/sriov_numvfs\n  echo 17 > /sys/bus/pci/devices/$VF0_PCI/sriov_vf_msix_count\n\nDefault MSI-X is 16, so 17 and above triggers this issue.\n\nKASAN reports:\n\n  BUG: KASAN: slab-out-of-bounds in ice_vsi_alloc_ring_stats+0x38d/0x4b0 [ice]\n  Read of size 8 at addr ffff8888b937d180 by task bash/28433\n  (...)\n\n  Call Trace:\n   (...)\n   ? ice_vsi_alloc_ring_stats+0x38d/0x4b0 [ice]\n   kasan_report+0xed/0x120\n   ? ice_vsi_alloc_ring_stats+0x38d/0x4b0 [ice]\n   ice_vsi_alloc_ring_stats+0x38d/0x4b0 [ice]\n   ice_vsi_cfg_def+0x3360/0x4770 [ice]\n   ? mutex_unlock+0x83/0xd0\n   ? __pfx_ice_vsi_cfg_def+0x10/0x10 [ice]\n   ? __pfx_ice_remove_vsi_lkup_fltr+0x10/0x10 [ice]\n   ice_vsi_cfg+0x7f/0x3b0 [ice]\n   ice_vf_reconfig_vsi+0x114/0x210 [ice]\n   ice_sriov_set_msix_vec_count+0x3d0/0x960 [ice]\n   sriov_vf_msix_count_store+0x21c/0x300\n   (...)\n\n  Allocated by task 28201:\n   (...)\n   ice_vsi_cfg_def+0x1c8e/0x4770 [ice]\n   ice_vsi_cfg+0x7f/0x3b0 [ice]\n   ice_vsi_setup+0x179/0xa30 [ice]\n   ice_sriov_configure+0xcaa/0x1520 [ice]\n   sriov_numvfs_store+0x212/0x390\n   (...)\n\nTo fix it, use ice_vsi_rebuild() instead of ice_vf_reconfig_vsi(). This\ncauses the required arrays to be reallocated taking the new queue count\ninto account (ice_vsi_realloc_stat_arrays()). Set req_txq and req_rxq\nbefore ice_vsi_rebuild(), so that realloc uses the newly set queue\ncount.\n\nAdditionally, ice_vsi_rebuild() does not remove VSI filters\n(ice_fltr_remove_all()), so ice_vf_init_host_cfg() is no longer\nnecessary.",
      },
      {
         lang: "es",
         value: "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: ice: Fix increasing MSI-X on VF Aumentar el valor de MSI-X en un VF conduce a operaciones de memoria no válidas. Esto se debe a que no se reasignan algunas matrices. Reproductor: modprobe ice echo 0 > /sys/bus/pci/devices/$PF_PCI/sriov_drivers_autoprobe echo 1 > /sys/bus/pci/devices/$PF_PCI/sriov_numvfs echo 17 > /sys/bus/pci/devices/$VF0_PCI/sriov_vf_msix_count El MSI-X predeterminado es 16, por lo que 17 y superior desencadenan este problema. KASAN informa: ERROR: KASAN: slab fuera de los límites en ice_vsi_alloc_ring_stats+0x38d/0x4b0 [ice] Lectura de tamaño 8 en la dirección ffff8888b937d180 por la tarea bash/28433 (...) Seguimiento de llamadas: (...) ? ice_vsi_alloc_ring_stats+0x38d/0x4b0 [ice] kasan_report+0xed/0x120 ? ice_vsi_alloc_ring_stats+0x38d/0x4b0 [ice] ice_vsi_alloc_ring_stats+0x38d/0x4b0 [ice] ice_vsi_alloc_ring_stats+0x38d/0x4b0 [ice] ice_vsi_cfg_def+0x3360/0x4770 [ice] ? mutex_unlock+0x83/0xd0 ? __pfx_ice_vsi_cfg_def+0x10/0x10 [hielo] ? __pfx_ice_remove_vsi_lkup_fltr+0x10/0x10 [hielo] ice_vsi_cfg+0x7f/0x3b0 [hielo] ice_vf_reconfig_vsi+0x114/0x210 [hielo] ice_sriov_set_msix_vec_count+0x3d0/0x960 [hielo] sriov_vf_msix_count_store+0x21c/0x300 (...) Asignado por la tarea 28201: (...) ice_vsi_cfg_def+0x1c8e/0x4770 [hielo] ice_vsi_cfg+0x7f/0x3b0 [hielo] ice_vsi_setup+0x179/0xa30 [hielo] ice_sriov_configure+0xcaa/0x1520 [ice] sriov_numvfs_store+0x212/0x390 (...) Para solucionarlo, utilice ice_vsi_rebuild() en lugar de ice_vf_reconfig_vsi(). Esto hace que las matrices requeridas se reasignen teniendo en cuenta el nuevo recuento de colas (ice_vsi_realloc_stat_arrays()). Establezca req_txq y req_rxq antes de ice_vsi_rebuild(), de modo que realloc utilice el nuevo recuento de colas establecido. Además, ice_vsi_rebuild() no elimina los filtros VSI (ice_fltr_remove_all()), por lo que ice_vf_init_host_cfg() ya no es necesario.",
      },
   ],
   id: "CVE-2024-50042",
   lastModified: "2024-11-22T17:21:37.140",
   metrics: {
      cvssMetricV31: [
         {
            cvssData: {
               attackComplexity: "LOW",
               attackVector: "LOCAL",
               availabilityImpact: "HIGH",
               baseScore: 7.1,
               baseSeverity: "HIGH",
               confidentialityImpact: "HIGH",
               integrityImpact: "NONE",
               privilegesRequired: "LOW",
               scope: "UNCHANGED",
               userInteraction: "NONE",
               vectorString: "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H",
               version: "3.1",
            },
            exploitabilityScore: 1.8,
            impactScore: 5.2,
            source: "nvd@nist.gov",
            type: "Primary",
         },
      ],
   },
   published: "2024-10-21T20:15:17.200",
   references: [
      {
         source: "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
         tags: [
            "Patch",
         ],
         url: "https://git.kernel.org/stable/c/bce9af1b030bf59d51bbabf909a3ef164787e44e",
      },
      {
         source: "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
         tags: [
            "Patch",
         ],
         url: "https://git.kernel.org/stable/c/cbda6197929418fabf0e45ecf9b7a76360944c70",
      },
   ],
   sourceIdentifier: "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
   vulnStatus: "Analyzed",
   weaknesses: [
      {
         description: [
            {
               lang: "en",
               value: "CWE-125",
            },
         ],
         source: "nvd@nist.gov",
         type: "Primary",
      },
   ],
}


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.