{"id":"CVE-2025-38531","title":"iio: common: st_sensors: Fix use of uninitialize device structs","summary":"In the Linux kernel, the following vulnerability has been resolved:\n\niio: common: st_sensors: Fix use of uninitialize device structs\n\nThroughout the various probe functions &indio_dev->dev is used before it\nis initialized. This caused a …","severity":"none","vendor":"Linux","product":"Linux","affected":["Linux >= 4dff754876959b3f3b354800089bc8aaa3ec1d95 < 1f88548ec8ade8538eb970e36ffe5049b89d86f7","Linux >= 4dff754876959b3f3b354800089bc8aaa3ec1d95 < f9d4b618f1b9e6d760cc7c15052b92f7faf47201","Linux >= 4dff754876959b3f3b354800089bc8aaa3ec1d95 < 610615c9668037e3eca11132063b93b2d945af13","Linux >= 4dff754876959b3f3b354800089bc8aaa3ec1d95 < 3297a9016a45144883ec990bd4bd5b1d79cafb46","Linux >= 4dff754876959b3f3b354800089bc8aaa3ec1d95 < 9f92e93e257b33e73622640a9205f8642ec16ddd","Linux 5.16"],"published":"2025-08-16","updated":"2026-10-30","sourceUpdated":"2026-10-30T12:22:01.935Z","source":"CVEORG","sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2025-38531","references":[{"url":"https://git.kernel.org/stable/c/1f88548ec8ade8538eb970e36ffe5049b89d86f7"},{"url":"https://git.kernel.org/stable/c/f9d4b618f1b9e6d760cc7c15052b92f7faf47201"},{"url":"https://git.kernel.org/stable/c/610615c9668037e3eca11132063b93b2d945af13"},{"url":"https://git.kernel.org/stable/c/3297a9016a45144883ec990bd4bd5b1d79cafb46"},{"url":"https://git.kernel.org/stable/c/9f92e93e257b33e73622640a9205f8642ec16ddd"}],"tags":["cve.org"],"epss":0.00177,"epssPercentile":0.07276,"ingestedAt":"2026-11-03T18:52:04.086Z","slug":"CVE-2025-38531","body":"## Overview\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niio: common: st_sensors: Fix use of uninitialize device structs\n\nThroughout the various probe functions &indio_dev->dev is used before it\nis initialized. This caused a kernel panic in st_sensors_power_enable()\nwhen the call to devm_regulator_bulk_get_enable() fails and then calls\ndev_err_probe() with the uninitialized device.\n\nThis seems to only cause a panic with dev_err_probe(), dev_err(),\ndev_warn() and dev_info() don't seem to cause a panic, but are fixed\nas well.\n\nThe issue is reported and traced here: [1]\n\n## Affected\n\n- `Linux >= 4dff754876959b3f3b354800089bc8aaa3ec1d95 < 1f88548ec8ade8538eb970e36ffe5049b89d86f7`\n- `Linux >= 4dff754876959b3f3b354800089bc8aaa3ec1d95 < f9d4b618f1b9e6d760cc7c15052b92f7faf47201`\n- `Linux >= 4dff754876959b3f3b354800089bc8aaa3ec1d95 < 610615c9668037e3eca11132063b93b2d945af13`\n- `Linux >= 4dff754876959b3f3b354800089bc8aaa3ec1d95 < 3297a9016a45144883ec990bd4bd5b1d79cafb46`\n- `Linux >= 4dff754876959b3f3b354800089bc8aaa3ec1d95 < 9f92e93e257b33e73622640a9205f8642ec16ddd`\n- `Linux 5.16`\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"sunlit","depthScore":3,"depthScoreParts":{"impact":2.8,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}