Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-56700media: wl128x: Fix atomicity violation in fmc_send_cmd()

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 1 day later

    Published

  3. · 17 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-56700, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.22% · top 87% of all CVEs (18 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected e8454ff7b9a4d56f02c095bff12d3c92ef4c7fa6 – < d16109c9fdc1b8cea4fe63b42e06e926c3f68990
    • affected e8454ff7b9a4d56f02c095bff12d3c92ef4c7fa6 – < 3c818ad07e964bca3d27adac1e1f50e1e3c9180e
    • affected e8454ff7b9a4d56f02c095bff12d3c92ef4c7fa6 – < d7408a052aa1b4f6fb6f1c7a8877b84017a07ac9
    • affected e8454ff7b9a4d56f02c095bff12d3c92ef4c7fa6 – < ed228b74d8a500380150965d5becabf9a1e33141
    • affected e8454ff7b9a4d56f02c095bff12d3c92ef4c7fa6 – < 372dc9509122e5d45d4c12978e31c3c7d00aaca4
    • affected e8454ff7b9a4d56f02c095bff12d3c92ef4c7fa6 – < 378ce4e08ca2b1ac7bbf1d57b68643ca4226c5f8
    • affected e8454ff7b9a4d56f02c095bff12d3c92ef4c7fa6 – < 2e63c908de357048180516b84740ed62dac0b269
    • affected e8454ff7b9a4d56f02c095bff12d3c92ef4c7fa6 – < 80a3b2ee01eecf22dfa06968b3cde92c691dea10
    • affected e8454ff7b9a4d56f02c095bff12d3c92ef4c7fa6 – < ca59f9956d4519ab18ab2270be47c6b8c6ced091
  • Linux · Linux

    • affected 2.6.39
    • unaffected < 2.6.39
    • unaffected 4.19.325 – ≤ 4.19.*
    • unaffected 5.4.287 – ≤ 5.4.*
    • unaffected 5.10.231 – ≤ 5.10.*
    • unaffected 5.15.174 – ≤ 5.15.*
    • unaffected 6.1.120 – ≤ 6.1.*
    • unaffected 6.6.64 – ≤ 6.6.*
    • unaffected 6.11.11 – ≤ 6.11.*
    • unaffected 6.12.2 – ≤ 6.12.*
    • unaffected 6.13 – ≤ *

References

References11

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-56700 badge
[![CVE-2024-56700](https://cveledger.app/badge/CVE-2024-56700.svg)](https://cveledger.app/cve/CVE-2024-56700)

Record last updated .