CVE-2022-49084
qede: confirm skb is allocated before using
- 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
- 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: 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().
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
4.18
References 7
git.kernel.org
- stable/c/9648adb1b3ece55c657d3a4f52bfee663b710dfe
- stable/c/034a92c6a81048128fc7b18d278d52438a13902a
- stable/c/8928239e5e2e460d95b8a0b89f61671625e7ece0
- stable/c/c9bdce2359b5f4986eb38d1e81865b3586cc20d2
- stable/c/b2d6b3db9d1cf80908964036dbe1c52a86b1afb1
- stable/c/e1fd0c42acfa22bb34d2ab6a111484f466ab8093
- stable/c/4e910dbe36508654a896d5735b318c0b88172570