qede: confirm skb is allocated before using
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in Kernel 034a92c6a81048128fc7b18d278d52438a13902a, Kernel 4e910dbe36508654a896d5735b318c0b88172570, Kernel 8928239e5e2e460d95b8a0b89f61671625e7ece0 and 4 more.
In the Linux kernel, the following vulnerability has been resolved: qede: confirm skb is allocated before using qede_build_skb() assumes build_skb() always works and goes straight to skb_reserve(). However, build_skb() can fail under memory pressure. This results in a kernel panic because the skb to reserve is NULL. Add a check in case build_skb() failed to allocate and return NULL. The NULL return is handled correctly in callers to qede_build_skb().
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =4.18, >=8a8633978b842c88fbcfe00d4e5dde96048f630e <034a92c6a81048128fc7b18d278d52438a13902a, >=8a8633978b842c88fbcfe00d4e5dde96048f630e <4e910dbe36508654a896d5735b318c0b88172570, >=8a8633978b842c88fbcfe00d4e5dde96048f630e <8928239e5e2e460d95b8a0b89f61671625e7ece0, >=8a8633978b842c88fbcfe00d4e5dde96048f630e <9648adb1b3ece55c657d3a4f52bfee663b710dfe, >=8a8633978b842c88fbcfe00d4e5dde96048f630e <b2d6b3db9d1cf80908964036dbe1c52a86b1afb1, >=8a8633978b842c88fbcfe00d4e5dde96048f630e <c9bdce2359b5f4986eb38d1e81865b3586cc20d2, >=8a8633978b842c88fbcfe00d4e5dde96048f630e <e1fd0c42acfa22bb34d2ab6a111484f466ab8093 | 034a92c6a81048128fc7b18d278d52438a13902a, 4e910dbe36508654a896d5735b318c0b88172570, 8928239e5e2e460d95b8a0b89f61671625e7ece0, 9648adb1b3ece55c657d3a4f52bfee663b710dfe, b2d6b3db9d1cf80908964036dbe1c52a86b1afb1, c9bdce2359b5f4986eb38d1e81865b3586cc20d2, e1fd0c42acfa22bb34d2ab6a111484f466ab8093 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket