mlx5: fix skb leak while fifo resync and push
- 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
- Fix
- Fixed in 6.1.18, 6.2.5
- 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
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
In the Linux kernel, the following vulnerability has been resolved: mlx5: fix skb leak while fifo resync and push During ptp resync operation SKBs were poped from the fifo but were never freed neither by napi_consume nor by dev_kfree_skb_any. Add call to napi_consume_skb to properly free SKBs. Another leak was happening because mlx5e_skb_fifo_has_room() had an error in the check. Comparing free running counters works well unless C promotes the types to something wider than the counter. In this case counters are u16 but the result of the substraction is promouted to int and it causes wrong result (negative value) of the check when producer have already overlapped but consumer haven't yet. Explicit cast to u16 fixes the issue.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 58a518948f60153e8f6cb8361d2712aa3a1af94a · fixed in 234cffda95e1049f58e8ec136ef105c633f0ed19; From 58a518948f60153e8f6cb8361d2712aa3a1af94a · fixed in 68504c66d08c70fb92799722e25a932d311d74fd; From 58a518948f60153e8f6cb8361d2712aa3a1af94a · fixed in e435941b1da1a0be4ff8a7ae425774c76a5ac514
- Linux Linux
6.0
- KernelLinux
From 6.0.0 · fixed in 6.1.18; From 6.2.0 · fixed in 6.2.5