PCI: dwc: ep: Prevent changing BAR size/flags in pci_epc_set_bar()
CVE-2024-58006 · published 27 Feb 2025
How serious is it
- Severity: critical, CVSS score 9.6 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2024-58006?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: 4284c88fff0efc4e418abb53d78e02dc4f099d6c to < 01aaa7935af3050fd1e1e7de50001247c75baeab, 4284c88fff0efc4e418abb53d78e02dc4f099d6c to < b5cacfd067060c75088363ed3e19779078be2755, 4284c88fff0efc4e418abb53d78e02dc4f099d6c to < 3229c15d6267de8e704b4085df8a82a5af2d63eb, 4284c88fff0efc4e418abb53d78e02dc4f099d6c to < 3708acbd5f169ebafe1faa519cb28adc56295546
- Linux Linux: 6.0
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
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.)
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/01aaa7935af3050fd1e1e7de50001247c75baeab
- git.kernel.org/stable/c/b5cacfd067060c75088363ed3e19779078be2755
- git.kernel.org/stable/c/3229c15d6267de8e704b4085df8a82a5af2d63eb
- git.kernel.org/stable/c/3708acbd5f169ebafe1faa519cb28adc56295546
Merged from CVE List. Last updated 25 Oct 2026. All vulnerabilities · RSS · JSON