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-31573media: verisilicon: Fix kernel panic due to __initconst misuse

Description

In the Linux kernel, the following vulnerability has been resolved: media: verisilicon: Fix kernel panic due to __initconst misuse Fix a kernel panic when probing the driver as a module: Unable to handle kernel paging request at virtual address ffffd9c18eb05000 of_find_matching_node_and_match+0x5c/0x1a0 hantro_probe+0x2f4/0x7d0 [hantro_vpu] The imx8mq_vpu_shared_resources array is referenced by variant structures through their shared_devices field. When built as a module, __initconst causes this data to be freed after module init, but it's later accessed during probe, causing a page fault. The imx8mq_vpu_shared_resources is referenced from non-init code, so keeping __initconst or __initconst_or_module here is wrong. Drop the __initconst annotation and let it live in the normal .rodata section. A bug of __initconst called from regular non-init probe code leading to bugs during probe deferrals or during unbind-bind cycles.

Timeline

  1. ID reserved

    By Linux

  2. · 46 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-31573, 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.15% · top 95% of all CVEs (17 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 42a9fbccb33a38c5a9e0a84680939da8eae4f60e – < 53b88097bb0e0b895a691ae7da4a54b567c0d375
    • affected f2efc1e8ab65bdb9b892af132887323e4df92f02 – < 5d177ff5eb235de9cc0b8e877466f5a3af6f573e
    • affected 5133ef7c893c2c3aee7dd12503dc480de9dbfbb5 – < 07861e84b766c6db8014bc34138f3be4a62aad2a
    • affected 286d629d10640bc22f3bf46aa4f356eb7975e862 – < 1e7e9119cf9b0d8585b27653b1a6dc31397c252e
    • affected e0203ddf9af7c8e170e1e99ce83b4dc07f0cd765 – < e8d97c270cb46a2a88739019d0f8547adc7d97da
    • affected f988fbf0536b42f6a05ccc1ac709d60236ec1aa6
    • affected 6.6.160 – < 6.7
  • Linux · Linux

    • affected 6.19.6 – < 6.19.11

References

References5

Sources

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

Badge for a README or a ticket

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

Record last updated .