CVE-2023-52530

wifi: mac80211: fix potential key use-after-free

HIGH

7.8

CVSS Score

Published: March 2, 2024 at 09:52 PM UTC

Updated: August 5, 2026 at 09:25 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

HIGH7.8

Exploit prediction

EPSS 0.3%

SSVC

No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: fix potential key use-after-free When ieee80211_key_link() is called by ieee80211_gtk_rekey_add() but returns 0 due to KRACK protection (identical key reinstall), ieee80211_gtk_rekey_add() will still return a pointer into the key, in a potential use-after-free. This normally doesn't happen since it's only called by iwlwifi in case of WoWLAN rekey offload which has its own KRACK protection, but still better to fix, do that by returning an error code and converting that to success on the cfg80211 boundary only, leaving the error for bad callers of ieee80211_gtk_rekey_add().

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

v ≥ 3.16.50v ≥ 3.18.82v ≥ 3.2.95v ≥ 4.1.47v ≥ 4.13.14v ≥ 4.4.99v ≥ 4.9.633.16.50 ≤ v < 3.173.18.82 ≤ v < 3.193.2.95 ≤ v < 3.34.1.47 ≤ v < 4.24.13.14 ≤ v < 4.144.14 ≤ v < 5.10.2284.14 ≤ v < 5.15.1694.14 ≤ v < 5.4.2854.14 ≤ v < 6.1.574.14 ≤ v < 6.5.74.14 ≤ v < 6.64.4.99 ≤ v < 4.54.9.63 ≤ v < 4.105.11 ≤ v < 5.15.1695.16 ≤ v < 6.1.575.5 ≤ v < 5.10.2886.2 ≤ v < 6.5.72586fa0007dc6b7745da14250be7e3aae706b1283.16.50 3.18.82 3.2.953aa22c9619b49efe950aca3aebd1235a4940d4.1.47 4.13.14 4.4.99 4.9.63 6.6 rc1 6.6 rc2 6.6 rc3 6.6 rc46440f0ee8a1779f53526bccb9de00914daeb90946891c6fd2a500d1f39d1426765f610bdc2c2a39da0a8a11d1630cd648dc1ce86da620b4e240e0315a9ab1b2e30e898440a22d7b1d7a5b0b7c6a8791fef810e7c3d2a8fb3bbd23726599c487c30ea747efdf7cb4185b60c68e1a75e61691c4afdc15dea0e

Vendor states this is fixed in 2408f491ff998d674707725eadc47d8930aced09 (fixed)

Vendor states this is fixed in 2f4e16e39e4f5e78248dd9e51276a83203950b36 (fixed)

Vendor states this is fixed in 31db78a4923ef5e2008f2eed321811ca79e7f71b (fixed)

Vendor states this is fixed in 65c72a7201704574dace708cbc96a8f367b1491d (fixed)

Vendor states this is fixed in e8a834eb09bb95c2bf9c76f1a28ecef7d8c439d0 (fixed)

Vendor states this is fixed in e8e599a635066c50ac214c3e10858f1d37e03022 (fixed)

Affected range stops below 3.17, so it looks safe — our inference, not a vendor statement

Affected range stops below 3.19, so it looks safe — our inference, not a vendor statement

Affected range stops below 3.3, so it looks safe — our inference, not a vendor statement

Affected range stops below 4.10, so it looks safe — our inference, not a vendor statement

Vendor states this is fixed in 4.14 (unaffected)

Affected range stops below 4.2, so it looks safe — our inference, not a vendor statement

Affected range stops below 4.5, so it looks safe — our inference, not a vendor statement

Vendor states this is fixed in 5.10.228 (unaffected)

Affected range stops below 5.10.288, so it looks safe — our inference, not a vendor statement

Vendor states this is fixed in 5.15.169 (unaffected)

Vendor states this is fixed in 5.4.285 (unaffected)

Vendor states this is fixed in 6.1.57 (unaffected)

Vendor states this is fixed in 6.5.7 (unaffected)

Vendor states this is fixed in 6.6 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references