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-90416RDMA/mlx5: Fix stack out-of-bounds read in cc_params debugfs

Description

In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx5: Fix stack out-of-bounds read in cc_params debugfs get_param() reads a congestion parameter as a u32 but formats it with the signed "%d" into an 11-byte stack buffer. A value with bit 31 set, such as 0x80000000, renders as "-2147483648\n" whose full length is 12. snprintf() stores only 11 bytes yet returns 12, so simple_read_from_buffer() treats 12 bytes as valid and reads one byte past lbuf[]. Size the buffer for the widest unsigned decimal, format with "%u" to match the u32, and use scnprintf() so the length passed to simple_read_from_buffer() reflects the bytes actually stored.

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.22% · top 88% of all CVEs (16 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 4a2da0b8c0782816f3ae6846ae7942fcbb0f8172 – < 1c5b4f76cd73372c5a8a4c91c95d5a31f141e091
    • affected 4a2da0b8c0782816f3ae6846ae7942fcbb0f8172 – < 06b62758f81e27ca4c81201c22e3436c6d9ac894
    • affected 4a2da0b8c0782816f3ae6846ae7942fcbb0f8172 – < d809cf3f0ed9255abfc73c4730bcf187151422af
    • affected 4a2da0b8c0782816f3ae6846ae7942fcbb0f8172 – < 0b0122fcc923a0271130f5fb71af2cd7e20434d9
    • affected 4a2da0b8c0782816f3ae6846ae7942fcbb0f8172 – < ce8dfd32a33b578c3abf178f67b4c8d36854f041
    • affected 4a2da0b8c0782816f3ae6846ae7942fcbb0f8172 – < 4599311e78e88c893ad551aca622de2bfdf1c31f
    • affected 4a2da0b8c0782816f3ae6846ae7942fcbb0f8172 – < c75ee076fa09778a2f9602a972dade4a0b0785f7
    • affected 4a2da0b8c0782816f3ae6846ae7942fcbb0f8172 – < 03826bc1fa6c90405bf05831f2b501a8368dcd27
  • Linux · Linux

    • affected 4.14
    • unaffected < 4.14
    • unaffected 5.10.270 – ≤ 5.10.*
    • 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

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .