{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-71198 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-71198 is a vulnerability in Linux, published on 4 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-71198 and fix it if it is affected.\n\nWhat it is: CVE-2025-71198 is a vulnerability in Linux, published on 4 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-71198 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-71198/ (Markdown: https://insights.sbomify.com/CVE-2025-71198/index.md)","id":"CVE-2025-71198","markdown":"https://insights.sbomify.com/CVE-2025-71198/index.md","name":"CVE-2025-71198","record":{"aliases":["BELL-CVE-2025-71198","DEBIAN-CVE-2025-71198","GHSA-ph76-p2v9-4hmx","ROOT-OS-DEBIAN-11-CVE-2025-71198","ROOT-OS-DEBIAN-12-CVE-2025-71198","ROOT-OS-UBUNTU-2204-CVE-2025-71198","ROOT-OS-UBUNTU-2404-CVE-2025-71198","UBUNTU-CVE-2025-71198"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"low_privilege","summary":"A local attacker can cause a kernel crash by configuring unsupported accelerometer wakeup events on specific ST sensors due to a null pointer dereference.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\niio: imu: st_lsm6dsx: fix iio_chan_spec for sensors without event detection\n\nThe st_lsm6dsx_acc_channels array of struct iio_chan_spec has a non-NULL\nevent_spec field, indicating support for IIO events. However, event\ndetection is not supported for all sensors, and if userspace tries to\nconfigure accelerometer wakeup events on a sensor device that does not\nsupport them (e.g. LSM6DS0), st_lsm6dsx_write_event() dereferences a NULL\npointer when trying to write to the wakeup register.\nDefine an additional struct iio_chan_spec array whose members have a NULL\nevent_spec field, and use this array instead of st_lsm6dsx_acc_channels for\nsensors without event detection capability.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"iio: imu: st_lsm6dsx: fix iio_chan_spec for sensors without event detection","id":"CVE-2025-71198","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"iio: adc: at91-sama5d2_adc: Fix potential use-after-free in sama5d2_adc driver","id":"CVE-2025-71199"},"packages":[],"prev":{"headline":"w1: therm: Fix off-by-one buffer overflow in alarms_store","id":"CVE-2025-71197"},"products":["Linux"],"published":"2026-02-04","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-05-11","vendors":["Linux"]},"summary":"A local attacker can cause a kernel crash by configuring unsupported accelerometer wakeup events on specific ST sensors due to a null pointer dereference.","url":"https://insights.sbomify.com/CVE-2025-71198/"}