In the Linux kernel, the following vulnerability has been resolved: wifi: cfg80211: don't filter…

Why it is Amber

• CVSS 8.8 high
• On your watchlist: linux kernel

References

• https://git.kernel.org/stable/c/0aa44982125c86b47961be5ac1c82eddab8080f3
• https://git.kernel.org/stable/c/1380ee3a202dbb9f8e8b3c3b87eb410450d57799
• https://git.kernel.org/stable/c/64e23a36d8f04811372365b44cfca325f8e0f4bb
• https://git.kernel.org/stable/c/65fdb973bd905bc3f5cb045a04c1828f2d2a7e24
• https://git.kernel.org/stable/c/6d2fd26185678038ef2ea11dd4d2e6eccbf2dd25
• https://git.kernel.org/stable/c/6ef87a853327434ae1cd9c5a2c27a557fb4047fc
• https://git.kernel.org/stable/c/b377e1000d963e7182a987082b4b06580bd7ac84
• https://git.kernel.org/stable/c/fb445ec7480da5d2b82bf681e3b4313603722729

Original description

In the Linux kernel, the following vulnerability has been resolved: wifi: cfg80211: don't filter by BSS type when removing stale entries When an assoc AP switches to a channel that already has a BSS entry, cfg80211_update_assoc_bss_entry() removes that entry before rehashing the real one, since the two would otherwise collide in the BSS rbtree. The lookup for that entry also required it to match the connection's BSS type, so an entry advertising e.g. the IBSS capability bit was left in place, and the following cfg80211_rehash_bss() then ran into it: WARN_ON(!cmp) Changing the type shouldn't really happen, but can be triggered by a rogue AP/device, so drop the check and remove any entries matching the comparison.