CVE-2024-35818 (GCVE-0-2024-35818)
Vulnerability from cvelistv5
Published
2024-05-17 13:23
Modified
2024-12-19 08:55
Severity ?
Summary
In the Linux kernel, the following vulnerability has been resolved: LoongArch: Define the __io_aw() hook as mmiowb() Commit fb24ea52f78e0d595852e ("drivers: Remove explicit invocations of mmiowb()") remove all mmiowb() in drivers, but it says: "NOTE: mmiowb() has only ever guaranteed ordering in conjunction with spin_unlock(). However, pairing each mmiowb() removal in this patch with the corresponding call to spin_unlock() is not at all trivial, so there is a small chance that this change may regress any drivers incorrectly relying on mmiowb() to order MMIO writes between CPUs using lock-free synchronisation." The mmio in radeon_ring_commit() is protected by a mutex rather than a spinlock, but in the mutex fastpath it behaves similar to spinlock. We can add mmiowb() calls in the radeon driver but the maintainer says he doesn't like such a workaround, and radeon is not the only example of mutex protected mmio. So we should extend the mmiowb tracking system from spinlock to mutex, and maybe other locking primitives. This is not easy and error prone, so we solve it in the architectural code, by simply defining the __io_aw() hook as mmiowb(). And we no longer need to override queued_spin_unlock() so use the generic definition. Without this, we get such an error when run 'glxgears' on weak ordering architectures such as LoongArch: radeon 0000:04:00.0: ring 0 stalled for more than 10324msec radeon 0000:04:00.0: ring 3 stalled for more than 10240msec radeon 0000:04:00.0: GPU lockup (current fence id 0x000000000001f412 last fence id 0x000000000001f414 on ring 3) radeon 0000:04:00.0: GPU lockup (current fence id 0x000000000000f940 last fence id 0x000000000000f941 on ring 0) radeon 0000:04:00.0: scheduling IB failed (-35). [drm:radeon_gem_va_ioctl [radeon]] *ERROR* Couldn't update BO_VA (-35) radeon 0000:04:00.0: scheduling IB failed (-35). [drm:radeon_gem_va_ioctl [radeon]] *ERROR* Couldn't update BO_VA (-35) radeon 0000:04:00.0: scheduling IB failed (-35). [drm:radeon_gem_va_ioctl [radeon]] *ERROR* Couldn't update BO_VA (-35) radeon 0000:04:00.0: scheduling IB failed (-35). [drm:radeon_gem_va_ioctl [radeon]] *ERROR* Couldn't update BO_VA (-35) radeon 0000:04:00.0: scheduling IB failed (-35). [drm:radeon_gem_va_ioctl [radeon]] *ERROR* Couldn't update BO_VA (-35) radeon 0000:04:00.0: scheduling IB failed (-35). [drm:radeon_gem_va_ioctl [radeon]] *ERROR* Couldn't update BO_VA (-35) radeon 0000:04:00.0: scheduling IB failed (-35). [drm:radeon_gem_va_ioctl [radeon]] *ERROR* Couldn't update BO_VA (-35)
References
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/0b61a7dc6712b78799b3949997e8a5e94db5c4b0
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/97cd43ba824aec764f5ea2790d0c0a318f885167
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/9adec248bba33b1503252caf8e59d81febfc5ceb
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/9c68ece8b2a5c5ff9b2fcaea923dd73efeb174cd
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/d7d7c6cdea875be3b241d7d39873bb431db7154d
af854a3a-2127-422b-91ae-364da2661108https://git.kernel.org/stable/c/0b61a7dc6712b78799b3949997e8a5e94db5c4b0
af854a3a-2127-422b-91ae-364da2661108https://git.kernel.org/stable/c/97cd43ba824aec764f5ea2790d0c0a318f885167
af854a3a-2127-422b-91ae-364da2661108https://git.kernel.org/stable/c/9adec248bba33b1503252caf8e59d81febfc5ceb
af854a3a-2127-422b-91ae-364da2661108https://git.kernel.org/stable/c/9c68ece8b2a5c5ff9b2fcaea923dd73efeb174cd
af854a3a-2127-422b-91ae-364da2661108https://git.kernel.org/stable/c/d7d7c6cdea875be3b241d7d39873bb431db7154d
Impacted products
Vendor Product Version
Linux Linux Version: fa96b57c149061f71a70bd6582d995f6424fbbf4
Version: fa96b57c149061f71a70bd6582d995f6424fbbf4
Version: fa96b57c149061f71a70bd6582d995f6424fbbf4
Version: fa96b57c149061f71a70bd6582d995f6424fbbf4
Version: fa96b57c149061f71a70bd6582d995f6424fbbf4
 Create a notification for this product.
   Linux Linux Version: 5.19
 Create a notification for this product.
Show details on NVD website

To clipboard 

