{ "schema_version": "1.6.1", "id": "RPI-CVE-2023-53540", "modified": "2026-10-09T11:39:44Z", "upstream": [ "CVE-2023-53540" ], "published": "2025-10-04T15:17:41Z", "summary": "wifi: cfg80211: reject auth/assoc to AP with our address", "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: cfg80211: reject auth/assoc to AP with our address\n\nIf the AP uses our own address as its MLD address or BSSID, then\nclearly something's wrong. Reject such connections so we don't\ntry and fail later.", "severity": [ { "type": "CVSS_V3", "score": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H" } ], "affected": [ { "package": { "ecosystem": "Raspberry Pi OS:12", "name": "linux" }, "versions": [ "1:6.1.21-1+rpt1", "1:6.1.47-1+rpt2", "1:6.1.47-1+rpt4", "1:6.1.54-1+rpt2" ], "ecosystem_specific": { "binaries": [ { "binary_name": "linux-image-6.1.0-rpi1-rpi-v6", "binary_version": "1:6.1.21-1+rpt1" }, { "binary_name": "linux-image-6.1.0-rpi1-rpi-v7", "binary_version": "1:6.1.21-1+rpt1" }, { "binary_name": "linux-image-6.1.0-rpi1-rpi-v7l", "binary_version": "1:6.1.21-1+rpt1" }, { "binary_name": "linux-image-6.1.0-rpi1-rpi-v8", "binary_version": "1:6.1.21-1+rpt1" }, { "binary_name": "linux-image-6.1.0-rpi2-rpi-v6", "binary_version": "1:6.1.47-1+rpt2" }, { "binary_name": "linux-image-6.1.0-rpi2-rpi-v7", "binary_version": "1:6.1.47-1+rpt2" }, { "binary_name": "linux-image-6.1.0-rpi2-rpi-v7l", "binary_version": "1:6.1.47-1+rpt2" }, { "binary_name": "linux-image-6.1.0-rpi2-rpi-v8", "binary_version": "1:6.1.47-1+rpt2" }, { "binary_name": "linux-image-6.1.0-rpi3-rpi-2712", "binary_version": "1:6.1.47-1+rpt4" }, { "binary_name": "linux-image-6.1.0-rpi3-rpi-v6", "binary_version": "1:6.1.47-1+rpt4" }, { "binary_name": "linux-image-6.1.0-rpi3-rpi-v7", "binary_version": "1:6.1.47-1+rpt4" }, { "binary_name": "linux-image-6.1.0-rpi3-rpi-v7l", "binary_version": "1:6.1.47-1+rpt4" }, { "binary_name": "linux-image-6.1.0-rpi3-rpi-v8", "binary_version": "1:6.1.47-1+rpt4" }, { "binary_name": "linux-image-6.1.0-rpi4-rpi-2712", "binary_version": "1:6.1.54-1+rpt2" }, { "binary_name": "linux-image-6.1.0-rpi4-rpi-v6", "binary_version": "1:6.1.54-1+rpt2" }, { "binary_name": "linux-image-6.1.0-rpi4-rpi-v7", "binary_version": "1:6.1.54-1+rpt2" }, { "binary_name": "linux-image-6.1.0-rpi4-rpi-v7l", "binary_version": "1:6.1.54-1+rpt2" }, { "binary_name": "linux-image-6.1.0-rpi4-rpi-v8", "binary_version": "1:6.1.54-1+rpt2" } ] }, "database_specific": { "per_version": { "1:6.1.21-1+rpt1": { "linux_commit": "0afb5e98488aed7017b9bf321b575d0177feb7ed", "upstream_version": "6.1.21", "assessment": "commit ancestry (strak rule)", "upstream_fixed": "6.1.55" }, "1:6.1.47-1+rpt2": { "linux_commit": "655fc658a15ae7a6f37103754adb39ba52a9a14e", "upstream_version": "6.1.47", "assessment": "commit ancestry (strak rule)", "upstream_fixed": "6.1.55" }, "1:6.1.47-1+rpt4": { "linux_commit": "655fc658a15ae7a6f37103754adb39ba52a9a14e", "upstream_version": "6.1.47", "assessment": "commit ancestry (strak rule)", "upstream_fixed": "6.1.55", "compiled_filter": false }, "1:6.1.54-1+rpt2": { "linux_commit": "2906f7abdc03d4a92b6b0e2e0c87ea2a9dffe8f7", "upstream_version": "6.1.54", "assessment": "commit ancestry (strak rule)", "upstream_fixed": "6.1.55" } } } } ], "references": [ { "type": "ADVISORY", "url": "https://www.cve.org/CVERecord?id=CVE-2023-53540" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/676a423410131d111a264d29aecbe6aadd57fb22" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/07added2c6cd63de047bc786b39436322abb67c0" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/5d4e04bf3a0f098bd9033de3a5291810fa14c7a6" } ], "database_specific": { "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git", "upstream_modified": "2026-08-05T11:24:39Z", "severity": { "source": "kernel CNA", "cvss_v3_score": 7.1, "cvss_v3_severity": "High", "scenario": "AV:A - The BSS parameters that trigger the bug originate from attacker-transmitted beacon/probe-response frames, which cfg80211 accepts into the scan cache without rejecting a BSSID equal to a local interface address; an attacker in WiFi range can therefore induce the victim's SME to auth/assoc to a self-addressed BSS. Per WiFi frame-injection guidance this is Adjacent.\nAC:L - The attacker fully controls the beacon's BSSID/MLD address and SSID, and the victim STA's MAC address is passively observable from its probe requests; the victim's connection attempt is routine auto-join behavior that the attacker can force by deauthing it from its real AP.\nPR:N - A rogue AP needs no credentials or prior association with the victim, and the failure occurs in the pre-authentication auth/assoc path before any key exchange.\nUI:N - Automatic reconnection to a known/matching SSID by wpa_supplicant or the kernel SME requires no human action, and the attacker can trigger it on demand with a deauth.\nS:U - The WARN_ON and the corrupted MLME state are entirely within the kernel's own security authority; no VM, IOMMU, or sandbox boundary is crossed.\nC:N - No out-of-bounds read, uninitialized memory disclosure, or other read primitive is created; the attacker gains no access to kernel or user data.\nI:L - The attacker's rogue BSS causes mac80211 to tear down the legitimate association and leaves inconsistent state behind (`vif.cfg.ap_addr` set to the interface's own address, and in the MLO case a link_sta bearing our own address inserted into `local->link_sta_hash`), a bounded modification of kernel connection state rather than arbitrary write.\nA:H - The path reaches `WARN_ON()` in `sta_info_insert_check()`, which is a kernel panic on the many deployments running `panic_on_warn=1`, and can be triggered repeatedly to persistently deny WiFi connectivity." } } }