Answer in brief
CVE-2023-53171 records a Medium severity (CVSS 5.5) vulnerability in vfio/type1: prevent underflow of locked_vm via exec(). 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 5.5. 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 | >=73fa0d10d077d9521ee2dace2307ae2c9a965336 <5a271242716846cc016736fb76be2b40ee49b0c3 || >=73fa0d10d077d9521ee2dace2307ae2c9a965336 <eafb81c50da899dd80b340c841277acc4a1945b7 || >=73fa0d10d077d9521ee2dace2307ae2c9a965336 <a6b2aabe664098d5cf877ae0fd96459464a30e17 || >=73fa0d10d077d9521ee2dace2307ae2c9a965336 <b0790dff0760b7734cf0961f497ad64628ca550b || >=73fa0d10d077d9521ee2dace2307ae2c9a965336 <046eca5018f8a5dd1dc2cedf87fb5843b9ea3026 | 5a271242716846cc016736fb76be2b40ee49b0c3, eafb81c50da899dd80b340c841277acc4a1945b7, a6b2aabe664098d5cf877ae0fd96459464a30e17, b0790dff0760b7734cf0961f497ad64628ca550b, 046eca5018f8a5dd1dc2cedf87fb5843b9ea3026 |
| Linux/Linuxgeneric | 3.6 | Not reported |
Published upstream
Sep 15, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 5, 2026
In the Linux kernel, the following vulnerability has been resolved: vfio/type1: prevent underflow of locked_vm via exec() When a vfio container is preserved across exec, the task does not change, but it gets a new mm with locked_vm=0, and loses the count from existing dma mappings. If the user later unmaps a dma mapping, locked_vm underflows to a large unsigned value, and a subsequent dma map request fails with ENOMEM in __account_locked_vm. To avoid underflow, grab and save the mm at the time a dma is mapped. Use that mm when adjusting locked_vm, rather than re-acquiring the saved task's mm, which may have changed. If the saved mm is dead, do nothing. locked_vm is incremented for existing mappings in a subsequent patch.
Quoted source text, attributed separately from HOL analysis.