{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90307 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90307 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-90307 and fix it if it is affected.\n\nWhat it is: CVE-2026-90307 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-90307 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-90307/ (Markdown: https://insights.sbomify.com/CVE-2026-90307/index.md)","id":"CVE-2026-90307","markdown":"https://insights.sbomify.com/CVE-2026-90307/index.md","name":"CVE-2026-90307","record":{"aliases":["AZL-101903","BELL-CVE-2026-90307","DEBIAN-CVE-2026-90307","GHSA-24j7-gr38-qhjc","UBUNTU-CVE-2026-90307"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel RDMA","requires_auth":"none","summary":"A malicious RDMA target can leak kernel heap memory to the initiator by sending truncated SRP requests, exposing sensitive data.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/srp: fix heap information leak on a truncated SRP_CRED_REQ\n\nsrp_recv_done() passes wc-\u003ebyte_len to srp_process_rsp(). It passes\nnothing to srp_process_cred_req() and srp_process_aer_req(), which read\nfixed-size fields from the receive buffer without checking that those\nfields were received.\n\nThe buffer size is max_ti_iu_len, which comes from the login response\nand is not validated. A target that advertises 8 and then sends an\n8-byte SRP_CRED_REQ makes the initiator read req-\u003etag from beyond the\nend of the buffer. req-\u003etag is copied into the SRP_CRED_RSP and sent\nback, so those bytes reach the target. SRP_AER_REQ behaves the same way\nand also reads req-\u003elun.\n\nThe leak is 8 bytes per response. max_ti_iu_len also decides which slab\ncache the buffer comes from. With 8 the buffer is a kmalloc-8 object and\nthe read is entirely outside it:\n\n  BUG: KASAN: slab-out-of-bounds in srp_recv_done+0x172b/0x1aa0\n  Read of size 8 at addr ffff888104714da8 by task kworker/u8:3/50\n   which belongs to the cache kmalloc-8 of size 8\n  The buggy address is located 0 bytes to the right of\n   allocated 8-byte region [ffff888104714da0, ffff888104714da8)\n\nWithout KASAN the returned bytes are whatever is next in the slab. One\nrun returned \".strtab\".\n\nrsp-\u003edata[3] in srp_process_rsp() has the same problem: only\nresp_data_len is checked before it is read.\n\nDrop a request that is shorter than the structure being parsed, and\ncheck byte_len before the tsk_mgmt read.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"RDMA/srp: fix heap information leak on a truncated SRP_CRED_REQ","id":"CVE-2026-90307","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"RDMA/erdma: Hold QP references for AE and CM processing","id":"CVE-2026-90308"},"packages":[],"prev":{"headline":"ARM: 9481/2: breakpoint: CFI breakpoints only on demand","id":"CVE-2026-90306"},"products":["Linux"],"published":"2026-09-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A malicious RDMA target can leak kernel heap memory to the initiator by sending truncated SRP requests, exposing sensitive data.","url":"https://insights.sbomify.com/CVE-2026-90307/"}