net: team: free skb when broadcast has no txable port
- 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.18.57, 7.2.11
- 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: net: team: free skb when broadcast has no txable port bc_transmit() sends the original skb through the last txable port. When no port is txable, it returns false without consuming the skb, but team_xmit() still returns NETDEV_TX_OK. AF_PACKET sends then retain the skb and its socket write-memory charge. A TX-enabled, link-down port keeps the broadcast transmit op installed. Carrier can stay up through a second link-up, TX-disabled port or be forced on by userspace. Free the original skb on the no-port path while leaving the existing drop accounting intact. Discovered by Sashiko during review of previous commit.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Linux Linux
From 5fc889911a99043a97da1daa0d010ad72cbc3042 · fixed in 961563117626f4681623077ec0cfd86f86da0d49; From 5fc889911a99043a97da1daa0d010ad72cbc3042 · fixed in f34b1bcac4581a5bd3daf9eff90f175e736b54aa; From 5fc889911a99043a97da1daa0d010ad72cbc3042 · fixed in 489114c9ecae44e523361a4b3e610ee5ebd9189c
- Linux Linux
3.6
- KernelLinux
From 3.6.0 · fixed in 6.18.57; From 6.19.0 · fixed in 7.2.11