Answer in brief
CVE-2024-58006 records a Unknown severity vulnerability in PCI: dwc: ep: Prevent changing BAR size/flags in pci_epc_set_bar(). 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.
A CVSS score is not reported in the current record. 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.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=4284c88fff0efc4e418abb53d78e02dc4f099d6c <b5cacfd067060c75088363ed3e19779078be2755 || >=4284c88fff0efc4e418abb53d78e02dc4f099d6c <3229c15d6267de8e704b4085df8a82a5af2d63eb || >=4284c88fff0efc4e418abb53d78e02dc4f099d6c <3708acbd5f169ebafe1faa519cb28adc56295546 | b5cacfd067060c75088363ed3e19779078be2755, 3229c15d6267de8e704b4085df8a82a5af2d63eb, 3708acbd5f169ebafe1faa519cb28adc56295546 |
| Linux/Linuxgeneric | 6.0 | Not reported |
Published upstream
Feb 27, 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 5, 2026
In the Linux kernel, the following vulnerability has been resolved: PCI: dwc: ep: Prevent changing BAR size/flags in pci_epc_set_bar() In commit 4284c88fff0e ("PCI: designware-ep: Allow pci_epc_set_bar() update inbound map address") set_bar() was modified to support dynamically changing the backing physical address of a BAR that was already configured. This means that set_bar() can be called twice, without ever calling clear_bar() (as calling clear_bar() would clear the BAR's PCI address assigned by the host). This can only be done if the new BAR size/flags does not differ from the existing BAR configuration. Add these missing checks. If we allow set_bar() to set e.g. a new BAR size that differs from the existing BAR size, the new address translation range will be smaller than the BAR size already determined by the host, which would mean that a read past the new BAR size would pass the iATU untranslated, which could allow the host to read memory not belonging to the new struct pci_epf_bar. While at it, add comments which clarifies the support for dynamically changing the physical address of a BAR. (Which was also missing.)
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-58006 records a Unknown severity vulnerability in PCI: dwc: ep: Prevent changing BAR size/flags in pci_epc_set_bar(). 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.
A CVSS score is not reported in the current record. 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.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=4284c88fff0efc4e418abb53d78e02dc4f099d6c <b5cacfd067060c75088363ed3e19779078be2755 || >=4284c88fff0efc4e418abb53d78e02dc4f099d6c <3229c15d6267de8e704b4085df8a82a5af2d63eb || >=4284c88fff0efc4e418abb53d78e02dc4f099d6c <3708acbd5f169ebafe1faa519cb28adc56295546 | b5cacfd067060c75088363ed3e19779078be2755, 3229c15d6267de8e704b4085df8a82a5af2d63eb, 3708acbd5f169ebafe1faa519cb28adc56295546 |
| Linux/Linuxgeneric | 6.0 | Not reported |
Published upstream
Feb 27, 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 5, 2026
In the Linux kernel, the following vulnerability has been resolved: PCI: dwc: ep: Prevent changing BAR size/flags in pci_epc_set_bar() In commit 4284c88fff0e ("PCI: designware-ep: Allow pci_epc_set_bar() update inbound map address") set_bar() was modified to support dynamically changing the backing physical address of a BAR that was already configured. This means that set_bar() can be called twice, without ever calling clear_bar() (as calling clear_bar() would clear the BAR's PCI address assigned by the host). This can only be done if the new BAR size/flags does not differ from the existing BAR configuration. Add these missing checks. If we allow set_bar() to set e.g. a new BAR size that differs from the existing BAR size, the new address translation range will be smaller than the BAR size already determined by the host, which would mean that a read past the new BAR size would pass the iATU untranslated, which could allow the host to read memory not belonging to the new struct pci_epf_bar. While at it, add comments which clarifies the support for dynamically changing the physical address of a BAR. (Which was also missing.)
Quoted source text, attributed separately from HOL analysis.