Payload overread via truncated sensor notifications
Published Oct 23, 2026 · Updated Oct 23, 2026
Out-of-bounds reading in Linux SCMI sensor handling allows attackers to trigger excess reads via truncated SENSOR_UPDATE notifications. The scmi_sensor_fill_custom_report() function derives a reading count from sensor metadata and accesses the trailing array without checking the received length. Triggering requires delivery of a truncated notification to the affected SCMI handler; attacker privileges and any resulting disclosure or crash are not established.
Summary
What happened
Out-of-bounds reading in Linux SCMI sensor handling allows attackers to trigger excess reads via truncated SENSOR_UPDATE notifications. The scmi_sensor_fill_custom_report() function derives a reading count from sensor metadata and accesses the trailing array without checking the received length. Triggering requires delivery of a truncated notification to the affected SCMI handler; attacker privileges and any resulting disclosure or crash are not established.
The record
- CVE
- CVE-2026-98893
- Published
- Oct 23, 2026
- Updated
- Oct 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 23, 2026CVE publishedPublication date reported by the CVE source.
- Oct 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <5.15.222
- Affected versionversion=0 <6.1.189
- Affected versionversion=0 <6.12.111
- Affected versionversion=0 <6.18.53
- Affected versionversion=0 <6.6.158
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <1bbe431fc59704d012660647516f6f94ddd82564
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <32bc5496b48174dbca1f187f710955ee4d9527a1
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <767789a58ae0d65ec3028e5b5b4da82210355d00
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <87a72e75f7560ea45cd28870194eaa153dd19e75
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c148ff2f5a168e0bc41d801efca6ee35a376cfcb
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e543d60f966a5f5c92298720c2fd1810f85a6be3
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us