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-90307RDMA/srp: fix heap information leak on a truncated SRP_CRED_REQ

Description

In the Linux kernel, the following vulnerability has been resolved: RDMA/srp: fix heap information leak on a truncated SRP_CRED_REQ srp_recv_done() passes wc->byte_len to srp_process_rsp(). It passes nothing to srp_process_cred_req() and srp_process_aer_req(), which read fixed-size fields from the receive buffer without checking that those fields were received. The buffer size is max_ti_iu_len, which comes from the login response and is not validated. A target that advertises 8 and then sends an 8-byte SRP_CRED_REQ makes the initiator read req->tag from beyond the end of the buffer. req->tag is copied into the SRP_CRED_RSP and sent back, so those bytes reach the target. SRP_AER_REQ behaves the same way and also reads req->lun. The leak is 8 bytes per response. max_ti_iu_len also decides which slab cache the buffer comes from. With 8 the buffer is a kmalloc-8 object and the read is entirely outside it: BUG: KASAN: slab-out-of-bounds in srp_recv_done+0x172b/0x1aa0 Read of size 8 at addr ffff888104714da8 by task kworker/u8:3/50 which belongs to the cache kmalloc-8 of size 8 The buggy address is located 0 bytes to the right of allocated 8-byte region [ffff888104714da0, ffff888104714da8) Without KASAN the returned bytes are whatever is next in the slab. One run returned ".strtab". rsp->data[3] in srp_process_rsp() has the same problem: only resp_data_len is checked before it is read. Drop a request that is shorter than the structure being parsed, and check byte_len before the tsk_mgmt read.

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 (13 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 bb12588a38e6db85e01dceadff7bc161fc92e7d2 – < 3f7fdf561f1ec3b523c39708df00bd808671668d
    • affected bb12588a38e6db85e01dceadff7bc161fc92e7d2 – < 138eb2f0ef02adfe6ad126afad5b54c56b5046ee
    • affected bb12588a38e6db85e01dceadff7bc161fc92e7d2 – < 3787f4c3e0d813d6c56be9f6dfaf66f8551fb0a7
    • affected bb12588a38e6db85e01dceadff7bc161fc92e7d2 – < 0e7ba617514902501514d577647d866e670dad90
    • affected bb12588a38e6db85e01dceadff7bc161fc92e7d2 – < 001adf2fe87d1ab677c014a97467bbea5153ae5f
    • affected bb12588a38e6db85e01dceadff7bc161fc92e7d2 – < dc2272c00d7c00ee2a69b57f7ca9caaefcbdb8cd
    • affected bb12588a38e6db85e01dceadff7bc161fc92e7d2 – < fa1b33fdab3e79dce83721ead3220200a2dbec22
    • affected bb12588a38e6db85e01dceadff7bc161fc92e7d2 – < 961ac0f0c5e414abdd6b33fae84b311d9fde0bd0
  • Linux · Linux

    • affected 2.6.37
    • unaffected < 2.6.37
    • 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-90307 badge
[![CVE-2026-90307](https://cveledger.app/badge/CVE-2026-90307.svg)](https://cveledger.app/cve/CVE-2026-90307)

Record last updated .