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-43310media: verisilicon: Avoid G2 bus error while decoding H.264 and HEVC

Description

In the Linux kernel, the following vulnerability has been resolved: media: verisilicon: Avoid G2 bus error while decoding H.264 and HEVC For the i.MX8MQ platform, there is a hardware limitation: the g1 VPU and g2 VPU cannot decode simultaneously; otherwise, it will cause below bus error and produce corrupted pictures, even potentially lead to system hang. [ 110.527986] hantro-vpu 38310000.video-codec: frame decode timed out. [ 110.583517] hantro-vpu 38310000.video-codec: bus error detected. Therefore, it is necessary to ensure that g1 and g2 operate alternately. This allows for successful multi-instance decoding of H.264 and HEVC. To achieve this, g1 and g2 share the same v4l2_m2m_dev, and then the v4l2_m2m_dev can handle the scheduling.

Timeline

  1. ID reserved

    By Linux

  2. · 7 days later

    Published

  3. · 6 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-43310, 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.12% · top 98% of all CVEs (13 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 cb5dd5a0fa518dff14ff2b90837c3c8f98f4dd5c – < 42a9fbccb33a38c5a9e0a84680939da8eae4f60e
    • affected cb5dd5a0fa518dff14ff2b90837c3c8f98f4dd5c – < f988fbf0536b42f6a05ccc1ac709d60236ec1aa6
    • affected cb5dd5a0fa518dff14ff2b90837c3c8f98f4dd5c – < f2efc1e8ab65bdb9b892af132887323e4df92f02
    • affected cb5dd5a0fa518dff14ff2b90837c3c8f98f4dd5c – < 5133ef7c893c2c3aee7dd12503dc480de9dbfbb5
    • affected cb5dd5a0fa518dff14ff2b90837c3c8f98f4dd5c – < 286d629d10640bc22f3bf46aa4f356eb7975e862
    • affected cb5dd5a0fa518dff14ff2b90837c3c8f98f4dd5c – < e0203ddf9af7c8e170e1e99ce83b4dc07f0cd765
  • Linux · Linux

    • affected 5.14
    • unaffected < 5.14
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.114 – ≤ 6.12.*
    • unaffected 6.18.57 – ≤ 6.18.*
    • unaffected 6.19.6 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .