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-2022-50541dmaengine: ti: k3-udma: Reset UDMA_CHAN_RT byte counters to prevent overflow

Description

In the Linux kernel, the following vulnerability has been resolved: dmaengine: ti: k3-udma: Reset UDMA_CHAN_RT byte counters to prevent overflow UDMA_CHAN_RT_*BCNT_REG stores the real-time channel bytecount statistics. These registers are 32-bit hardware counters and the driver uses these counters to monitor the operational progress status for a channel, when transferring more than 4GB of data it was observed that these counters overflow and completion calculation of a operation gets affected and the transfer hangs indefinitely. This commit adds changes to decrease the byte count for every complete transaction so that these registers never overflow and the proper byte count statistics is maintained for ongoing transaction by the RT counters. Earlier uc->bcnt used to maintain a count of the completed bytes at driver side, since the RT counters maintain the statistics of current transaction now, the maintenance of uc->bcnt is not necessary.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 7 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-2022-50541, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.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.16% · top 95% of all CVEs (16 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 25dcb5dd7b7ce5587c1df18f584ff78f51a68a94 – < d68da10b0cceb4177b653833e794b2923a4ffbd7
    • affected 25dcb5dd7b7ce5587c1df18f584ff78f51a68a94 – < e0b16bfbd3a4a8d09614046335f4482313e7c0c4
    • affected 25dcb5dd7b7ce5587c1df18f584ff78f51a68a94 – < a065657643a62a24b4435ddcaea45f1e9378749e
    • affected 25dcb5dd7b7ce5587c1df18f584ff78f51a68a94 – < 7c94dcfa8fcff2dba53915f1dabfee49a3df8b88
  • Linux · Linux

    • affected 5.6
    • unaffected < 5.6
    • unaffected 5.15.75 – ≤ 5.15.*
    • unaffected 5.19.17 – ≤ 5.19.*
    • unaffected 6.0.3 – ≤ 6.0.*
    • unaffected 6.1 – ≤ *

References

References4

Sources

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

Badge for a README or a ticket

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

Record last updated .