Answer in brief
CVE-2021-47012 records a High severity (CVSS 7.8) vulnerability in RDMA/siw: Fix a use after free in siw_alloc_mr. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=2251334dcac9eb337575d8767e2a6a7e81848f7f <30b9e92d0b5e5d5dc1101ab856c17009537cbca4 || >=2251334dcac9eb337575d8767e2a6a7e81848f7f <608a4b90ece039940e9425ee2b39c8beff27e00c || >=2251334dcac9eb337575d8767e2a6a7e81848f7f <3e22b88e02c194f6c80867abfef5cc09383461f4 || >=2251334dcac9eb337575d8767e2a6a7e81848f7f <ad9ce7188432650469a6c7625bf479f5ed0b6155 || >=2251334dcac9eb337575d8767e2a6a7e81848f7f <3093ee182f01689b89e9f8797b321603e5de4f63 | 30b9e92d0b5e5d5dc1101ab856c17009537cbca4, 608a4b90ece039940e9425ee2b39c8beff27e00c, 3e22b88e02c194f6c80867abfef5cc09383461f4, ad9ce7188432650469a6c7625bf479f5ed0b6155, 3093ee182f01689b89e9f8797b321603e5de4f63 |
| Linux/Linuxgeneric | 5.3 | Not reported |
Published upstream
Feb 28, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
In the Linux kernel, the following vulnerability has been resolved: RDMA/siw: Fix a use after free in siw_alloc_mr Our code analyzer reported a UAF. In siw_alloc_mr(), it calls siw_mr_add_mem(mr,..). In the implementation of siw_mr_add_mem(), mem is assigned to mr->mem and then mem is freed via kfree(mem) if xa_alloc_cyclic() failed. Here, mr->mem still point to a freed object. After, the execution continue up to the err_out branch of siw_alloc_mr, and the freed mr->mem is used in siw_mr_drop_mem(mr). My patch moves "mr->mem = mem" behind the if (xa_alloc_cyclic(..)<0) {} section, to avoid the uaf.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2021-47012 records a High severity (CVSS 7.8) vulnerability in RDMA/siw: Fix a use after free in siw_alloc_mr. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=2251334dcac9eb337575d8767e2a6a7e81848f7f <30b9e92d0b5e5d5dc1101ab856c17009537cbca4 || >=2251334dcac9eb337575d8767e2a6a7e81848f7f <608a4b90ece039940e9425ee2b39c8beff27e00c || >=2251334dcac9eb337575d8767e2a6a7e81848f7f <3e22b88e02c194f6c80867abfef5cc09383461f4 || >=2251334dcac9eb337575d8767e2a6a7e81848f7f <ad9ce7188432650469a6c7625bf479f5ed0b6155 || >=2251334dcac9eb337575d8767e2a6a7e81848f7f <3093ee182f01689b89e9f8797b321603e5de4f63 | 30b9e92d0b5e5d5dc1101ab856c17009537cbca4, 608a4b90ece039940e9425ee2b39c8beff27e00c, 3e22b88e02c194f6c80867abfef5cc09383461f4, ad9ce7188432650469a6c7625bf479f5ed0b6155, 3093ee182f01689b89e9f8797b321603e5de4f63 |
| Linux/Linuxgeneric | 5.3 | Not reported |
Published upstream
Feb 28, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
In the Linux kernel, the following vulnerability has been resolved: RDMA/siw: Fix a use after free in siw_alloc_mr Our code analyzer reported a UAF. In siw_alloc_mr(), it calls siw_mr_add_mem(mr,..). In the implementation of siw_mr_add_mem(), mem is assigned to mr->mem and then mem is freed via kfree(mem) if xa_alloc_cyclic() failed. Here, mr->mem still point to a freed object. After, the execution continue up to the err_out branch of siw_alloc_mr, and the freed mr->mem is used in siw_mr_drop_mem(mr). My patch moves "mr->mem = mem" behind the if (xa_alloc_cyclic(..)<0) {} section, to avoid the uaf.
Quoted source text, attributed separately from HOL analysis.