CVE-2026-98893: firmware: arm_scmi: Validate SENSOR_UPDATE payload size
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.18% (FIRST EPSS).
- Fixed version: Linux Linux 1bbe431fc59704d012660647516f6f94ddd82564, 32bc5496b48174dbca1f187f710955ee4d9527a1, 767789a58ae0d65ec3028e5b5b4da82210355d00; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.159.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 1bbe431fc59704d012660647516f6f94ddd82564, 32bc5496b48174dbca1f187f710955ee4d9527a1, 767789a58ae0d65ec3028e5b5b4da82210355d00; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.159.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: firmware: arm_scmi: Validate SENSOR_UPDATE payload size SENSOR_UPDATE carries one or more sensor readings after the fixed notification header. The parser derives the expected reading count from the sensor description, but it did not verify that the received payload contains those entries before parsing them. Reject truncated update notifications before reading the variable array.
- Published
- Oct 23, 2026
- Updated
- Oct 26, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.11affected
- e3811190acf85c63518fbddaa28bcbfab2baa58d and later · before e543d60f966a5f5c92298720c2fd1810f85a6be3affected · git
- e3811190acf85c63518fbddaa28bcbfab2baa58d and later · before 87a72e75f7560ea45cd28870194eaa153dd19e75affected · git
- e3811190acf85c63518fbddaa28bcbfab2baa58d and later · before 1bbe431fc59704d012660647516f6f94ddd82564affected · git
- e3811190acf85c63518fbddaa28bcbfab2baa58d and later · before c148ff2f5a168e0bc41d801efca6ee35a376cfcbaffected · git
- e3811190acf85c63518fbddaa28bcbfab2baa58d and later · before 767789a58ae0d65ec3028e5b5b4da82210355d00affected · git
- e3811190acf85c63518fbddaa28bcbfab2baa58d and later · before 32bc5496b48174dbca1f187f710955ee4d9527a1affected · git
- before 5.11not affected · semver
- 5.15.222 and later · up to and including 5.15.*not affected · semver
- 6.1.189 and later · up to and including 6.1.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-98891Oct 23, 2026 · wifi: mac80211: validate deauth frame length before reason access0Monitor
- ← EarlierCVE-2026-98892Oct 23, 2026 · firmware: arm_scmi: Validate BASE_ERROR_EVENT payload size0Monitor
- Later →CVE-2026-98894Oct 23, 2026 · drm/amd/ras: reset CPER ring on corrupt entry size0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1bbe431fc59704d012660647516f6f94ddd82564 | Vendor (CNA) |
| Linux Linux | 32bc5496b48174dbca1f187f710955ee4d9527a1 | Vendor (CNA) |
| Linux Linux | 767789a58ae0d65ec3028e5b5b4da82210355d00 | Vendor (CNA) |
| Linux Linux | 87a72e75f7560ea45cd28870194eaa153dd19e75 | Vendor (CNA) |
| Linux Linux | c148ff2f5a168e0bc41d801efca6ee35a376cfcb | Vendor (CNA) |
| Linux Linux | e543d60f966a5f5c92298720c2fd1810f85a6be3 | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | 6.6.159.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayOct 27, 2026+4 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1390 · Oct 26, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/32bc5496b48174dbca1f187f710955ee4d9527a1
- git.kernel.org/stable/c/767789a58ae0d65ec3028e5b5b4da82210355d00
- git.kernel.org/stable/c/87a72e75f7560ea45cd28870194eaa153dd19e75
- git.kernel.org/stable/c/c148ff2f5a168e0bc41d801efca6ee35a376cfcb
- git.kernel.org/stable/c/e543d60f966a5f5c92298720c2fd1810f85a6be3
Vendor advisories and official records. Exploit/PoC links are deliberately left out.