CVE-2026-90274

coresight: etm4x: fix underflow for usage of (nrseqstate - 1)

N/A
Published: September 17, 2026 at 04:08 PM UTC
Updated: October 19, 2026 at 09:19 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: coresight: etm4x: fix underflow for usage of (nrseqstate - 1) According to IHI006H Embedded Trace Macrocell Architecture Specification[0], TRCSEQEVR<n> is implemented only when TRCIDR5.NUMSEQSTATE is 0b100, in which case n ranges from 0 to 2; otherwise, TRCIDR5.NUMSEQSTATE is 0b000. IOW, the number of usage in the initialisation or setting TRCSEQEVR<n> with drvdata->nrseqstate - 1 in the loop could make underflow issue when TRCIDR5.NUMSEQSTATE is 0b000. Therefore, introduce nr_seq_ctrls field and untie it from nrseqstate. As part of this introduce ETM_MAX_SEQ_TRANSITIONS macro and apply nr_seq_ctrls and above macro to TRCSEQEVR<n> relevant fields setup.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2e1cdfe184b5202d51e0611d7a051e2bea3039464.2
Vendor states this is fixed in 1674d9bff8073bdee5dbc200f56fc3caa28d0566 (fixed)
Vendor states this is fixed in 1ade9a335c69fc735cb7b3f222ed35ab135540fb (fixed)
Vendor states this is fixed in 4091f2d5b26d117c992ffcce1a5df425a0daedcd (fixed)
Vendor states this is fixed in 4f9a0f548413bf864f609c9f4bc56e3f1b3577d4 (fixed)
Vendor states this is fixed in 5ac900f73ce1d4d8308f40752b51bc8a02b244d2 (fixed)
Vendor states this is fixed in 8d669db59f7283b838e029af29da12e505265fae (fixed)
Vendor states this is fixed in be7b2de5b9a96ae68ffa3528e0a40d63e0fd8148 (fixed)
Vendor states this is fixed in 4.2 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.52 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.6 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card