CVE-2026-98709

In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: count only matching reservations in reserved switch ieee80211_vif_use_reserved_switch() validates a replacement by counting assigned links on ctx->replace_ctx and treating reservations too broadly. A link can still be assigned to the old channel context while holding a reservation that belongs to a different replacement operation. That can make the current replacement appear complete too early. If another link finalizes first, the function can free the WILL_BE_REPLACED chanctx while the unmatched link and driver still use it, leading to a use-after-free in later beacon generation. Require an in-place reservation to point at the current replacement context, and require the reserved and assigned contexts to be the matching replacement pair, before counting or moving the link.

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

wifi: mac80211: count only matching reservations in reserved switch

ieee80211_vif_use_reserved_switch() validates a replacement by counting assigned links on ctx->replace_ctx and treating reservations too broadly. A link can still be assigned to the old channel context while holding a reservation that belongs to a different replacement operation.

That can make the current replacement appear complete too early. If another link finalizes first, the function can free the WILL_BE_REPLACED chanctx while the unmatched link and driver still use it, leading to a use-after-free in later beacon generation.

Require an in-place reservation to point at the current replacement context, and require the reserved and assigned contexts to be the matching replacement pair, before counting or moving the link.

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

wifi: mac80211: count only matching reservations in reserved switch

ieee80211_vif_use_reserved_switch() validates a replacement by counting assigned links on ctx->replace_ctx and treating reservations too broadly. A link can still be assigned to the old channel context while holding a reservation that belongs to a different replacement operation.

That can make the current replacement appear complete too early. If another link finalizes first, the function can free the WILL_BE_REPLACED chanctx while the unmatched link and driver still use it, leading to a use-after-free in later beacon generation.

Require an in-place reservation to point at the current replacement context, and require the reserved and assigned contexts to be the matching replacement pair, before counting or moving the link.

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

wifi: mac80211: count only matching reservations in reserved switch

ieee80211_vif_use_reserved_switch() validates a replacement by counting assigned links on ctx->replace_ctx and treating reservations too broadly. A link can still be assigned to the old channel context while holding a reservation that belongs to a different replacement operation.

That can make the current replacement appear complete too early. If another link finalizes first, the function can free the WILL_BE_REPLACED chanctx while the unmatched link and driver still use it, leading to a use-after-free in later beacon generation.

Require an in-place reservation to point at the current replacement context, and require the reserved and assigned contexts to be the matching replacement pair, before counting or moving the link.

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

wifi: mac80211: count only matching reservations in reserved switch

ieee80211_vif_use_reserved_switch() validates a replacement by counting assigned links on ctx->replace_ctx and treating reservations too broadly. A link can still be assigned to the old channel context while holding a reservation that belongs to a different replacement operation.

That can make the current replacement appear complete too early. If another link finalizes first, the function can free the WILL_BE_REPLACED chanctx while the unmatched link and driver still use it, leading to a use-after-free in later beacon generation.

Require an in-place reservation to point at the current replacement context, and require the reserved and assigned contexts to be the matching replacement pair, before counting or moving the link.

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

wifi: mac80211: count only matching reservations in reserved switch

ieee80211_vif_use_reserved_switch() validates a replacement by counting assigned links on ctx->replace_ctx and treating reservations too broadly. A link can still be assigned to the old channel context while holding a reservation that belongs to a different replacement operation.

That can make the current replacement appear complete too early. If another link finalizes first, the function can free the WILL_BE_REPLACED chanctx while the unmatched link and driver still use it, leading to a use-after-free in later beacon generation.

Require an in-place reservation to point at the current replacement context, and require the reserved and assigned contexts to be the matching replacement pair, before counting or moving the link.

• CVE-2026-46267
  • nfc: hci: shdlc: Stop timers and work before freeing context {CVE-2026-46267}
• CVE-2026-53004
  • sctp: fix OOB write to userspace in sctp_getsockopt_peer_auth_chunks {CVE-2026-53004}
• CVE-2026-98716
  • KVM: SVM: Use the active VMCB's MSR bitmap when checking if MSR is intercepted {CVE-2026-98716}
• CVE-2026-98714
  • KVM: SVM: Update control fields on #VMEXIT if and only if VMRUN succeeded {CVE-2026-98714}
• CVE-2026-98715
  • KVM: SVM: Preserve TLB control (i.e. pending TLB flush) on failed VMRUN {CVE-2026-98715}
• CVE-2026-98662
  • iio: light: gp2ap020a00f: drain irq_work after free_irq {CVE-2026-98662}
• CVE-2026-98430
  • RDMA/efa: Keep admin queues alive while IRQ is registered {CVE-2026-98430}
• CVE-2026-98769
  • usb: gadget: f_uac1_legacy: validate bRequest index in generic_{set,get}_cmd {CVE-2026-98769}
