Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 32 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.17% · top 93% of all CVEs (15 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 2e1cdfe184b5202d51e0611d7a051e2bea303946 – < 8d669db59f7283b838e029af29da12e505265fae
    • affected 2e1cdfe184b5202d51e0611d7a051e2bea303946 – < 4091f2d5b26d117c992ffcce1a5df425a0daedcd
    • affected 2e1cdfe184b5202d51e0611d7a051e2bea303946 – < be7b2de5b9a96ae68ffa3528e0a40d63e0fd8148
    • affected 2e1cdfe184b5202d51e0611d7a051e2bea303946 – < 4f9a0f548413bf864f609c9f4bc56e3f1b3577d4
    • affected 2e1cdfe184b5202d51e0611d7a051e2bea303946 – < 1ade9a335c69fc735cb7b3f222ed35ab135540fb
    • affected 2e1cdfe184b5202d51e0611d7a051e2bea303946 – < 5ac900f73ce1d4d8308f40752b51bc8a02b244d2
    • affected 2e1cdfe184b5202d51e0611d7a051e2bea303946 – < 1674d9bff8073bdee5dbc200f56fc3caa28d0566
  • Linux · Linux

    • affected 4.2
    • unaffected < 4.2
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-90274 badge
[![CVE-2026-90274](https://cveledger.app/badge/CVE-2026-90274.svg)](https://cveledger.app/cve/CVE-2026-90274)

Record last updated .