GCVE Workshop - 22 September 2026 (14:00-18:00), Luxembourg Before The Vulnopticon Conference - Registration

GHSA-QPMF-FC23-R543

Vulnerability from github – Published: 2026-08-15 15:30 – Updated: 2026-08-17 06:33
VLAI
Details

In the Linux kernel, the following vulnerability has been resolved:

wifi: mac80211: fix tid_tx use-after-free on BA session stop

ieee80211_stop_tx_ba_cb() hands tid_tx to kfree_rcu() through ieee80211_remove_tid_tx(), and then reads tid_tx->ndp after dropping sta->lock:

ieee80211_remove_tid_tx(sta, tid);  /* kfree_rcu(tid_tx, rcu_head) */
...
spin_unlock_bh(&sta->lock);

if (start_txq)
    ieee80211_agg_start_txq(sta, tid, false);

if (send_delba)
    ieee80211_send_delba(..., tid_tx->ndp);

That read is not covered by an RCU read-side critical section, and it runs in preemptible process context: both callers hold the wiphy mutex, reaching it either from the ieee80211_ba_session_work() wiphy work or from ieee80211_sta_tear_down_BA_sessions() during station teardown. Softirqs can run in that window too, both from the local_bh_enable() that ends ieee80211_agg_start_txq() and from any interrupt exit, so the RCU callback can free tid_tx before the read.

Driving the function from a test module with the grace period forced into that window, KASAN reports the read, and the free arrives on the ordinary RCU softirq path:

BUG: KASAN: slab-use-after-free in ieee80211_stop_tx_ba_cb+0x3cd/0x400 Read of size 1 at addr ffff888002b9f52e by task kworker/0:1/10 [...] Freed by task 57: __kasan_slab_free+0x47/0x70 __rcu_free_sheaf_prepare+0x70/0x250 rcu_free_sheaf_nobarn+0x18/0x40 rcu_core+0x426/0x1310 handle_softirqs+0x144/0x590 __irq_exit_rcu+0xea/0x150 irq_exit_rcu+0x9/0x20 sysvec_apic_timer_interrupt+0x6b/0x80 asm_sysvec_apic_timer_interrupt+0x1a/0x20

send_delba is only set when tx_stop is set, which happens for AGG_STOP_LOCAL_REQUEST alone, so this is reached on local teardown - session idle timeout, PTK rekey, suspend, HW reconfig - and not from a peer's DELBA.

Read ndp into a local before the session is freed, while sta->lock is still held. tid_tx->ndp has a single writer, in ieee80211_tx_ba_session_handle_start(), which cannot run concurrently here: both paths are serialised by the wiphy mutex, and the session is already marked HT_AGG_STATE_STOPPING at this point. tid_tx->ndp is also the only tid_tx dereference left after ieee80211_remove_tid_tx() in this function.

[move/change the comment a bit to be more general not just on ndp, initialize ndp directly]

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-74489"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-08-15T13:17:53Z",
    "severity": "HIGH"
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: mac80211: fix tid_tx use-after-free on BA session stop\n\nieee80211_stop_tx_ba_cb() hands tid_tx to kfree_rcu() through\nieee80211_remove_tid_tx(), and then reads tid_tx-\u003endp after dropping\nsta-\u003elock:\n\n\tieee80211_remove_tid_tx(sta, tid);\t/* kfree_rcu(tid_tx, rcu_head) */\n\t...\n\tspin_unlock_bh(\u0026sta-\u003elock);\n\n\tif (start_txq)\n\t\tieee80211_agg_start_txq(sta, tid, false);\n\n\tif (send_delba)\n\t\tieee80211_send_delba(..., tid_tx-\u003endp);\n\nThat read is not covered by an RCU read-side critical section, and it runs\nin preemptible process context: both callers hold the wiphy mutex, reaching\nit either from the ieee80211_ba_session_work() wiphy work or from\nieee80211_sta_tear_down_BA_sessions() during station teardown.\nSoftirqs can run in that window too, both from the local_bh_enable() that\nends ieee80211_agg_start_txq() and from any interrupt exit, so the RCU\ncallback can free tid_tx before the read.\n\nDriving the function from a test module with the grace period forced into\nthat window, KASAN reports the read, and the free arrives on the ordinary\nRCU softirq path:\n\n  BUG: KASAN: slab-use-after-free in ieee80211_stop_tx_ba_cb+0x3cd/0x400\n  Read of size 1 at addr ffff888002b9f52e by task kworker/0:1/10\n  [...]\n  Freed by task 57:\n   __kasan_slab_free+0x47/0x70\n   __rcu_free_sheaf_prepare+0x70/0x250\n   rcu_free_sheaf_nobarn+0x18/0x40\n   rcu_core+0x426/0x1310\n   handle_softirqs+0x144/0x590\n   __irq_exit_rcu+0xea/0x150\n   irq_exit_rcu+0x9/0x20\n   sysvec_apic_timer_interrupt+0x6b/0x80\n   asm_sysvec_apic_timer_interrupt+0x1a/0x20\n\nsend_delba is only set when tx_stop is set, which happens for\nAGG_STOP_LOCAL_REQUEST alone, so this is reached on local teardown -\nsession idle timeout, PTK rekey, suspend, HW reconfig - and not from a\npeer\u0027s DELBA.\n\nRead ndp into a local before the session is freed, while sta-\u003elock is still\nheld. tid_tx-\u003endp has a single writer, in\nieee80211_tx_ba_session_handle_start(), which cannot run concurrently here:\nboth paths are serialised by the wiphy mutex, and the session is already\nmarked HT_AGG_STATE_STOPPING at this point. tid_tx-\u003endp is also the only\ntid_tx dereference left after ieee80211_remove_tid_tx() in this function.\n\n[move/change the comment a bit to be more general not just on ndp,\n initialize ndp directly]",
  "id": "GHSA-qpmf-fc23-r543",
  "modified": "2026-08-17T06:33:49Z",
  "published": "2026-08-15T15:30:34Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-74489"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/09fc36eec7841cdf732f4db39855e0c73bd075cc"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/2f067f5a450ea07efd249142a11d940a068fe29c"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ]
}



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…

Loading…