CVE-2023-53171
BaseFortify
Publication date: 2025-09-15
Last updated on: 2025-12-02
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 3.6 (inc) to 5.10.173 (exc) |
| linux | linux_kernel | From 5.11 (inc) to 5.15.99 (exc) |
| linux | linux_kernel | From 5.16 (inc) to 6.1.16 (exc) |
| linux | linux_kernel | From 6.2 (inc) to 6.2.3 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-NVD-CWE-noinfo |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability occurs in the Linux kernel's vfio/type1 driver where an underflow of the locked_vm counter happens during an exec() call. When a vfio container is preserved across exec, the task's memory descriptor (mm) changes, resetting locked_vm to zero and losing the count from existing DMA mappings. If the user later unmaps a DMA mapping, locked_vm underflows to a large unsigned value, causing subsequent DMA map requests to fail with ENOMEM errors. The fix involves saving the mm at the time a DMA is mapped and using that saved mm when adjusting locked_vm to prevent underflow.
How can this vulnerability impact me? :
This vulnerability can cause failures in DMA mapping requests due to locked_vm underflow, leading to ENOMEM errors. This means that applications relying on vfio for DMA mappings may experience resource allocation failures, potentially causing disruptions or degraded performance in systems using this functionality.