media: verisilicon: Fix kernel panic due to __initconst misuse
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
f988fbf0536b42f6a05ccc1ac709d60236ec1aa6| No fix yet |
| Linux Linux |
| No fix yet |
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.
From the CVE record · Linux
The Linux kernel’s verisilicon media driver can access freed data when built as a module, causing a kernel panic during probe. The issue can occur after probe deferrals or during unbind-bind cycles; the input does not describe an attacker path, authentication requirement, or user interaction.
Engineers running Linux kernels with the verisilicon media driver built as a module should check their affected versions; no version range was provided.