wifi: cfg80211: detect stuck ECSA element in probe resp
In the Linux kernel, the following vulnerability has been resolved: wifi: cfg80211: detect stuck ECSA element in probe resp We recently added some validation that we don't try to connect to an AP that is currently in a channel switch process, since that might want the channel to be quiet or we might not be able to connect in time to hear the switching in a beacon. This was in commit c09c4f31998b ("wifi: mac80211: don't connect to an AP while it's in a CSA process"). However, we promptly got a report that this caused new connection failures, and it turns out that the AP that we now cannot connect to is permanently advertising an extended channel switch announcement, even with quiet. The AP in question was an Asus RT-AC53, with firmware 3.0.0.4.380_10760-g21a5898. As a first step, attempt to detect that we're dealing with such a situation, so mac80211 can use this later.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.7.5
- CVEs
- CVE-2024-26683
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 2 Nov 2026, 23:16 UTC · Revision 1
Source evidence
wifi: cfg80211: detect stuck ECSA element in probe resp
core-osv · Original sourcePublished 2 Apr 2024, 07:01 UTC
In the Linux kernel, the following vulnerability has been resolved: wifi: cfg80211: detect stuck ECSA element in probe resp We recently added some validation that we don't try to connect to an AP that is currently in a channel switch process, since that might want the channel to be quiet or we might not be able to connect in time to hear the switching in a beacon. This was in commit c09c4f31998b ("wifi: mac80211: don't connect to an AP while it's in a CSA process"). However, we promptly got a report that this caused new connection failures, and it turns out that the AP that we now cannot connect to is permanently advertising an extended channel switch announcement, even with quiet. The AP in question was an Asus RT-AC53, with firmware 3.0.0.4.380_10760-g21a5898. As a first step, attempt to detect that we're dealing with such a situation, so mac80211 can use this later.
osv:CVE-2024-26683
Kernel
Fixed versions: 6.7.5
Complete source record
{
"id": "ae8c971b2d4a0c566aaed06694663bb6229088d3dbb832d6f8845a91ff1a36c5",
"url": "https://osv.dev/vulnerability/CVE-2024-26683",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "wifi: cfg80211: detect stuck ECSA element in probe resp",
"summary": "In the Linux kernel, the following vulnerability has been resolved: wifi: cfg80211: detect stuck ECSA element in probe resp We recently added some validation that we don't try to connect to an AP that is currently in a channel switch process, since that might want the channel to be quiet or we might not be able to connect in time to hear the switching in a beacon. This was in commit c09c4f31998b (\"wifi: mac80211: don't connect to an AP while it's in a CSA process\"). However, we promptly got a report that this caused new connection failures, and it turns out that the AP that we now cannot connect to is permanently advertising an extended channel switch announcement, even with quiet. The AP in question was an Asus RT-AC53, with firmware 3.0.0.4.380_10760-g21a5898. As a first step, attempt to detect that we're dealing with such a situation, so mac80211 can use this later.",
"evidence": "osv:CVE-2024-26683",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.7.5",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2024-26683",
"aliases": [
"CVE-2024-26683"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "c09c4f31998bac6d73508e38812518aceb069b68"
},
{
"fixed": "ce112c941c2b172afba3e913a90c380647d53975"
},
{
"fixed": "177fbbcb4ed6b306c1626a277fac3fb1c495a4c7"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-26683.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.7.5"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-26683.json"
}
}
],
"modified": "2026-10-28T02:30:24.537790005Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/177fbbcb4ed6b306c1626a277fac3fb1c495a4c7",
"https://git.kernel.org/stable/c/ce112c941c2b172afba3e913a90c380647d53975",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/26xxx/CVE-2024-26683.json",
"https://nvd.nist.gov/vuln/detail/CVE-2024-26683",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/26xxx/CVE-2024-26683.json"
}
},
"related_cves": [
{
"value": "CVE-2024-26683",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 490817,
"published_at": "2024-04-02T07:01:45.996+00:00"
}