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-2026-72301ASoC: SOF: ipc3-control: Fix TOCTOU in bytes_put and bytes_get

Description

In the Linux kernel, the following vulnerability has been resolved: ASoC: SOF: ipc3-control: Fix TOCTOU in bytes_put and bytes_get In sof_ipc3_bytes_put(), the size used for the memcpy is derived from the old data->size already in the buffer, not the incoming new data's size field. If the new data has a different size, the copy length is wrong: it may truncate valid data or copy stale bytes. Similarly, sof_ipc3_bytes_get() checks data->size against max_size without accounting for the sizeof(struct sof_ipc_ctrl_data) offset of the flex array within the allocation. Fix bytes_put to validate and use the incoming data's sof_abi_hdr.size from ucontrol before copying. Fix bytes_get to subtract sizeof(*cdata) from the bounds check to match the actual available space.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 2 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-2026-72301, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.17% · top 94% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 544ac8858f249950b4d99c68e538cdc07300528f – < 8bd715a9d882fe1993bb2aec5eff89fffa946592
    • affected 544ac8858f249950b4d99c68e538cdc07300528f – < 0dce240145f47545d2e4b18c6d58033b83e1fd0e
    • affected 544ac8858f249950b4d99c68e538cdc07300528f – < ed4f758f34be4c32e02933ac4fa044589d9c1c16
    • affected 544ac8858f249950b4d99c68e538cdc07300528f – < 0c4fbdaca225b97122b61b68c5353caa33a253c3
    • affected 544ac8858f249950b4d99c68e538cdc07300528f – < 92f90917413bdd6078fefff6f6c83a07bf870b04
    • affected 544ac8858f249950b4d99c68e538cdc07300528f – < 1f97760417b5faa60e9642fd0ed61eb17d0b1b39
  • Linux · Linux

    • affected 5.18
    • unaffected < 5.18
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.97 – ≤ 6.12.*
    • unaffected 6.18.40 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .