Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 2e63c908de357048180516b84740ed62dac0b269, 372dc9509122e5d45d4c12978e31c3c7d00aaca4, 378ce4e08ca2b1ac7bbf1d57b68643ca4226c5f8.

Low priority for now. Upgrade to Linux Linux 2e63c908de357048180516b84740ed62dac0b269, 372dc9509122e5d45d4c12978e31c3c7d00aaca4, 378ce4e08ca2b1ac7bbf1d57b68643ca4226c5f8 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Dec 28, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 12th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-56700

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel2.6.39 and later · before 4.19.325
  • linux linux kernel4.20 and later · before 5.4.287
  • linux linux kernel5.5 and later · before 5.10.231
  • linux linux kernel5.11 and later · before 5.15.174
  • linux linux kernel5.16 and later · before 6.1.120
  • linux linux kernel6.2 and later · before 6.6.64
  • linux linux kernel6.7 and later · before 6.11.11
  • linux linux kernel6.12 and later · before 6.12.2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 2.6.39affected
    • e8454ff7b9a4d56f02c095bff12d3c92ef4c7fa6 and later · before d16109c9fdc1b8cea4fe63b42e06e926c3f68990affected · git
    • e8454ff7b9a4d56f02c095bff12d3c92ef4c7fa6 and later · before 3c818ad07e964bca3d27adac1e1f50e1e3c9180eaffected · git
    • e8454ff7b9a4d56f02c095bff12d3c92ef4c7fa6 and later · before d7408a052aa1b4f6fb6f1c7a8877b84017a07ac9affected · git
    • e8454ff7b9a4d56f02c095bff12d3c92ef4c7fa6 and later · before ed228b74d8a500380150965d5becabf9a1e33141affected · git
    • e8454ff7b9a4d56f02c095bff12d3c92ef4c7fa6 and later · before 372dc9509122e5d45d4c12978e31c3c7d00aaca4affected · git
    • e8454ff7b9a4d56f02c095bff12d3c92ef4c7fa6 and later · before 378ce4e08ca2b1ac7bbf1d57b68643ca4226c5f8affected · git
    • e8454ff7b9a4d56f02c095bff12d3c92ef4c7fa6 and later · before 2e63c908de357048180516b84740ed62dac0b269affected · git
    • e8454ff7b9a4d56f02c095bff12d3c92ef4c7fa6 and later · before 80a3b2ee01eecf22dfa06968b3cde92c691dea10affected · git
    • e8454ff7b9a4d56f02c095bff12d3c92ef4c7fa6 and later · before ca59f9956d4519ab18ab2270be47c6b8c6ced091affected · git

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.123-16.1.123-1
Debian:13linuxbefore 6.12.3-16.12.3-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-56698Dec 28, 2024 · usb: dwc3: gadget: Fix looping of queued SG entries
    22Monitor
  • ← EarlierCVE-2024-56699Dec 28, 2024 · s390/pci: Fix potential double remove of hotplug slot
    31Monitor
  • Later →CVE-2024-56704Dec 28, 2024 · 9p/xen: fix release of IRQ
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux2e63c908de357048180516b84740ed62dac0b269Vendor (CNA)
Linux Linux372dc9509122e5d45d4c12978e31c3c7d00aaca4Vendor (CNA)
Linux Linux378ce4e08ca2b1ac7bbf1d57b68643ca4226c5f8Vendor (CNA)
Linux Linux3c818ad07e964bca3d27adac1e1f50e1e3c9180eVendor (CNA)
Linux Linux80a3b2ee01eecf22dfa06968b3cde92c691dea10Vendor (CNA)
Linux Linuxca59f9956d4519ab18ab2270be47c6b8c6ced091Vendor (CNA)
Linux Linuxd16109c9fdc1b8cea4fe63b42e06e926c3f68990Vendor (CNA)
Linux Linuxd7408a052aa1b4f6fb6f1c7a8877b84017a07ac9Vendor (CNA)
Linux Linuxed228b74d8a500380150965d5becabf9a1e33141Vendor (CNA)
debian:linux6.1.123-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-476 · NULL Pointer Dereference

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (10 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records