scsi: core: Fix possible memory leak if device_add() fails
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 4.14.323, Kernel 4.19.292, Kernel 5.4.254 and 12 more.
In the Linux kernel, the following vulnerability has been resolved: scsi: core: Fix possible memory leak if device_add() fails If device_add() returns error, the name allocated by dev_set_name() needs be freed. As the comment of device_add() says, put_device() should be used to decrease the reference count in the error path. So fix this by calling put_device(), then the name can be freed in kobject_cleanp().
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=2.6.26 <4.14.323, >=4.15 <4.19.292, >=4.20 <5.4.254, >=5.11 <5.15.127, >=5.16 <6.1.46, >=5.5 <5.10.191, >=6.2 <6.4.11, =6.5, >=ee959b00c335d7780136c5abda37809191fe52c3 <06c5340858011aa1195aec43a776e3185fbf7f56, >=ee959b00c335d7780136c5abda37809191fe52c3 <43c0e16d0c5ec59398b405f4c4aa5a076e656c3f, >=ee959b00c335d7780136c5abda37809191fe52c3 <63956ad27a6882f01fea7c69e17823090f4c7b3f, >=ee959b00c335d7780136c5abda37809191fe52c3 <6bc7f4c8c27d526f968788b8a985896755b1df35, >=ee959b00c335d7780136c5abda37809191fe52c3 <aa9a76d5ffdecd3b52ac333eb89361b0c9fe04e8, >=ee959b00c335d7780136c5abda37809191fe52c3 <b191ff1f075c4875f11271cbf0093e6e044a12aa, >=ee959b00c335d7780136c5abda37809191fe52c3 <e12fac07f61caac9c5b186d827658b3470787619, =2.6.26, >=ee959b00c335d7780136c5abda37809191fe52c3 <04b5b5cb0136ce970333a9c6cec7e46adba1ea3a | 4.14.323, 4.19.292, 5.4.254, 5.15.127, 6.1.46, 5.10.191, 6.4.11, 06c5340858011aa1195aec43a776e3185fbf7f56, 43c0e16d0c5ec59398b405f4c4aa5a076e656c3f, 63956ad27a6882f01fea7c69e17823090f4c7b3f, 6bc7f4c8c27d526f968788b8a985896755b1df35, aa9a76d5ffdecd3b52ac333eb89361b0c9fe04e8, b191ff1f075c4875f11271cbf0093e6e044a12aa, e12fac07f61caac9c5b186d827658b3470787619, 04b5b5cb0136ce970333a9c6cec7e46adba1ea3a |
| linux-kernel: Kernel | >=2.6.26 <4.14.323, >=4.15.0 <4.19.292, >=4.20.0 <5.4.254, >=5.11.0 <5.15.127, >=5.16.0 <6.1.46, >=5.5.0 <5.10.191, >=6.2.0 <6.4.11 | 4.14.323, 4.19.292, 5.4.254, 5.15.127, 6.1.46, 5.10.191, 6.4.11 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket