Answer in brief
CVE-2026-31573 records a Unknown severity vulnerability in media: verisilicon: Fix kernel panic due to __initconst misuse. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=5133ef7c893c2c3aee7dd12503dc480de9dbfbb5 <07861e84b766c6db8014bc34138f3be4a62aad2a || >=286d629d10640bc22f3bf46aa4f356eb7975e862 <1e7e9119cf9b0d8585b27653b1a6dc31397c252e || >=e0203ddf9af7c8e170e1e99ce83b4dc07f0cd765 <e8d97c270cb46a2a88739019d0f8547adc7d97da | 07861e84b766c6db8014bc34138f3be4a62aad2a, 1e7e9119cf9b0d8585b27653b1a6dc31397c252e, e8d97c270cb46a2a88739019d0f8547adc7d97da |
| Linux/Linuxgeneric | >=6.19.6 <6.19.11 | 6.19.11 |
Published upstream
Apr 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.