ROOT-OS-UBUNTU-2404-CVE-2025-71227 CVE-2025-71227 in rootio-linux - Patched by Root

Root has patched CVE-2025-71227 in the rootio-linux package for Root:Ubuntu:24.04. Multiple fixed versions available...

ROOT-OS-UBUNTU-2204-CVE-2025-71227 CVE-2025-71227 in rootio-linux - Patched by Root

Root has patched CVE-2025-71227 in the rootio-linux package for Root:Ubuntu:22.04. Multiple fixed versions available...

ROOT-OS-DEBIAN-13-CVE-2025-71227 CVE-2025-71227 in rootio-linux - Patched by Root

Root has patched CVE-2025-71227 in the rootio-linux package for Root:Debian:13. Multiple fixed versions available...

CVE-2025-71227 vulnerabilities

Vulnerabilities for packages: linux-vmware, linux-qemu, linux-aws, linux-azure, linux-gcp...

CVE-2025-71227

creationtimestamp| type| source ---|---|--- 2026-03-19 00:00:00+00:00| seen| https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/...

BELL-CVE-2025-71227

Bulletin has no description...

CVE-2025-71227

A flaw was found in the Linux kernel's mac80211 WiFi subsystem. When a regulatory change disables a channel between the time it is scanned and when a connection attempt is made, a kernel warning WARN is triggered. This fix replaces the warning with a more informative error message, as the warning...

DEBIAN-CVE-2025-71227

In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: don't WARN for connections on invalid channels It's not clear to me how exactly syzbot managed to hit this, but it seems conceivable that e.g. regulatory changed and has disabled a channel between scanning channel...

CVE-2025-71227

In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: don't WARN for connections on invalid channels It's not clear to me how exactly syzbot managed to hit this, but it seems conceivable that e.g. regulatory changed and has disabled a channel between scanning channel...

CVE-2025-71227

In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: don't WARN for connections on invalid channels It's not clear to me how exactly syzbot managed to hit this, but it seems conceivable that e.g. regulatory changed and has disabled a channel between scanning channel...