PCI: brcmstb: Fix error path after a call to regulator_bulk_get()
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.1.134, 6.6.87, 6.12.23, 6.13.11, 6.14.2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: PCI: brcmstb: Fix error path after a call to regulator_bulk_get() If the regulator_bulk_get() returns an error and no regulators are created, we need to set their number to zero. If we don't do this and the PCIe link up fails, a call to the regulator_bulk_free() will result in a kernel panic. While at it, print the error value, as we cannot return an error upwards as the kernel will WARN() on an error from add_bus(). [kwilczynski: commit log, use comma in the message to match style with other similar messages]
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 9e6be018b26347c26a93e63fb50a37ee2c9311de · fixed in 99a0efba9f903acbdece548862b6b4cbe7d999e1; From 9e6be018b26347c26a93e63fb50a37ee2c9311de · fixed in eedd054834930b8d678f0776cd4b091b8fffbb4a; From 9e6be018b26347c26a93e63fb50a37ee2c9311de · fixed in df63321a40cc98e52313cffbff376b8ae9ceffa7; From 9e6be018b26347c26a93e63fb50a37ee2c9311de · fixed in 7842e842a9bf6bd5866c84f588353711d131ab1a; From 9e6be018b26347c26a93e63fb50a37ee2c9311de · fixed in 6f44e1fdb006db61394aa4d4c25728ada00842e7; From 9e6be018b26347c26a93e63fb50a37ee2c9311de · fixed in 3651ad5249c51cf7eee078e12612557040a6bdb4
- Linux Linux
6.0
- KernelLinux
From 6.0.0 · fixed in 6.1.134; From 6.2.0 · fixed in 6.6.87; From 6.7.0 · fixed in 6.12.23; From 6.13.0 · fixed in 6.13.11; From 6.14.0 · fixed in 6.14.2