qede: confirm skb is allocated before using
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 8a8633978b842c88fbcfe00d4e5dde96048f630e · < e1fd0c42acfa22bb34d2ab6a111484f466ab8093| No fix yet |
| Linux Linux |
|
|
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().
From the CVE record · Linux
The Linux kernel’s qede driver can use a NULL pointer when an skb allocation fails under memory pressure, causing a kernel panic. The input does not establish whether an attacker can trigger this remotely or locally, or whether authentication or user interaction is required.
Operators running Linux kernels with the qede driver should check whether their kernel includes the fix; affected versions were not specified.