In the Linux kernel, the following vulnerability has been resolved:
iio: adc: axp20x_adc: Add missing sentinel to AXP717 ADC channel maps
The AXP717 ADC channel maps is missing a sentinel entry at the end. This
causes a KASAN warning.
Add the missing sentinel entry.
Security readout for executives and security teams
Plain-English summary
A missing end marker in the Linux AXP717 ADC channel map can cause the kernel to access beyond the intended map, producing a KASAN memory-safety warning. The supplied CVSS score is 7.3, reflecting potentially serious confidentiality and availability consequences for a local, low-privileged attacker. Evidence does not establish practical exploitability.
Executive priority
Treat as a high-priority, targeted kernel update rather than an internet-wide emergency. Prioritize embedded, appliance, and Linux environments using AXP717 ADC functionality, especially where untrusted users have local access. Confirm vendor-fixed builds promptly; the supplied evidence does not support claims of active exploitation.
Technical view
The axp20x_adc driver’s AXP717 channel maps lack a sentinel entry. Code expecting that terminator may continue beyond the map boundary, triggering KASAN. The upstream resolution adds the missing sentinel. The supplied CVSS vector requires local access and low privileges, with high confidentiality and availability impact and low integrity impact.
Likely exposure
Exposure is most plausible on Linux systems using the AXP717 ADC functionality in the affected axp20x_adc driver. The bundle marks Linux versions 6.12, 6.12.40, 6.15.8, and 6.16 as affected, but does not provide a complete, clearly bounded version range. Confirm against vendor advisories and kernel provenance.
Exploitation context
The supplied record is not in KEV, and no cited source reports active exploitation or a public exploit. The CVSS vector describes a local, low-privileged attack path without user interaction. A KASAN warning proves an invalid memory access condition during testing, but the bundle does not demonstrate reliable security impact or weaponization.
Researcher notes
The source bundle provides no CWE and does not document the precise out-of-bounds operation, trigger conditions, reachable data, or exploit reliability. The repeated commit identifier and ambiguous affected-version presentation reduce precision. Review the referenced stable-kernel commits and relevant vendor backports to establish introduction points, fixed branches, and whether the warning can produce security-relevant behavior.
Mitigation direction
Update to a vendor-supported kernel containing the referenced sentinel fix.
Check distribution or device-vendor advisories for exact fixed package versions.
Prioritize systems that use AXP717 ADC hardware or the affected driver.
Restrict local account access until remediation is confirmed.
Validation and detection
Inventory kernel versions and vendor package revisions on potentially affected systems.
Determine whether systems use AXP717 ADC functionality through the axp20x_adc driver.
Verify the deployed kernel includes one of the referenced corrective commits.
Run vendor-approved regression testing after updating the kernel.
Monitor kernel and KASAN logs for axp20x_adc-related memory warnings.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-38547 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
4Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.