batman-adv: fix stale receive device on merged fragments
- 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 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110, and 2 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
Summary
In the Linux kernel, the following vulnerability has been resolved: batman-adv: fix stale receive device on merged fragments Fragment reassembly reuses the skb from the highest-numbered buffered fragment as the merged packet. When that fragment was received on a hard interface which is deleted before the chain completes, the merged skb can re-enter the receive path with a stale skb->dev and skb_iif. batadv_batman_skb_recv() passes such merged packets through the normal receive handlers again. DAT and bridge loop avoidance both derive the ARP header length from skb->dev, so they can dereference the freed net_device before the packet reaches the local mesh interface. Refresh the receive device metadata from the current receive device before running the packet handlers. This keeps internally reinjected merged fragments consistent with the normal receive path after hard interface teardown.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 610bfc6bc99bc83680d190ebc69359a05fc7f605 · fixed in 63d86250fa7cbe22451369bd1c0881dfc8190958; From 610bfc6bc99bc83680d190ebc69359a05fc7f605 · fixed in f830c2dfc1431764db9256b3d5db1695fc9a7f56; From 610bfc6bc99bc83680d190ebc69359a05fc7f605 · fixed in f4b4ae763b5d59319fad62a00c76676758e7dafa; From 610bfc6bc99bc83680d190ebc69359a05fc7f605 · fixed in 6df64825f8b199921120c685af2abca14b077331; From 610bfc6bc99bc83680d190ebc69359a05fc7f605 · fixed in a2c272da99c2077088083c14961cf2f1e4506995; From 610bfc6bc99bc83680d190ebc69359a05fc7f605 · fixed in e91d2cc7441d89a45bad73ad9789159c7441cb80; From 610bfc6bc99bc83680d190ebc69359a05fc7f605 · fixed in 2dffc8c44b6e3347b3719c6419c07b4a18fea895; From 610bfc6bc99bc83680d190ebc69359a05fc7f605 · fixed in ad46c907d7d9975a285c1e89a4adde652eaa93f5
- Linux Linux
3.13
- KernelLinux
From 3.13.0 · fixed in 5.10.270; From 5.11.0 · fixed in 5.15.221; From 5.16.0 · fixed in 6.1.188; From 6.2.0 · fixed in 6.6.157; From 6.7.0 · fixed in 6.12.110; From 6.13.0 · fixed in 6.18.51; From 6.19.0 · fixed in 7.2.5
References 8
git.kernel.org
- stable/c/63d86250fa7cbe22451369bd1c0881dfc8190958
- stable/c/f830c2dfc1431764db9256b3d5db1695fc9a7f56
- stable/c/f4b4ae763b5d59319fad62a00c76676758e7dafa
- stable/c/6df64825f8b199921120c685af2abca14b077331
- stable/c/a2c272da99c2077088083c14961cf2f1e4506995
- stable/c/e91d2cc7441d89a45bad73ad9789159c7441cb80
- stable/c/2dffc8c44b6e3347b3719c6419c07b4a18fea895
- stable/c/ad46c907d7d9975a285c1e89a4adde652eaa93f5