staging: rtl8723bs: fix a potential memory leak in rtw_init_cmd_priv()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 39bef9c6a91bbb790d04c1347cfeae584541fb6a, Kernel 708056fba733a73d926772ea4ce9a42d240345da, Kernel 8db6ca84eee0ac258706f3fca54f7c021cb159ef and 3 more.
In the Linux kernel, the following vulnerability has been resolved: staging: rtl8723bs: fix a potential memory leak in rtw_init_cmd_priv() In rtw_init_cmd_priv(), if `pcmdpriv->rsp_allocated_buf` is allocated in failure, then `pcmdpriv->cmd_allocated_buf` will be not properly released. Besides, considering there are only two error paths and the first one can directly return, so we do not need implicitly jump to the `exit` tag to execute the error handler. So this patch added `kfree(pcmdpriv->cmd_allocated_buf);` on the error path to release the resource and simplified the return logic of rtw_init_cmd_priv(). As there is no proper device to test with, no runtime testing was performed.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =4.12, >=554c0a3abf216c991c5ebddcdb2c08689ecd290b <39bef9c6a91bbb790d04c1347cfeae584541fb6a, >=554c0a3abf216c991c5ebddcdb2c08689ecd290b <708056fba733a73d926772ea4ce9a42d240345da, >=554c0a3abf216c991c5ebddcdb2c08689ecd290b <8db6ca84eee0ac258706f3fca54f7c021cb159ef, >=554c0a3abf216c991c5ebddcdb2c08689ecd290b <a5be64ff6d21f7805a91e6d81f53fc19cd9f0fae, >=554c0a3abf216c991c5ebddcdb2c08689ecd290b <e5d8f05edb36fc4ab15beec62cb6ab62f5a60fe2, >=554c0a3abf216c991c5ebddcdb2c08689ecd290b <e6cc39db24a63f68314473621020ed8cad7be423 | 39bef9c6a91bbb790d04c1347cfeae584541fb6a, 708056fba733a73d926772ea4ce9a42d240345da, 8db6ca84eee0ac258706f3fca54f7c021cb159ef, a5be64ff6d21f7805a91e6d81f53fc19cd9f0fae, e5d8f05edb36fc4ab15beec62cb6ab62f5a60fe2, e6cc39db24a63f68314473621020ed8cad7be423 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket