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-2025-38391usb: typec: altmodes/displayport: do not index invalid pin_assignments

Description

In the Linux kernel, the following vulnerability has been resolved: usb: typec: altmodes/displayport: do not index invalid pin_assignments A poorly implemented DisplayPort Alt Mode port partner can indicate that its pin assignment capabilities are greater than the maximum value, DP_PIN_ASSIGN_F. In this case, calls to pin_assignment_show will cause a BRK exception due to an out of bounds array access. Prevent for loop in pin_assignment_show from accessing invalid values in pin_assignments by adding DP_PIN_ASSIGN_MAX value in typec_dp.h and using i < DP_PIN_ASSIGN_MAX as a loop condition.

Timeline

  1. ID reserved

    By Linux

  2. · 3 months later

    Published

  3. · 16 months 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

CVSS scores of CVE-2025-38391, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 0e3bb7d6894d9b6e67d6382bb03a46a1dc989588 – < c93bc959788ed9a1af7df57cb539837bdf790cee
    • affected 0e3bb7d6894d9b6e67d6382bb03a46a1dc989588 – < 114a977e0f6bf278e05eade055e13fc271f69cf7
    • affected 0e3bb7d6894d9b6e67d6382bb03a46a1dc989588 – < 621d5a3ef0231ab242f2d31eecec40c38ca609c5
    • affected 0e3bb7d6894d9b6e67d6382bb03a46a1dc989588 – < 2f535517b5611b7221ed478527e4b58e29536ddf
    • affected 0e3bb7d6894d9b6e67d6382bb03a46a1dc989588 – < 45e9444b3b97eaf51a5024f1fea92f44f39b50c6
    • affected 0e3bb7d6894d9b6e67d6382bb03a46a1dc989588 – < 5581e694d3a1c2f32c5a51d745c55b107644e1f8
    • affected 0e3bb7d6894d9b6e67d6382bb03a46a1dc989588 – < 47cb5d26f61d80c805d7de4106451153779297a1
    • affected 0e3bb7d6894d9b6e67d6382bb03a46a1dc989588 – < af4db5a35a4ef7a68046883bfd12468007db38f1
  • Linux · Linux

    • affected 4.19
    • unaffected < 4.19
    • unaffected 5.4.296 – ≤ 5.4.*
    • unaffected 5.10.240 – ≤ 5.10.*
    • unaffected 5.15.187 – ≤ 5.15.*
    • unaffected 6.1.144 – ≤ 6.1.*
    • unaffected 6.6.97 – ≤ 6.6.*
    • unaffected 6.12.37 – ≤ 6.12.*
    • unaffected 6.15.6 – ≤ 6.15.*
    • unaffected 6.16 – ≤ *

References

References10

Sources

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

Badge for a README or a ticket

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

Record last updated .