FKIE_CVE-2026-46248

Vulnerability from fkie_nvd - Published: 2026-06-03 18:16 - Updated: 2026-06-05 20:51
Severity
Summary
In the Linux kernel, the following vulnerability has been resolved: wifi: ath12k: clear stale link mapping of ahvif->links_map When an arvif is initialized in non-AP STA mode but MLO connection preparation fails before the arvif is created (arvif->is_created remains false), the error path attempts to delete all links. However, link deletion only executes when arvif->is_created is true. As a result, ahvif retains a stale entry of arvif that is initialized but not created. When a new arvif is initialized with the same link id, this stale mapping triggers the following WARN_ON. WARNING: drivers/net/wireless/ath/ath12k/mac.c:4271 at ath12k_mac_op_change_vif_links+0x140/0x180 [ath12k], CPU#3: wpa_supplicant/275 Call trace: ath12k_mac_op_change_vif_links+0x140/0x180 [ath12k] (P) drv_change_vif_links+0xbc/0x1a4 [mac80211] ieee80211_vif_update_links+0x54c/0x6a0 [mac80211] ieee80211_vif_set_links+0x40/0x70 [mac80211] ieee80211_prep_connection+0x84/0x450 [mac80211] ieee80211_mgd_auth+0x200/0x480 [mac80211] ieee80211_auth+0x14/0x20 [mac80211] cfg80211_mlme_auth+0x90/0xf0 [cfg80211] nl80211_authenticate+0x32c/0x380 [cfg80211] genl_family_rcv_msg_doit+0xc8/0x134 Fix this issue by unassigning the link vif and clearing ahvif->links_map if arvif is only initialized but not created. Tested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.5-01651-QCAHKSWPL_SILICONZ-1
Impacted products
Vendor Product Version

{
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: ath12k: clear stale link mapping of ahvif-\u003elinks_map\n\nWhen an arvif is initialized in non-AP STA mode but MLO connection\npreparation fails before the arvif is created\n(arvif-\u003eis_created remains false), the error path attempts to delete all\nlinks. However, link deletion only executes when arvif-\u003eis_created is true.\nAs a result, ahvif retains a stale entry of arvif that is initialized but\nnot created.\n\nWhen a new arvif is initialized with the same link id, this stale mapping\ntriggers the following WARN_ON.\n\nWARNING: drivers/net/wireless/ath/ath12k/mac.c:4271 at ath12k_mac_op_change_vif_links+0x140/0x180 [ath12k], CPU#3: wpa_supplicant/275\n\nCall trace:\n ath12k_mac_op_change_vif_links+0x140/0x180 [ath12k] (P)\n drv_change_vif_links+0xbc/0x1a4 [mac80211]\n ieee80211_vif_update_links+0x54c/0x6a0 [mac80211]\n ieee80211_vif_set_links+0x40/0x70 [mac80211]\n ieee80211_prep_connection+0x84/0x450 [mac80211]\n ieee80211_mgd_auth+0x200/0x480 [mac80211]\n ieee80211_auth+0x14/0x20 [mac80211]\n cfg80211_mlme_auth+0x90/0xf0 [cfg80211]\n nl80211_authenticate+0x32c/0x380 [cfg80211]\n genl_family_rcv_msg_doit+0xc8/0x134\n\nFix this issue by unassigning the link vif and clearing ahvif-\u003elinks_map\nif arvif is only initialized but not created.\n\nTested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.5-01651-QCAHKSWPL_SILICONZ-1"
    }
  ],
  "id": "CVE-2026-46248",
  "lastModified": "2026-06-05T20:51:20.400",
  "metrics": {},
  "published": "2026-06-03T18:16:25.097",
  "references": [
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/2c1ba9c2adf0fda96eaaebd8799268a7506a8fc9"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/acd8319e834be6790e449701cb6df0f636801977"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/da289440f04c93048d82d293b180f1cacdfee2d9"
    }
  ],
  "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
  "vulnStatus": "Awaiting Analysis"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…