netem: fix return value if duplicate enqueue fails
- 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 3.17, 4.10, 4.15, 4.20, 4.21, and 6 more
- 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: partial
Summary
In the Linux kernel, the following vulnerability has been resolved: netem: fix return value if duplicate enqueue fails There is a bug in netem_enqueue() introduced by commit 5845f706388a ("net: netem: fix skb length BUG_ON in __skb_to_sgvec") that can lead to a use-after-free. This commit made netem_enqueue() always return NET_XMIT_SUCCESS when a packet is duplicated, which can cause the parent qdisc's q.qlen to be mistakenly incremented. When this happens qlen_notify() may be skipped on the parent during destruction, leaving a dangling pointer for some classful qdiscs like DRR. There are two ways for the bug happen: • If the duplicated packet is dropped by rootq->enqueue() and then the original packet is also dropped. • If rootq->enqueue() sends the duplicated packet to a different qdisc and the original packet is dropped. In both cases NET_XMIT_SUCCESS is returned even though no packets are enqueued at the netem qdisc. The fix is to defer the enqueue of the duplicate packet until after the original packet has been guaranteed to return NET_XMIT_SUCCESS.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From 5845f706388a4cde0f6b80f9e5d33527e942b7d9 · fixed in 759e3e8c4a6a6b4e52ebc4547123a457f0ce90d4; From 5845f706388a4cde0f6b80f9e5d33527e942b7d9 · fixed in c414000da1c2ea1ba9a5e5bb1a4ba774e51e202d; From 5845f706388a4cde0f6b80f9e5d33527e942b7d9 · fixed in 52d99a69f3d556c6426048c9d481b912205919d8; From 5845f706388a4cde0f6b80f9e5d33527e942b7d9 · fixed in 0486d31dd8198e22b63a4730244b38fffce6d469; From 5845f706388a4cde0f6b80f9e5d33527e942b7d9 · fixed in 577d6c0619467fe90f7e8e57e45cb5bd9d936014; From 5845f706388a4cde0f6b80f9e5d33527e942b7d9 · fixed in e5bb2988a310667abed66c7d3ffa28880cf0f883; From 5845f706388a4cde0f6b80f9e5d33527e942b7d9 · fixed in c07ff8592d57ed258afee5a5e04991a48dbaf382; From 3.16.66 · fixed in 3.17; From 4.9.163 · fixed in 4.10; From 4.14.106 · fixed in 4.15; From 4.19.28 · fixed in 4.20; From 4.20.15 · fixed in 4.21
- Linux Linux
5.0
- KernelLinux
From 5.0.0 · fixed in 5.4.283; From 5.5.0 · fixed in 5.10.225; From 5.11.0 · fixed in 5.15.166; From 5.16.0 · fixed in 6.1.107; From 6.2.0 · fixed in 6.6.48; From 6.7.0 · fixed in 6.10.7
References 7
git.kernel.org
- stable/c/759e3e8c4a6a6b4e52ebc4547123a457f0ce90d4
- stable/c/c414000da1c2ea1ba9a5e5bb1a4ba774e51e202d
- stable/c/52d99a69f3d556c6426048c9d481b912205919d8
- stable/c/0486d31dd8198e22b63a4730244b38fffce6d469
- stable/c/577d6c0619467fe90f7e8e57e45cb5bd9d936014
- stable/c/e5bb2988a310667abed66c7d3ffa28880cf0f883
- stable/c/c07ff8592d57ed258afee5a5e04991a48dbaf382