• CVE-2026-98764
  • usb: gadget: f_fs: Fix NULL pointer dereference in FUNCTIONFS_ENDPOINT_DESC {CVE-2026-98764}
• CVE-2026-98763
  • usb: core: clear both ep_in and ep_out for non-ep0 control endpoints {CVE-2026-98763}
• CVE-2026-46064
  • ibmasm: fix heap over-read in ibmasm_send_i2o_message() {CVE-2026-46064}
• CVE-2026-98621
  • net: gue: reject invalid REMCSUM offsets {CVE-2026-98621}
• CVE-2026-98636
  • squashfs: Add dictionary size range check to prevent shift-out-of-bounds {CVE-2026-98636}
• CVE-2026-98771
  • usb: storage: sierra_ms: reject short SWoC info transfers {CVE-2026-98771}
• CVE-2026-98772
  • USB: serial: fix port tear down use-after-free {CVE-2026-98772}
• CVE-2026-53149
  • thunderbolt: Bound root directory content to block size {CVE-2026-53149}
• CVE-2026-46163
  • wifi: b43legacy: enforce bounds check on firmware key index in RX path {CVE-2026-46163}
• CVE-2026-52962
  • ceph: fix a buffer leak in __ceph_setxattr() {CVE-2026-52962}
• CVE-2026-98386
  • scsi: qla2xxx: Use memset_io() to clear QLAFX00 request ring slot {CVE-2026-98386}
• CVE-2026-45916
  • power: supply: sbs-battery: Fix use-after-free in power_supply_changed() {CVE-2026-45916}
• CVE-2026-98555
  • llc: fix skb UAF and leaks on llc_mac_hdr_init() failure {CVE-2026-98555}
• CVE-2023-54243
  • netfilter: ebtables: fix table blob use-after-free {CVE-2023-54243}
• CVE-2026-53255
  • Bluetooth: MGMT: validate advertising TLV before type checks {CVE-2026-53255}
• CVE-2026-98409
  • watchdog: rtd119x: Avoid division by zero {CVE-2026-98409}
• CVE-2026-98598
  • ipv6: Prevent rt6_insert_exception() for dying fib6_info. {CVE-2026-98598}
• CVE-2026-53392
  • NFSv4/flexfiles: reject zero filehandle version count {CVE-2026-53392}
• CVE-2026-98422
  • wifi: mac80211: reset the AP_VLAN tailroom counter on ifdown {CVE-2026-98422}
• CVE-2026-98393
  • net: ipv4: Fix UDP length overflow with PMTU discover and big MTU {CVE-2026-98393}
• CVE-2026-53129
  • fs/mbcache: cancel shrink work before destroying the cache {CVE-2026-53129}
• CVE-2023-53794
  • cifs: fix session state check in reconnect to avoid use-after-free issue {CVE-2023-53794}
• CVE-2026-98494
  • net: atl1: fix soft lockup on out-of-range cmb_tpd_next_to_clean read {CVE-2026-98494}
• CVE-2026-98428
  • ALSA: usb: 6fire: Avoid embedded URBs {CVE-2026-98428}
• CVE-2026-53157
  • net: phonet: free phonet_device after RCU grace period {CVE-2026-53157}
• CVE-2026-98709
  • wifi: mac80211: count only matching reservations in reserved switch {CVE-2026-98709}
• CVE-2026-98614
  • sctp: avoid livelock while updating retransmit path {CVE-2026-98614}
• CVE-2026-98811
  • net/sched: cls_api: reclaim an empty proto on the error path {CVE-2026-98811}
• CVE-2026-43042
  • mpls: add seqcount to protect the…

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

wifi: mac80211: count only matching reservations in reserved switch

ieee80211_vif_use_reserved_switch() validates a replacement by counting assigned links on ctx->replace_ctx and treating reservations too broadly. A link can still be assigned to the old channel context while holding a reservation that belongs to a different replacement operation.

That can make the current replacement appear complete too early. If another link finalizes first, the function can free the WILL_BE_REPLACED chanctx while the unmatched link and driver still use it, leading to a use-after-free in later beacon generation.

Require an in-place reservation to point at the current replacement context, and require the reserved and assigned contexts to be the matching replacement pair, before counting or moving the link.

In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: count only matching reservations in reserved switch ieee80211_vif_use_reserved_switch() validates a replacement by counting assigned links on ctx->replace_ctx and treating reservations too broadly. A link can still be assigned to the old channel context while holding a reservation that belongs to a different replacement operation. That can make the current replacement appear complete too early. If another link finalizes first, the function can free the WILL_BE_REPLACED chanctx while the unmatched link and driver still use it, leading to a use-after-free in later beacon generation. Require an in-place reservation to point at the current replacement context, and require the reserved and assigned contexts to be the matching replacement pair, before counting or moving the link.