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 offindmatching_nodeandmatch+0x5c/0x1a0 hantroprobe+0x2f4/0x7d0 [hantrovpu] The imx8mqvpusharedresources array is referenced by variant structures through their shareddevices 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 imx8mqvpushared_resources is referenced from non-init code, so keeping __initconst or __initconstormodule 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.