{
   containers: {
      adp: [
         {
            metrics: [
               {
                  other: {
                     content: {
                        id: "CVE-2024-35818",
                        options: [
                           {
                              Exploitation: "none",
                           },
                           {
                              Automatable: "no",
                           },
                           {
                              "Technical Impact": "partial",
                           },
                        ],
                        role: "CISA Coordinator",
                        timestamp: "2024-06-17T17:39:17.575146Z",
                        version: "2.0.3",
                     },
                     type: "ssvc",
                  },
               },
            ],
            providerMetadata: {
               dateUpdated: "2024-06-17T17:43:13.960Z",
               orgId: "134c704f-9b21-4f2e-91b3-4a467353bcc0",
               shortName: "CISA-ADP",
            },
            title: "CISA ADP Vulnrichment",
         },
         {
            providerMetadata: {
               dateUpdated: "2024-08-02T03:21:47.482Z",
               orgId: "af854a3a-2127-422b-91ae-364da2661108",
               shortName: "CVE",
            },
            references: [
               {
                  tags: [
                     "x_transferred",
                  ],
                  url: "https://git.kernel.org/stable/c/97cd43ba824aec764f5ea2790d0c0a318f885167",
               },
               {
                  tags: [
                     "x_transferred",
                  ],
                  url: "https://git.kernel.org/stable/c/d7d7c6cdea875be3b241d7d39873bb431db7154d",
               },
               {
                  tags: [
                     "x_transferred",
                  ],
                  url: "https://git.kernel.org/stable/c/0b61a7dc6712b78799b3949997e8a5e94db5c4b0",
               },
               {
                  tags: [
                     "x_transferred",
                  ],
                  url: "https://git.kernel.org/stable/c/9adec248bba33b1503252caf8e59d81febfc5ceb",
               },
               {
                  tags: [
                     "x_transferred",
                  ],
                  url: "https://git.kernel.org/stable/c/9c68ece8b2a5c5ff9b2fcaea923dd73efeb174cd",
               },
            ],
            title: "CVE Program Container",
         },
      ],
      cna: {
         affected: [
            {
               defaultStatus: "unaffected",
               product: "Linux",
               programFiles: [
                  "arch/loongarch/include/asm/Kbuild",
                  "arch/loongarch/include/asm/io.h",
                  "arch/loongarch/include/asm/qspinlock.h",
               ],
               repo: "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
               vendor: "Linux",
               versions: [
                  {
                     lessThan: "97cd43ba824aec764f5ea2790d0c0a318f885167",
                     status: "affected",
                     version: "fa96b57c149061f71a70bd6582d995f6424fbbf4",
                     versionType: "git",
                  },
                  {
                     lessThan: "d7d7c6cdea875be3b241d7d39873bb431db7154d",
                     status: "affected",
                     version: "fa96b57c149061f71a70bd6582d995f6424fbbf4",
                     versionType: "git",
                  },
                  {
                     lessThan: "0b61a7dc6712b78799b3949997e8a5e94db5c4b0",
                     status: "affected",
                     version: "fa96b57c149061f71a70bd6582d995f6424fbbf4",
                     versionType: "git",
                  },
                  {
                     lessThan: "9adec248bba33b1503252caf8e59d81febfc5ceb",
                     status: "affected",
                     version: "fa96b57c149061f71a70bd6582d995f6424fbbf4",
                     versionType: "git",
                  },
                  {
                     lessThan: "9c68ece8b2a5c5ff9b2fcaea923dd73efeb174cd",
                     status: "affected",
                     version: "fa96b57c149061f71a70bd6582d995f6424fbbf4",
                     versionType: "git",
                  },
               ],
            },
            {
               defaultStatus: "affected",
               product: "Linux",
               programFiles: [
                  "arch/loongarch/include/asm/Kbuild",
                  "arch/loongarch/include/asm/io.h",
                  "arch/loongarch/include/asm/qspinlock.h",
               ],
               repo: "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
               vendor: "Linux",
               versions: [
                  {
                     status: "affected",
                     version: "5.19",
                  },
                  {
                     lessThan: "5.19",
                     status: "unaffected",
                     version: "0",
                     versionType: "semver",
                  },
                  {
                     lessThanOrEqual: "6.1.*",
                     status: "unaffected",
                     version: "6.1.84",
                     versionType: "semver",
                  },
                  {
                     lessThanOrEqual: "6.6.*",
                     status: "unaffected",
                     version: "6.6.24",
                     versionType: "semver",
                  },
                  {
                     lessThanOrEqual: "6.7.*",
                     status: "unaffected",
                     version: "6.7.12",
                     versionType: "semver",
                  },
                  {
                     lessThanOrEqual: "6.8.*",
                     status: "unaffected",
                     version: "6.8.3",
                     versionType: "semver",
                  },
                  {
                     lessThanOrEqual: "*",
                     status: "unaffected",
                     version: "6.9",
                     versionType: "original_commit_for_fix",
                  },
               ],
            },
         ],
         descriptions: [
            {
               lang: "en",
               value: "In the Linux kernel, the following vulnerability has been resolved:\n\nLoongArch: Define the __io_aw() hook as mmiowb()\n\nCommit fb24ea52f78e0d595852e (\"drivers: Remove explicit invocations of\nmmiowb()\") remove all mmiowb() in drivers, but it says:\n\n\"NOTE: mmiowb() has only ever guaranteed ordering in conjunction with\nspin_unlock(). However, pairing each mmiowb() removal in this patch with\nthe corresponding call to spin_unlock() is not at all trivial, so there\nis a small chance that this change may regress any drivers incorrectly\nrelying on mmiowb() to order MMIO writes between CPUs using lock-free\nsynchronisation.\"\n\nThe mmio in radeon_ring_commit() is protected by a mutex rather than a\nspinlock, but in the mutex fastpath it behaves similar to spinlock. We\ncan add mmiowb() calls in the radeon driver but the maintainer says he\ndoesn't like such a workaround, and radeon is not the only example of\nmutex protected mmio.\n\nSo we should extend the mmiowb tracking system from spinlock to mutex,\nand maybe other locking primitives. This is not easy and error prone, so\nwe solve it in the architectural code, by simply defining the __io_aw()\nhook as mmiowb(). And we no longer need to override queued_spin_unlock()\nso use the generic definition.\n\nWithout this, we get such an error when run 'glxgears' on weak ordering\narchitectures such as LoongArch:\n\nradeon 0000:04:00.0: ring 0 stalled for more than 10324msec\nradeon 0000:04:00.0: ring 3 stalled for more than 10240msec\nradeon 0000:04:00.0: GPU lockup (current fence id 0x000000000001f412 last fence id 0x000000000001f414 on ring 3)\nradeon 0000:04:00.0: GPU lockup (current fence id 0x000000000000f940 last fence id 0x000000000000f941 on ring 0)\nradeon 0000:04:00.0: scheduling IB failed (-35).\n[drm:radeon_gem_va_ioctl [radeon]] *ERROR* Couldn't update BO_VA (-35)\nradeon 0000:04:00.0: scheduling IB failed (-35).\n[drm:radeon_gem_va_ioctl [radeon]] *ERROR* Couldn't update BO_VA (-35)\nradeon 0000:04:00.0: scheduling IB failed (-35).\n[drm:radeon_gem_va_ioctl [radeon]] *ERROR* Couldn't update BO_VA (-35)\nradeon 0000:04:00.0: scheduling IB failed (-35).\n[drm:radeon_gem_va_ioctl [radeon]] *ERROR* Couldn't update BO_VA (-35)\nradeon 0000:04:00.0: scheduling IB failed (-35).\n[drm:radeon_gem_va_ioctl [radeon]] *ERROR* Couldn't update BO_VA (-35)\nradeon 0000:04:00.0: scheduling IB failed (-35).\n[drm:radeon_gem_va_ioctl [radeon]] *ERROR* Couldn't update BO_VA (-35)\nradeon 0000:04:00.0: scheduling IB failed (-35).\n[drm:radeon_gem_va_ioctl [radeon]] *ERROR* Couldn't update BO_VA (-35)",
            },
         ],
         providerMetadata: {
            dateUpdated: "2024-12-19T08:55:44.015Z",
            orgId: "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            shortName: "Linux",
         },
         references: [
            {
               url: "https://git.kernel.org/stable/c/97cd43ba824aec764f5ea2790d0c0a318f885167",
            },
            {
               url: "https://git.kernel.org/stable/c/d7d7c6cdea875be3b241d7d39873bb431db7154d",
            },
            {
               url: "https://git.kernel.org/stable/c/0b61a7dc6712b78799b3949997e8a5e94db5c4b0",
            },
            {
               url: "https://git.kernel.org/stable/c/9adec248bba33b1503252caf8e59d81febfc5ceb",
            },
            {
               url: "https://git.kernel.org/stable/c/9c68ece8b2a5c5ff9b2fcaea923dd73efeb174cd",
            },
         ],
         title: "LoongArch: Define the __io_aw() hook as mmiowb()",
         x_generator: {
            engine: "bippy-5f407fcff5a0",
         },
      },
   },
   cveMetadata: {
      assignerOrgId: "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      assignerShortName: "Linux",
      cveId: "CVE-2024-35818",
      datePublished: "2024-05-17T13:23:22.370Z",
      dateReserved: "2024-05-17T12:19:12.343Z",
      dateUpdated: "2024-12-19T08:55:44.015Z",
      state: "PUBLISHED",
   },
   dataType: "CVE_RECORD",
   dataVersion: "5.1",
   "vulnerability-lookup:meta": {
      fkie_nvd: {
         descriptions: "[{\"lang\": \"en\", \"value\": \"In the Linux kernel, the following vulnerability has been resolved:\\n\\nLoongArch: Define the __io_aw() hook as mmiowb()\\n\\nCommit fb24ea52f78e0d595852e (\\\"drivers: Remove explicit invocations of\\nmmiowb()\\\") remove all mmiowb() in drivers, but it says:\\n\\n\\\"NOTE: mmiowb() has only ever guaranteed ordering in conjunction with\\nspin_unlock(). However, pairing each mmiowb() removal in this patch with\\nthe corresponding call to spin_unlock() is not at all trivial, so there\\nis a small chance that this change may regress any drivers incorrectly\\nrelying on mmiowb() to order MMIO writes between CPUs using lock-free\\nsynchronisation.\\\"\\n\\nThe mmio in radeon_ring_commit() is protected by a mutex rather than a\\nspinlock, but in the mutex fastpath it behaves similar to spinlock. We\\ncan add mmiowb() calls in the radeon driver but the maintainer says he\\ndoesn't like such a workaround, and radeon is not the only example of\\nmutex protected mmio.\\n\\nSo we should extend the mmiowb tracking system from spinlock to mutex,\\nand maybe other locking primitives. This is not easy and error prone, so\\nwe solve it in the architectural code, by simply defining the __io_aw()\\nhook as mmiowb(). And we no longer need to override queued_spin_unlock()\\nso use the generic definition.\\n\\nWithout this, we get such an error when run 'glxgears' on weak ordering\\narchitectures such as LoongArch:\\n\\nradeon 0000:04:00.0: ring 0 stalled for more than 10324msec\\nradeon 0000:04:00.0: ring 3 stalled for more than 10240msec\\nradeon 0000:04:00.0: GPU lockup (current fence id 0x000000000001f412 last fence id 0x000000000001f414 on ring 3)\\nradeon 0000:04:00.0: GPU lockup (current fence id 0x000000000000f940 last fence id 0x000000000000f941 on ring 0)\\nradeon 0000:04:00.0: scheduling IB failed (-35).\\n[drm:radeon_gem_va_ioctl [radeon]] *ERROR* Couldn't update BO_VA (-35)\\nradeon 0000:04:00.0: scheduling IB failed (-35).\\n[drm:radeon_gem_va_ioctl [radeon]] *ERROR* Couldn't update BO_VA (-35)\\nradeon 0000:04:00.0: scheduling IB failed (-35).\\n[drm:radeon_gem_va_ioctl [radeon]] *ERROR* Couldn't update BO_VA (-35)\\nradeon 0000:04:00.0: scheduling IB failed (-35).\\n[drm:radeon_gem_va_ioctl [radeon]] *ERROR* Couldn't update BO_VA (-35)\\nradeon 0000:04:00.0: scheduling IB failed (-35).\\n[drm:radeon_gem_va_ioctl [radeon]] *ERROR* Couldn't update BO_VA (-35)\\nradeon 0000:04:00.0: scheduling IB failed (-35).\\n[drm:radeon_gem_va_ioctl [radeon]] *ERROR* Couldn't update BO_VA (-35)\\nradeon 0000:04:00.0: scheduling IB failed (-35).\\n[drm:radeon_gem_va_ioctl [radeon]] *ERROR* Couldn't update BO_VA (-35)\"}, {\"lang\": \"es\", \"value\": \"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: LoongArch: define el gancho __io_aw() como mmiowb(). Confirmaci\\u00f3n fb24ea52f78e0d595852e (\\\"drivers: elimina las invocaciones expl\\u00edcitas de mmiowb()\\\") elimina todos los mmiowb() en los controladores, pero dice : \\\"NOTA: mmiowb() solo ha garantizado el pedido junto con spin_unlock(). Sin embargo, emparejar cada eliminaci\\u00f3n de mmiowb() en este parche con la llamada correspondiente a spin_unlock() no es nada trivial, por lo que existe una peque\\u00f1a posibilidad que este cambio puede hacer retroceder cualquier controlador que dependa incorrectamente de mmiowb() para ordenar escrituras MMIO entre CPU usando sincronizaci\\u00f3n sin bloqueo\\\". El mmio en radeon_ring_commit() est\\u00e1 protegido por un mutex en lugar de un spinlock, pero en el mutex fastpath se comporta de manera similar al spinlock. Podemos agregar llamadas mmiowb() en el controlador radeon, pero el mantenedor dice que no le gusta esa soluci\\u00f3n, y radeon no es el \\u00fanico ejemplo de mmio protegido por mutex. Entonces deber\\u00edamos extender el sistema de seguimiento mmiowb de spinlock a mutex, y tal vez a otras primitivas de bloqueo. Esto no es f\\u00e1cil y propenso a errores, por lo que lo solucionamos en el c\\u00f3digo arquitect\\u00f3nico, simplemente definiendo el gancho __io_aw() como mmiowb(). Y ya no necesitamos anular queued_spin_unlock() as\\u00ed que use la definici\\u00f3n gen\\u00e9rica. Sin esto, obtenemos este error cuando ejecutamos 'glxgears' en arquitecturas de ordenamiento d\\u00e9biles como LoongArch: radeon 0000:04:00.0: el anillo 0 se detuvo durante m\\u00e1s de 10324 mseg radeon 0000:04:00.0: el anillo 3 se detuvo durante m\\u00e1s de 10240 mseg radeon 0000:04:00.0: bloqueo de GPU (ID de valla actual 0x000000000001f412 ID de \\u00faltima valla 0x000000000001f414 en el anillo 3) radeon 0000:04:00.0: Bloqueo de GPU (ID de valla actual 0x000000000000f940 ID de \\u00faltima valla 0x000 000000000f941 en el anillo 0) radeon 0000:04:00.0: la programaci\\u00f3n IB fall\\u00f3 (-35). [drm:radeon_gem_va_ioctl [radeon]] *ERROR* No se pudo actualizar BO_VA (-35) radeon 0000:04:00.0: fall\\u00f3 la programaci\\u00f3n de IB (-35). [drm:radeon_gem_va_ioctl [radeon]] *ERROR* No se pudo actualizar BO_VA (-35) radeon 0000:04:00.0: fall\\u00f3 la programaci\\u00f3n de IB (-35). [drm:radeon_gem_va_ioctl [radeon]] *ERROR* No se pudo actualizar BO_VA (-35) radeon 0000:04:00.0: fall\\u00f3 la programaci\\u00f3n de IB (-35). [drm:radeon_gem_va_ioctl [radeon]] *ERROR* No se pudo actualizar BO_VA (-35) radeon 0000:04:00.0: fall\\u00f3 la programaci\\u00f3n de IB (-35). [drm:radeon_gem_va_ioctl [radeon]] *ERROR* No se pudo actualizar BO_VA (-35) radeon 0000:04:00.0: fall\\u00f3 la programaci\\u00f3n de IB (-35). [drm:radeon_gem_va_ioctl [radeon]] *ERROR* No se pudo actualizar BO_VA (-35) radeon 0000:04:00.0: fall\\u00f3 la programaci\\u00f3n de IB (-35). [drm:radeon_gem_va_ioctl [radeon]] *ERROR* No se pudo actualizar BO_VA (-35)\"}]",
         id: "CVE-2024-35818",
         lastModified: "2024-11-21T09:20:57.953",
         published: "2024-05-17T14:15:16.710",
         references: "[{\"url\": \"https://git.kernel.org/stable/c/0b61a7dc6712b78799b3949997e8a5e94db5c4b0\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}, {\"url\": \"https://git.kernel.org/stable/c/97cd43ba824aec764f5ea2790d0c0a318f885167\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}, {\"url\": \"https://git.kernel.org/stable/c/9adec248bba33b1503252caf8e59d81febfc5ceb\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}, {\"url\": \"https://git.kernel.org/stable/c/9c68ece8b2a5c5ff9b2fcaea923dd73efeb174cd\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}, {\"url\": \"https://git.kernel.org/stable/c/d7d7c6cdea875be3b241d7d39873bb431db7154d\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}, {\"url\": \"https://git.kernel.org/stable/c/0b61a7dc6712b78799b3949997e8a5e94db5c4b0\", \"source\": \"af854a3a-2127-422b-91ae-364da2661108\"}, {\"url\": \"https://git.kernel.org/stable/c/97cd43ba824aec764f5ea2790d0c0a318f885167\", \"source\": \"af854a3a-2127-422b-91ae-364da2661108\"}, {\"url\": \"https://git.kernel.org/stable/c/9adec248bba33b1503252caf8e59d81febfc5ceb\", \"source\": \"af854a3a-2127-422b-91ae-364da2661108\"}, {\"url\": \"https://git.kernel.org/stable/c/9c68ece8b2a5c5ff9b2fcaea923dd73efeb174cd\", \"source\": \"af854a3a-2127-422b-91ae-364da2661108\"}, {\"url\": \"https://git.kernel.org/stable/c/d7d7c6cdea875be3b241d7d39873bb431db7154d\", \"source\": \"af854a3a-2127-422b-91ae-364da2661108\"}]",
         sourceIdentifier: "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
         vulnStatus: "Awaiting Analysis",
      },
      nvd: "{\"cve\":{\"id\":\"CVE-2024-35818\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2024-05-17T14:15:16.710\",\"lastModified\":\"2024-11-21T09:20:57.953\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nLoongArch: Define the __io_aw() hook as mmiowb()\\n\\nCommit fb24ea52f78e0d595852e (\\\"drivers: Remove explicit invocations of\\nmmiowb()\\\") remove all mmiowb() in drivers, but it says:\\n\\n\\\"NOTE: mmiowb() has only ever guaranteed ordering in conjunction with\\nspin_unlock(). However, pairing each mmiowb() removal in this patch with\\nthe corresponding call to spin_unlock() is not at all trivial, so there\\nis a small chance that this change may regress any drivers incorrectly\\nrelying on mmiowb() to order MMIO writes between CPUs using lock-free\\nsynchronisation.\\\"\\n\\nThe mmio in radeon_ring_commit() is protected by a mutex rather than a\\nspinlock, but in the mutex fastpath it behaves similar to spinlock. We\\ncan add mmiowb() calls in the radeon driver but the maintainer says he\\ndoesn't like such a workaround, and radeon is not the only example of\\nmutex protected mmio.\\n\\nSo we should extend the mmiowb tracking system from spinlock to mutex,\\nand maybe other locking primitives. This is not easy and error prone, so\\nwe solve it in the architectural code, by simply defining the __io_aw()\\nhook as mmiowb(). And we no longer need to override queued_spin_unlock()\\nso use the generic definition.\\n\\nWithout this, we get such an error when run 'glxgears' on weak ordering\\narchitectures such as LoongArch:\\n\\nradeon 0000:04:00.0: ring 0 stalled for more than 10324msec\\nradeon 0000:04:00.0: ring 3 stalled for more than 10240msec\\nradeon 0000:04:00.0: GPU lockup (current fence id 0x000000000001f412 last fence id 0x000000000001f414 on ring 3)\\nradeon 0000:04:00.0: GPU lockup (current fence id 0x000000000000f940 last fence id 0x000000000000f941 on ring 0)\\nradeon 0000:04:00.0: scheduling IB failed (-35).\\n[drm:radeon_gem_va_ioctl [radeon]] *ERROR* Couldn't update BO_VA (-35)\\nradeon 0000:04:00.0: scheduling IB failed (-35).\\n[drm:radeon_gem_va_ioctl [radeon]] *ERROR* Couldn't update BO_VA (-35)\\nradeon 0000:04:00.0: scheduling IB failed (-35).\\n[drm:radeon_gem_va_ioctl [radeon]] *ERROR* Couldn't update BO_VA (-35)\\nradeon 0000:04:00.0: scheduling IB failed (-35).\\n[drm:radeon_gem_va_ioctl [radeon]] *ERROR* Couldn't update BO_VA (-35)\\nradeon 0000:04:00.0: scheduling IB failed (-35).\\n[drm:radeon_gem_va_ioctl [radeon]] *ERROR* Couldn't update BO_VA (-35)\\nradeon 0000:04:00.0: scheduling IB failed (-35).\\n[drm:radeon_gem_va_ioctl [radeon]] *ERROR* Couldn't update BO_VA (-35)\\nradeon 0000:04:00.0: scheduling IB failed (-35).\\n[drm:radeon_gem_va_ioctl [radeon]] *ERROR* Couldn't update BO_VA (-35)\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: LoongArch: define el gancho __io_aw() como mmiowb(). Confirmación fb24ea52f78e0d595852e (\\\"drivers: elimina las invocaciones explícitas de mmiowb()\\\") elimina todos los mmiowb() en los controladores, pero dice : \\\"NOTA: mmiowb() solo ha garantizado el pedido junto con spin_unlock(). Sin embargo, emparejar cada eliminación de mmiowb() en este parche con la llamada correspondiente a spin_unlock() no es nada trivial, por lo que existe una pequeña posibilidad que este cambio puede hacer retroceder cualquier controlador que dependa incorrectamente de mmiowb() para ordenar escrituras MMIO entre CPU usando sincronización sin bloqueo\\\". El mmio en radeon_ring_commit() está protegido por un mutex en lugar de un spinlock, pero en el mutex fastpath se comporta de manera similar al spinlock. Podemos agregar llamadas mmiowb() en el controlador radeon, pero el mantenedor dice que no le gusta esa solución, y radeon no es el único ejemplo de mmio protegido por mutex. Entonces deberíamos extender el sistema de seguimiento mmiowb de spinlock a mutex, y tal vez a otras primitivas de bloqueo. Esto no es fácil y propenso a errores, por lo que lo solucionamos en el código arquitectónico, simplemente definiendo el gancho __io_aw() como mmiowb(). Y ya no necesitamos anular queued_spin_unlock() así que use la definición genérica. Sin esto, obtenemos este error cuando ejecutamos 'glxgears' en arquitecturas de ordenamiento débiles como LoongArch: radeon 0000:04:00.0: el anillo 0 se detuvo durante más de 10324 mseg radeon 0000:04:00.0: el anillo 3 se detuvo durante más de 10240 mseg radeon 0000:04:00.0: bloqueo de GPU (ID de valla actual 0x000000000001f412 ID de última valla 0x000000000001f414 en el anillo 3) radeon 0000:04:00.0: Bloqueo de GPU (ID de valla actual 0x000000000000f940 ID de última valla 0x000 000000000f941 en el anillo 0) radeon 0000:04:00.0: la programación IB falló (-35). [drm:radeon_gem_va_ioctl [radeon]] *ERROR* No se pudo actualizar BO_VA (-35) radeon 0000:04:00.0: falló la programación de IB (-35). [drm:radeon_gem_va_ioctl [radeon]] *ERROR* No se pudo actualizar BO_VA (-35) radeon 0000:04:00.0: falló la programación de IB (-35). [drm:radeon_gem_va_ioctl [radeon]] *ERROR* No se pudo actualizar BO_VA (-35) radeon 0000:04:00.0: falló la programación de IB (-35). [drm:radeon_gem_va_ioctl [radeon]] *ERROR* No se pudo actualizar BO_VA (-35) radeon 0000:04:00.0: falló la programación de IB (-35). [drm:radeon_gem_va_ioctl [radeon]] *ERROR* No se pudo actualizar BO_VA (-35) radeon 0000:04:00.0: falló la programación de IB (-35). [drm:radeon_gem_va_ioctl [radeon]] *ERROR* No se pudo actualizar BO_VA (-35) radeon 0000:04:00.0: falló la programación de IB (-35). [drm:radeon_gem_va_ioctl [radeon]] *ERROR* No se pudo actualizar BO_VA (-35)\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/0b61a7dc6712b78799b3949997e8a5e94db5c4b0\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/97cd43ba824aec764f5ea2790d0c0a318f885167\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/9adec248bba33b1503252caf8e59d81febfc5ceb\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/9c68ece8b2a5c5ff9b2fcaea923dd73efeb174cd\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/d7d7c6cdea875be3b241d7d39873bb431db7154d\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/0b61a7dc6712b78799b3949997e8a5e94db5c4b0\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\"},{\"url\":\"https://git.kernel.org/stable/c/97cd43ba824aec764f5ea2790d0c0a318f885167\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\"},{\"url\":\"https://git.kernel.org/stable/c/9adec248bba33b1503252caf8e59d81febfc5ceb\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\"},{\"url\":\"https://git.kernel.org/stable/c/9c68ece8b2a5c5ff9b2fcaea923dd73efeb174cd\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\"},{\"url\":\"https://git.kernel.org/stable/c/d7d7c6cdea875be3b241d7d39873bb431db7154d\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\"}]}}",
      vulnrichment: {
         containers: "{\"adp\": [{\"title\": \"CVE Program Container\", \"references\": [{\"url\": \"https://git.kernel.org/stable/c/97cd43ba824aec764f5ea2790d0c0a318f885167\", \"tags\": [\"x_transferred\"]}, {\"url\": \"https://git.kernel.org/stable/c/d7d7c6cdea875be3b241d7d39873bb431db7154d\", \"tags\": [\"x_transferred\"]}, {\"url\": \"https://git.kernel.org/stable/c/0b61a7dc6712b78799b3949997e8a5e94db5c4b0\", \"tags\": [\"x_transferred\"]}, {\"url\": \"https://git.kernel.org/stable/c/9adec248bba33b1503252caf8e59d81febfc5ceb\", \"tags\": [\"x_transferred\"]}, {\"url\": \"https://git.kernel.org/stable/c/9c68ece8b2a5c5ff9b2fcaea923dd73efeb174cd\", \"tags\": [\"x_transferred\"]}], \"providerMetadata\": {\"orgId\": \"af854a3a-2127-422b-91ae-364da2661108\", \"shortName\": \"CVE\", \"dateUpdated\": \"2024-08-02T03:21:47.482Z\"}}, {\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2024-35818\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2024-06-17T17:39:17.575146Z\"}}}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2024-06-17T17:39:18.574Z\"}}], \"cna\": {\"title\": \"LoongArch: Define the __io_aw() hook as mmiowb()\", \"affected\": [{\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"fa96b57c1490\", \"lessThan\": \"97cd43ba824a\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"fa96b57c1490\", \"lessThan\": \"d7d7c6cdea87\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"fa96b57c1490\", \"lessThan\": \"0b61a7dc6712\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"fa96b57c1490\", \"lessThan\": \"9adec248bba3\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"fa96b57c1490\", \"lessThan\": \"9c68ece8b2a5\", \"versionType\": \"git\"}], \"programFiles\": [\"arch/loongarch/include/asm/Kbuild\", \"arch/loongarch/include/asm/io.h\", \"arch/loongarch/include/asm/qspinlock.h\"], \"defaultStatus\": \"unaffected\"}, {\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"5.19\"}, {\"status\": \"unaffected\", \"version\": \"0\", \"lessThan\": \"5.19\", \"versionType\": \"semver\"}, {\"status\": \"unaffected\", \"version\": \"6.1.84\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"6.1.*\"}, {\"status\": \"unaffected\", \"version\": \"6.6.24\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"6.6.*\"}, {\"status\": \"unaffected\", \"version\": \"6.7.12\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"6.7.*\"}, {\"status\": \"unaffected\", \"version\": \"6.8.3\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"6.8.*\"}, {\"status\": \"unaffected\", \"version\": \"6.9\", \"versionType\": \"original_commit_for_fix\", \"lessThanOrEqual\": \"*\"}], \"programFiles\": [\"arch/loongarch/include/asm/Kbuild\", \"arch/loongarch/include/asm/io.h\", \"arch/loongarch/include/asm/qspinlock.h\"], \"defaultStatus\": \"affected\"}], \"references\": [{\"url\": \"https://git.kernel.org/stable/c/97cd43ba824aec764f5ea2790d0c0a318f885167\"}, {\"url\": \"https://git.kernel.org/stable/c/d7d7c6cdea875be3b241d7d39873bb431db7154d\"}, {\"url\": \"https://git.kernel.org/stable/c/0b61a7dc6712b78799b3949997e8a5e94db5c4b0\"}, {\"url\": \"https://git.kernel.org/stable/c/9adec248bba33b1503252caf8e59d81febfc5ceb\"}, {\"url\": \"https://git.kernel.org/stable/c/9c68ece8b2a5c5ff9b2fcaea923dd73efeb174cd\"}], \"x_generator\": {\"engine\": \"bippy-8e903de6a542\"}, \"descriptions\": [{\"lang\": \"en\", \"value\": \"In the Linux kernel, the following vulnerability has been resolved:\\n\\nLoongArch: Define the __io_aw() hook as mmiowb()\\n\\nCommit fb24ea52f78e0d595852e (\\\"drivers: Remove explicit invocations of\\nmmiowb()\\\") remove all mmiowb() in drivers, but it says:\\n\\n\\\"NOTE: mmiowb() has only ever guaranteed ordering in conjunction with\\nspin_unlock(). However, pairing each mmiowb() removal in this patch with\\nthe corresponding call to spin_unlock() is not at all trivial, so there\\nis a small chance that this change may regress any drivers incorrectly\\nrelying on mmiowb() to order MMIO writes between CPUs using lock-free\\nsynchronisation.\\\"\\n\\nThe mmio in radeon_ring_commit() is protected by a mutex rather than a\\nspinlock, but in the mutex fastpath it behaves similar to spinlock. We\\ncan add mmiowb() calls in the radeon driver but the maintainer says he\\ndoesn't like such a workaround, and radeon is not the only example of\\nmutex protected mmio.\\n\\nSo we should extend the mmiowb tracking system from spinlock to mutex,\\nand maybe other locking primitives. This is not easy and error prone, so\\nwe solve it in the architectural code, by simply defining the __io_aw()\\nhook as mmiowb(). And we no longer need to override queued_spin_unlock()\\nso use the generic definition.\\n\\nWithout this, we get such an error when run 'glxgears' on weak ordering\\narchitectures such as LoongArch:\\n\\nradeon 0000:04:00.0: ring 0 stalled for more than 10324msec\\nradeon 0000:04:00.0: ring 3 stalled for more than 10240msec\\nradeon 0000:04:00.0: GPU lockup (current fence id 0x000000000001f412 last fence id 0x000000000001f414 on ring 3)\\nradeon 0000:04:00.0: GPU lockup (current fence id 0x000000000000f940 last fence id 0x000000000000f941 on ring 0)\\nradeon 0000:04:00.0: scheduling IB failed (-35).\\n[drm:radeon_gem_va_ioctl [radeon]] *ERROR* Couldn't update BO_VA (-35)\\nradeon 0000:04:00.0: scheduling IB failed (-35).\\n[drm:radeon_gem_va_ioctl [radeon]] *ERROR* Couldn't update BO_VA (-35)\\nradeon 0000:04:00.0: scheduling IB failed (-35).\\n[drm:radeon_gem_va_ioctl [radeon]] *ERROR* Couldn't update BO_VA (-35)\\nradeon 0000:04:00.0: scheduling IB failed (-35).\\n[drm:radeon_gem_va_ioctl [radeon]] *ERROR* Couldn't update BO_VA (-35)\\nradeon 0000:04:00.0: scheduling IB failed (-35).\\n[drm:radeon_gem_va_ioctl [radeon]] *ERROR* Couldn't update BO_VA (-35)\\nradeon 0000:04:00.0: scheduling IB failed (-35).\\n[drm:radeon_gem_va_ioctl [radeon]] *ERROR* Couldn't update BO_VA (-35)\\nradeon 0000:04:00.0: scheduling IB failed (-35).\\n[drm:radeon_gem_va_ioctl [radeon]] *ERROR* Couldn't update BO_VA (-35)\"}], \"providerMetadata\": {\"orgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"shortName\": \"Linux\", \"dateUpdated\": \"2024-11-29T10:54:37.328Z\"}}}",
         cveMetadata: "{\"cveId\": \"CVE-2024-35818\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2024-11-29T10:54:37.328Z\", \"dateReserved\": \"2024-05-17T12:19:12.343Z\", \"assignerOrgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"datePublished\": \"2024-05-17T13:23:22.370Z\", \"assignerShortName\": \"Linux\"}",
         dataType: "CVE_RECORD",
         dataVersion: "5.1",
      },
   },
}


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.