fkie_cve-2024-56700
Vulnerability from fkie_nvd
Published
2024-12-28 10:15
Modified
2024-12-28 10:15
Severity ?
Summary
In the Linux kernel, the following vulnerability has been resolved: media: wl128x: Fix atomicity violation in fmc_send_cmd() Atomicity violation occurs when the fmc_send_cmd() function is executed simultaneously with the modification of the fmdev->resp_skb value. Consider a scenario where, after passing the validity check within the function, a non-null fmdev->resp_skb variable is assigned a null value. This results in an invalid fmdev->resp_skb variable passing the validity check. As seen in the later part of the function, skb = fmdev->resp_skb; when the invalid fmdev->resp_skb passes the check, a null pointer dereference error may occur at line 478, evt_hdr = (void *)skb->data; To address this issue, it is recommended to include the validity check of fmdev->resp_skb within the locked section of the function. This modification ensures that the value of fmdev->resp_skb does not change during the validation process, thereby maintaining its validity. This possible bug is found by an experimental static analysis tool developed by our team. This tool analyzes the locking APIs to extract function pairs that can be concurrently executed, and then analyzes the instructions in the paired functions to identify possible concurrency bugs including data races and atomicity violations.
References
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/2e63c908de357048180516b84740ed62dac0b269
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/372dc9509122e5d45d4c12978e31c3c7d00aaca4
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/378ce4e08ca2b1ac7bbf1d57b68643ca4226c5f8
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/3c818ad07e964bca3d27adac1e1f50e1e3c9180e
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/80a3b2ee01eecf22dfa06968b3cde92c691dea10
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/ca59f9956d4519ab18ab2270be47c6b8c6ced091
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/d16109c9fdc1b8cea4fe63b42e06e926c3f68990
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/d7408a052aa1b4f6fb6f1c7a8877b84017a07ac9
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/ed228b74d8a500380150965d5becabf9a1e33141
Impacted products
Vendor Product Version


To clipboard 

{
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: wl128x: Fix atomicity violation in fmc_send_cmd()\n\nAtomicity violation occurs when the fmc_send_cmd() function is executed\nsimultaneously with the modification of the fmdev-\u003eresp_skb value.\nConsider a scenario where, after passing the validity check within the\nfunction, a non-null fmdev-\u003eresp_skb variable is assigned a null value.\nThis results in an invalid fmdev-\u003eresp_skb variable passing the validity\ncheck. As seen in the later part of the function, skb = fmdev-\u003eresp_skb;\nwhen the invalid fmdev-\u003eresp_skb passes the check, a null pointer\ndereference error may occur at line 478, evt_hdr = (void *)skb-\u003edata;\n\nTo address this issue, it is recommended to include the validity check of\nfmdev-\u003eresp_skb within the locked section of the function. This\nmodification ensures that the value of fmdev-\u003eresp_skb does not change\nduring the validation process, thereby maintaining its validity.\n\nThis possible bug is found by an experimental static analysis tool\ndeveloped by our team. This tool analyzes the locking APIs\nto extract function pairs that can be concurrently executed, and then\nanalyzes the instructions in the paired functions to identify possible\nconcurrency bugs including data races and atomicity violations."
    },
    {
      "lang": "es",
      "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: media: wl128x: Se corrige la violaci\u00f3n de atomicidad en fmc_send_cmd() La violaci\u00f3n de atomicidad ocurre cuando la funci\u00f3n fmc_send_cmd() se ejecuta simult\u00e1neamente con la modificaci\u00f3n del valor fmdev-\u0026gt;resp_skb. Considere un escenario donde, despu\u00e9s de pasar la verificaci\u00f3n de validez dentro de la funci\u00f3n, a una variable fmdev-\u0026gt;resp_skb no nula se le asigna un valor nulo. Esto da como resultado una variable fmdev-\u0026gt;resp_skb no v\u00e1lida que pasa la verificaci\u00f3n de validez. Como se ve en la parte posterior de la funci\u00f3n, skb = fmdev-\u0026gt;resp_skb; cuando la fmdev-\u0026gt;resp_skb no v\u00e1lida pasa la verificaci\u00f3n, puede ocurrir un error de desreferencia de puntero nulo en la l\u00ednea 478, evt_hdr = (void *)skb-\u0026gt;data; Para solucionar este problema, se recomienda incluir la comprobaci\u00f3n de validez de fmdev-\u0026gt;resp_skb dentro de la secci\u00f3n bloqueada de la funci\u00f3n. Esta modificaci\u00f3n garantiza que el valor de fmdev-\u0026gt;resp_skb no cambie durante el proceso de validaci\u00f3n, manteniendo as\u00ed su validez. Este posible error se detecta mediante una herramienta de an\u00e1lisis est\u00e1tico experimental desarrollada por nuestro equipo. Esta herramienta analiza las API de bloqueo para extraer pares de funciones que se pueden ejecutar simult\u00e1neamente y, a continuaci\u00f3n, analiza las instrucciones en las funciones emparejadas para identificar posibles errores de concurrencia, incluidas las ejecuci\u00f3ns de datos y las violaciones de atomicidad."
    }
  ],
  "id": "CVE-2024-56700",
  "lastModified": "2024-12-28T10:15:17.290",
  "metrics": {},
  "published": "2024-12-28T10:15:17.290",
  "references": [
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/2e63c908de357048180516b84740ed62dac0b269"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/372dc9509122e5d45d4c12978e31c3c7d00aaca4"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/378ce4e08ca2b1ac7bbf1d57b68643ca4226c5f8"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/3c818ad07e964bca3d27adac1e1f50e1e3c9180e"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/80a3b2ee01eecf22dfa06968b3cde92c691dea10"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/ca59f9956d4519ab18ab2270be47c6b8c6ced091"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/d16109c9fdc1b8cea4fe63b42e06e926c3f68990"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/d7408a052aa1b4f6fb6f1c7a8877b84017a07ac9"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/ed228b74d8a500380150965d5becabf9a1e33141"
    }
  ],
  "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.