Answer in brief
CVE-2023-53116 records a Critical severity (CVSS 9.8) vulnerability in nvmet: avoid potential UAF in nvmet_req_complete(). 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.
Answer in brief
CVE-2023-53116 records a Critical severity (CVSS 9.8) vulnerability in nvmet: avoid potential UAF in nvmet_req_complete(). 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 9.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 |
| cpe:2.3:o:linux:linux_kernel:6.3:rc1:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.3:rc2:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=a07b4970f464f13640e28e16dad6cfa33647cc99 <e5d99b29012bbf0e86929403209723b2806500c1 || >=a07b4970f464f13640e28e16dad6cfa33647cc99 <fafcb4b26393870c45462f9af6a48e581dbbcf7e || >=a07b4970f464f13640e28e16dad6cfa33647cc99 <04c394208831d5e0d5cfee46722eb0f033cd4083 || >=a07b4970f464f13640e28e16dad6cfa33647cc99 <a6317235da8aa7cb97529ebc8121cc2a4c4c437a || >=a07b4970f464f13640e28e16dad6cfa33647cc99 <f1d5888a5efe345b63c430b256e95acb0a475642 || >=a07b4970f464f13640e28e16dad6cfa33647cc99 <bcd535f07c58342302a2cd2bdd8894fe0872c8a9 || >=a07b4970f464f13640e28e16dad6cfa33647cc99 <8ed9813871038b25a934b21ab76b5b7dbf44fc3a || >=a07b4970f464f13640e28e16dad6cfa33647cc99 <6173a77b7e9d3e202bdb9897b23f2a8afe7bf286 | e5d99b29012bbf0e86929403209723b2806500c1, fafcb4b26393870c45462f9af6a48e581dbbcf7e, 04c394208831d5e0d5cfee46722eb0f033cd4083, a6317235da8aa7cb97529ebc8121cc2a4c4c437a, f1d5888a5efe345b63c430b256e95acb0a475642, bcd535f07c58342302a2cd2bdd8894fe0872c8a9, 8ed9813871038b25a934b21ab76b5b7dbf44fc3a, 6173a77b7e9d3e202bdb9897b23f2a8afe7bf286 |
| Linux/Linuxgeneric | 4.8 | Not reported |
Published upstream
May 2, 2025
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: nvmet: avoid potential UAF in nvmet_req_complete() An nvme target ->queue_response() operation implementation may free the request passed as argument. Such implementation potentially could result in a use after free of the request pointer when percpu_ref_put() is called in nvmet_req_complete(). Avoid such problem by using a local variable to save the sq pointer before calling __nvmet_req_complete(), thus avoiding dereferencing the req pointer after that function call.
Quoted source text, attributed separately from HOL analysis.
CVSS is 9.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 |
| cpe:2.3:o:linux:linux_kernel:6.3:rc1:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.3:rc2:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=a07b4970f464f13640e28e16dad6cfa33647cc99 <e5d99b29012bbf0e86929403209723b2806500c1 || >=a07b4970f464f13640e28e16dad6cfa33647cc99 <fafcb4b26393870c45462f9af6a48e581dbbcf7e || >=a07b4970f464f13640e28e16dad6cfa33647cc99 <04c394208831d5e0d5cfee46722eb0f033cd4083 || >=a07b4970f464f13640e28e16dad6cfa33647cc99 <a6317235da8aa7cb97529ebc8121cc2a4c4c437a || >=a07b4970f464f13640e28e16dad6cfa33647cc99 <f1d5888a5efe345b63c430b256e95acb0a475642 || >=a07b4970f464f13640e28e16dad6cfa33647cc99 <bcd535f07c58342302a2cd2bdd8894fe0872c8a9 || >=a07b4970f464f13640e28e16dad6cfa33647cc99 <8ed9813871038b25a934b21ab76b5b7dbf44fc3a || >=a07b4970f464f13640e28e16dad6cfa33647cc99 <6173a77b7e9d3e202bdb9897b23f2a8afe7bf286 | e5d99b29012bbf0e86929403209723b2806500c1, fafcb4b26393870c45462f9af6a48e581dbbcf7e, 04c394208831d5e0d5cfee46722eb0f033cd4083, a6317235da8aa7cb97529ebc8121cc2a4c4c437a, f1d5888a5efe345b63c430b256e95acb0a475642, bcd535f07c58342302a2cd2bdd8894fe0872c8a9, 8ed9813871038b25a934b21ab76b5b7dbf44fc3a, 6173a77b7e9d3e202bdb9897b23f2a8afe7bf286 |
| Linux/Linuxgeneric | 4.8 | Not reported |
Published upstream
May 2, 2025
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: nvmet: avoid potential UAF in nvmet_req_complete() An nvme target ->queue_response() operation implementation may free the request passed as argument. Such implementation potentially could result in a use after free of the request pointer when percpu_ref_put() is called in nvmet_req_complete(). Avoid such problem by using a local variable to save the sq pointer before calling __nvmet_req_complete(), thus avoiding dereferencing the req pointer after that function call.
Quoted source text, attributed separately from HOL analysis.