CVE-2024-56700: Linux kernel · media: wl128x: Fix atomicity violation in fmc_send_cmd()
Source GCVE Database
Not known to be exploited · CVSS 5.5 Medium.
Data as of 30 Oct 2026, 00:52 UTC
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 28 Dec 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
AI-suggested
A fix is available that moves the validity check of fmdev->resp_skb inside the locked section of the fmc_send_cmd() function to prevent concurrent modification. Users should apply the official Linux kernel patches that address this issue once released. Until patched, avoiding untrusted code execution or local access that could trigger this function may reduce risk. Monitor vendor advisories for the official patch release.
Description
CVE-2024-56700 is a medium-severity vulnerability in the Linux kernel's media wl128x driver. It involves an atomicity violation in the fmc_send_cmd() function, where concurrent modification of the fmdev->resp_skb pointer can lead to a null pointer dereference and potential kernel crash. The issue arises because the validity check of fmdev->resp_skb is not performed under proper locking, allowing a race condition. The vulnerability was identified using an experimental static analysis tool. A fix involves ensuring the validity check occurs within a locked section to prevent concurrent modification during validation.
References
- nvd.nist.gov/vuln/detail/CVE-2024-56700 (opens in a new tab)
- git.kernel.org/stable/c/2e63c908de357048180516b84740ed62dac0b269 (opens in a new tab)
- git.kernel.org/stable/c/372dc9509122e5d45d4c12978e31c3c7d00aaca4 (opens in a new tab)
- git.kernel.org/stable/c/378ce4e08ca2b1ac7bbf1d57b68643ca4226c5f8 (opens in a new tab)
- git.kernel.org/stable/c/3c818ad07e964bca3d27adac1e1f50e1e3c9180e (opens in a new tab)
- git.kernel.org/stable/c/80a3b2ee01eecf22dfa06968b3cde92c691dea10 (opens in a new tab)
- git.kernel.org/stable/c/ca59f9956d4519ab18ab2270be47c6b8c6ced091 (opens in a new tab)
- git.kernel.org/stable/c/d16109c9fdc1b8cea4fe63b42e06e926c3f68990 (opens in a new tab)
- git.kernel.org/stable/c/d7408a052aa1b4f6fb6f1c7a8877b84017a07ac9 (opens in a new tab)
- git.kernel.org/stable/c/ed228b74d8a500380150965d5becabf9a1e33141 (opens in a new tab)
- lists.debian.org/debian-lts-announce/2025/03/msg00001.html (opens in a new tab)
- lists.debian.org/debian-lts-announce/2025/03/msg00002.html (opens in a new tab)