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-98187wifi: p54: require a full exp_if record in PDR_INTERFACE_LIST

Description

In the Linux kernel, the following vulnerability has been resolved: wifi: p54: require a full exp_if record in PDR_INTERFACE_LIST The PDR_INTERFACE_LIST loop only checks that the record start is within the entry before reading an entire struct exp_if from it. A truncated trailing record makes the if_id/variant reads cross the entry boundary into the heap beyond the EEPROM buffer (verified with a KASAN reproducer of the loop). The variant also feeds the synth front-end selection, so this is not only a leak. Advance only while a full record still fits in the entry.

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 13 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.18% · top 93% of all CVEs (17 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 eff1a59c48e3c6a006eb4fe5f2e405a996f2259d – < 162dbe1c285a621eab6a9f2851086b63a0378928
    • affected eff1a59c48e3c6a006eb4fe5f2e405a996f2259d – < 70bf34b425fe549a4f6a8d50a319f8f05d1f91c9
    • affected eff1a59c48e3c6a006eb4fe5f2e405a996f2259d – < 487f966421014de41e835bbce3feb30b35f4f729
    • affected eff1a59c48e3c6a006eb4fe5f2e405a996f2259d – < bc83c04be042f53869c315b8e1eb5f124959d1d7
    • affected eff1a59c48e3c6a006eb4fe5f2e405a996f2259d – < d44c1badc2dcb042985f7e37f4c448c84548b81f
    • affected eff1a59c48e3c6a006eb4fe5f2e405a996f2259d – < d2fb6b588dc5bbab4f603661e41cd60f0d931628
    • affected eff1a59c48e3c6a006eb4fe5f2e405a996f2259d – < d82492fd0a3fb61963c236521852763238ad3898
    • affected eff1a59c48e3c6a006eb4fe5f2e405a996f2259d – < d8efd84f49379ed28624098821f80e992657d935
  • Linux · Linux

    • affected 2.6.24
    • unaffected < 2.6.24
    • unaffected 5.10.271 – ≤ 5.10.*
    • unaffected 5.15.222 – ≤ 5.15.*
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.112 – ≤ 6.12.*
    • unaffected 6.18.54 – ≤ 6.18.*
    • unaffected 7.2.8 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .