{"api_version":"1","generated_at":"2026-09-17T23:51:45+00:00","cve":"CVE-2026-92510","urls":{"html":"https://cve.report/CVE-2026-92510","api":"https://cve.report/api/cve/CVE-2026-92510.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-92510","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-92510"},"summary":{"title":"RDMA/core: Fix potential use after free in ib_destroy_srq_user()","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/core: Fix potential use after free in ib_destroy_srq_user()\n\nWhen accessing a SRQ via the netlink path the only synchronization\nmechanism for the said SRQ is rdma_restrack_get().\nCurrently, rdma_restrack_del() is invoked at the end of\nib_destroy_srq_user(), which is too late, since by that point\nvendor-specific resources associated with the SRQ might already be\nfreed. This can leave a short window where the SRQ remains accessible\nthrough restrack, leading to a potential use-after-free.\n\nFix this by moving the rdma_restrack_begin_del() call to the start of\nib_destroy_srq_user(), ensuring that the SRQ is removed from restrack\nbefore its internal resources are released. This guarantees that no new\nusers hold references to a SRQ that is in the process of destruction.\n\nIn addition, this change preserves the intended inverted order\nbetween create and destroy routines: resources are added to\nrestrack at the end of successful creation, and hence shall be removed\nfrom the restrack first thing during the destruction flow, which keeps\nthe lifecycle management consistent and predictable.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-17 17:17:53","updated_at":"2026-09-17 17:17:53"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/a5bfd9fe05d5cebbd3e447bf7f7b2c663007d8b9","name":"https://git.kernel.org/stable/c/a5bfd9fe05d5cebbd3e447bf7f7b2c663007d8b9","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/d3d0eabe6e39b024deb3e085e2d408d037e967c3","name":"https://git.kernel.org/stable/c/d3d0eabe6e39b024deb3e085e2d408d037e967c3","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/88244ecc71cc0b3ed200f5ef7ddea6686adfd730","name":"https://git.kernel.org/stable/c/88244ecc71cc0b3ed200f5ef7ddea6686adfd730","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/bedd7dee72588c838f5b67197ea8b387e7beb918","name":"https://git.kernel.org/stable/c/bedd7dee72588c838f5b67197ea8b387e7beb918","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/95c992c869df54a6a7061f5f3fb6400244f2af8f","name":"https://git.kernel.org/stable/c/95c992c869df54a6a7061f5f3fb6400244f2af8f","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/9c704383529044c02122f85a2a9a42cbf14a07a6","name":"https://git.kernel.org/stable/c/9c704383529044c02122f85a2a9a42cbf14a07a6","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-92510","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-92510","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 48f8a70e899fa4d9c8f00369f482f0382173ece9 a5bfd9fe05d5cebbd3e447bf7f7b2c663007d8b9 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 48f8a70e899fa4d9c8f00369f482f0382173ece9 d3d0eabe6e39b024deb3e085e2d408d037e967c3 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 48f8a70e899fa4d9c8f00369f482f0382173ece9 9c704383529044c02122f85a2a9a42cbf14a07a6 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 48f8a70e899fa4d9c8f00369f482f0382173ece9 bedd7dee72588c838f5b67197ea8b387e7beb918 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 48f8a70e899fa4d9c8f00369f482f0382173ece9 95c992c869df54a6a7061f5f3fb6400244f2af8f git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 48f8a70e899fa4d9c8f00369f482f0382173ece9 88244ecc71cc0b3ed200f5ef7ddea6686adfd730 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 5.13","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 5.13 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.1.188 6.1.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.6.157 6.6.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.110 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.52 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.6 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3-rc1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/infiniband/core/verbs.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"a5bfd9fe05d5cebbd3e447bf7f7b2c663007d8b9","status":"affected","version":"48f8a70e899fa4d9c8f00369f482f0382173ece9","versionType":"git"},{"lessThan":"d3d0eabe6e39b024deb3e085e2d408d037e967c3","status":"affected","version":"48f8a70e899fa4d9c8f00369f482f0382173ece9","versionType":"git"},{"lessThan":"9c704383529044c02122f85a2a9a42cbf14a07a6","status":"affected","version":"48f8a70e899fa4d9c8f00369f482f0382173ece9","versionType":"git"},{"lessThan":"bedd7dee72588c838f5b67197ea8b387e7beb918","status":"affected","version":"48f8a70e899fa4d9c8f00369f482f0382173ece9","versionType":"git"},{"lessThan":"95c992c869df54a6a7061f5f3fb6400244f2af8f","status":"affected","version":"48f8a70e899fa4d9c8f00369f482f0382173ece9","versionType":"git"},{"lessThan":"88244ecc71cc0b3ed200f5ef7ddea6686adfd730","status":"affected","version":"48f8a70e899fa4d9c8f00369f482f0382173ece9","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/infiniband/core/verbs.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"5.13"},{"lessThan":"5.13","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.1.*","status":"unaffected","version":"6.1.188","versionType":"semver"},{"lessThanOrEqual":"6.6.*","status":"unaffected","version":"6.6.157","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.110","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.52","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.6","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3-rc1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.1.188","versionStartIncluding":"5.13","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.6.157","versionStartIncluding":"5.13","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.110","versionStartIncluding":"5.13","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.52","versionStartIncluding":"5.13","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.6","versionStartIncluding":"5.13","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3-rc1","versionStartIncluding":"5.13","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/core: Fix potential use after free in ib_destroy_srq_user()\n\nWhen accessing a SRQ via the netlink path the only synchronization\nmechanism for the said SRQ is rdma_restrack_get().\nCurrently, rdma_restrack_del() is invoked at the end of\nib_destroy_srq_user(), which is too late, since by that point\nvendor-specific resources associated with the SRQ might already be\nfreed. This can leave a short window where the SRQ remains accessible\nthrough restrack, leading to a potential use-after-free.\n\nFix this by moving the rdma_restrack_begin_del() call to the start of\nib_destroy_srq_user(), ensuring that the SRQ is removed from restrack\nbefore its internal resources are released. This guarantees that no new\nusers hold references to a SRQ that is in the process of destruction.\n\nIn addition, this change preserves the intended inverted order\nbetween create and destroy routines: resources are added to\nrestrack at the end of successful creation, and hence shall be removed\nfrom the restrack first thing during the destruction flow, which keeps\nthe lifecycle management consistent and predictable."}],"providerMetadata":{"dateUpdated":"2026-09-17T16:10:20.775Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/a5bfd9fe05d5cebbd3e447bf7f7b2c663007d8b9"},{"url":"https://git.kernel.org/stable/c/d3d0eabe6e39b024deb3e085e2d408d037e967c3"},{"url":"https://git.kernel.org/stable/c/9c704383529044c02122f85a2a9a42cbf14a07a6"},{"url":"https://git.kernel.org/stable/c/bedd7dee72588c838f5b67197ea8b387e7beb918"},{"url":"https://git.kernel.org/stable/c/95c992c869df54a6a7061f5f3fb6400244f2af8f"},{"url":"https://git.kernel.org/stable/c/88244ecc71cc0b3ed200f5ef7ddea6686adfd730"}],"title":"RDMA/core: Fix potential use after free in ib_destroy_srq_user()","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-92510","datePublished":"2026-09-17T16:10:20.775Z","dateReserved":"2026-09-16T12:21:13.872Z","dateUpdated":"2026-09-17T16:10:20.775Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-17 17:17:53","lastModifiedDate":"2026-09-17 17:17:53","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"92510","Ordinal":"1","Title":"RDMA/core: Fix potential use after free in ib_destroy_srq_user()","CVE":"CVE-2026-92510","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"92510","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/core: Fix potential use after free in ib_destroy_srq_user()\n\nWhen accessing a SRQ via the netlink path the only synchronization\nmechanism for the said SRQ is rdma_restrack_get().\nCurrently, rdma_restrack_del() is invoked at the end of\nib_destroy_srq_user(), which is too late, since by that point\nvendor-specific resources associated with the SRQ might already be\nfreed. This can leave a short window where the SRQ remains accessible\nthrough restrack, leading to a potential use-after-free.\n\nFix this by moving the rdma_restrack_begin_del() call to the start of\nib_destroy_srq_user(), ensuring that the SRQ is removed from restrack\nbefore its internal resources are released. This guarantees that no new\nusers hold references to a SRQ that is in the process of destruction.\n\nIn addition, this change preserves the intended inverted order\nbetween create and destroy routines: resources are added to\nrestrack at the end of successful creation, and hence shall be removed\nfrom the restrack first thing during the destruction flow, which keeps\nthe lifecycle management consistent and predictable.","Type":"Description","Title":"RDMA/core: Fix potential use after free in ib_destroy_srq_user()"}]}}}