CVE-2024-26961: mac802154: fix llsec key resources release in mac802154_llsec_key_del
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.24% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 068ab2759bc0b4daf0b964de61b2731449c86531, 20d3e1c8a1847497269f04d874b2a5818ec29e2d, 49c8951680d7b76fceaee89dcfbab1363fb24fd1; azl3 hyperv-daemons 6.6.22.1-2 on Azure Linux 3.0 6.6.35.1-1; azl3 hyperv-daemons 6.6.35.1-1 on Azure Linux 3.0 6.6.35.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 068ab2759bc0b4daf0b964de61b2731449c86531, 20d3e1c8a1847497269f04d874b2a5818ec29e2d, 49c8951680d7b76fceaee89dcfbab1363fb24fd1; azl3 hyperv-daemons 6.6.22.1-2 on Azure Linux 3.0 6.6.35.1-1; azl3 hyperv-daemons 6.6.35.1-1 on Azure Linux 3.0 6.6.35.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: mac802154: fix llsec key resources release in mac802154_llsec_key_del mac802154_llsec_key_del() can free resources of a key directly without following the RCU rules for waiting before the end of a grace period. This may lead to use-after-free in case llsec_lookup_key() is traversing the list of keys in parallel with a key deletion: refcount_t: addition on 0; use-after-free. WARNING: CPU: 4 PID: 16000 at lib/refcount.c:25 refcount_warn_saturate+0x162/0x2a0 Modules linked in: CPU: 4 PID: 16000 Comm: wpan-ping Not tainted 6.7.0 #19 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/01/2014 RIP: 0010:refcount_warn_saturate+0x162/0x2a0 Call Trace: <TASK> llsec_lookup_key.isra.0+0x890/0x9e0 mac802154_llsec_encrypt+0x30c/0x9c0 ieee802154_subif_start_xmit+0x24/0x1e0 dev_hard_start_xmit+0x13e/0x690 sch_direct_xmit+0x2ae/0xbc0 __dev_queue_xmit+0x11dd/0x3c20 dgram_sendmsg+0x90b/0xd60 __sys_sendto+0x466/0x4c0 __x64_sys_sendto+0xe0/0x1c0 do_syscall_64+0x45/0xf0 entry_SYSCALL_64_after_hwframe+0x6e/0x76 Also, ieee802154_llsec_key_entry structures are not freed by mac802154_llsec_key_del(): unreferenced object 0xffff8880613b6980 (size 64): comm "iwpan", pid 2176, jiffies 4294761134 (age 60.475s) hex dump (first 32 bytes): 78 0d 8f 18 80 88 ff ff 22 01 00 00 00 00 ad de x......."....... 00 00 00 00 00 00 00 00 03 00 cd ab 00 00 00 00 ................ backtrace: [<ffffffff81dcfa62>] __kmem_cache_alloc_node+0x1e2/0x2d0 [<ffffffff81c43865>] kmalloc_trace+0x25/0xc0 [<ffffffff88968b09>] mac802154_llsec_key_add+0xac9/0xcf0 [<ffffffff8896e41a>] ieee802154_add_llsec_key+0x5a/0x80 [<ffffffff8892adc6>] nl802154_add_llsec_key+0x426/0x5b0 [<ffffffff86ff293e>] genl_family_rcv_msg_doit+0x1fe/0x2f0 [<ffffffff86ff46d1>] genl_rcv_msg+0x531/0x7d0 [<ffffffff86fee7a9>] netlink_rcv_skb+0x169/0x440 [<ffffffff86ff1d88>] genl_rcv+0x28/0x40 [<ffffffff86fec15c>] netlink_unicast+0x53c/0x820 [<ffffffff86fecd8b>] netlink_sendmsg+0x93b/0xe60 [<ffffffff86b91b35>] ____sys_sendmsg+0xac5/0xca0 [<ffffffff86b9c3dd>] ___sys_sendmsg+0x11d/0x1c0 [<ffffffff86b9c65a>] __sys_sendmsg+0xfa/0x1d0 [<ffffffff88eadbf5>] do_syscall_64+0x45/0xf0 [<ffffffff890000ea>] entry_SYSCALL_64_after_hwframe+0x6e/0x76 Handle the proper resource release in the RCU callback function mac802154_llsec_key_del_rcu(). Note that if llsec_lookup_key() finds a key, it gets a refcount via llsec_key_get() and locally copies key id from key_entry (which is a list element). So it's safe to call llsec_key_put() and free the list entry after the RCU grace period elapses. Found by Linux Verification Center (linuxtesting.org).
- Published
- May 1, 2024
- Updated
- Oct 15, 2026
- EPSS
- 0.2% · 15th percentile
- CWE
- CWE-416
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.8
- CNA · Linux
- 7.0
- 0.8 point gap
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 3.16affected
- 5d637d5aabd85132bd85779677d8acb708e0ed90 and later · before 068ab2759bc0b4daf0b964de61b2731449c86531affected · git
- 5d637d5aabd85132bd85779677d8acb708e0ed90 and later · before d3d858650933d44ac12c1f31337e7110c2071821affected · git
- 5d637d5aabd85132bd85779677d8acb708e0ed90 and later · before dcd51ab42b7a0431575689c5f74b8b6efd45fc2faffected · git
- 5d637d5aabd85132bd85779677d8acb708e0ed90 and later · before 20d3e1c8a1847497269f04d874b2a5818ec29e2daffected · git
- 5d637d5aabd85132bd85779677d8acb708e0ed90 and later · before 640297c3e897bd7e1481466a6a5cb9560f1edb88affected · git
- 5d637d5aabd85132bd85779677d8acb708e0ed90 and later · before 49c8951680d7b76fceaee89dcfbab1363fb24fd1affected · git
- 5d637d5aabd85132bd85779677d8acb708e0ed90 and later · before e8a1e58345cf40b7b272e08ac7b32328b2543e40affected · git
- before 3.16not affected · semver
- 5.10.215 and later · up to and including 5.10.*not affected · semver
Affected versions · NVD (6)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel3.16 and later · before 5.10.215
- linux linux kernel5.11 and later · before 5.15.154
- linux linux kernel5.16 and later · before 6.1.84
- linux linux kernel6.2 and later · before 6.6.24
- linux linux kernel6.7 and later · before 6.7.12
- linux linux kernel6.8 and later · before 6.8.3
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:9 | bpftool | before 7.3.0-427.42.1.el9_4 | 7.3.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-64k | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-64k-core | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-core | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-devel | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-devel-matched | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-modules | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-modules-core | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-modules-extra | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-64k-devel | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-64k-devel-matched | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-64k-modules | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-64k-modules-core | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-64k-modules-extra | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-abi-stablelists | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-core | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-cross-headers | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-debug | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-debug-core | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-debug-devel | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-debug-devel-matched | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-debug-modules | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-26958May 1, 2024 · nfs: fix UAF in direct writes31Monitor
- ← EarlierCVE-2024-26960May 1, 2024 · mm: swap: fix race between free_swap_and_cache() and swapoff()28Monitor
- Later →CVE-2024-26973May 1, 2024 · fat: fix uninitialized field in nostale filehandles22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 068ab2759bc0b4daf0b964de61b2731449c86531 | Vendor (CNA) |
| Linux Linux | 20d3e1c8a1847497269f04d874b2a5818ec29e2d | Vendor (CNA) |
| Linux Linux | 49c8951680d7b76fceaee89dcfbab1363fb24fd1 | Vendor (CNA) |
| Linux Linux | 640297c3e897bd7e1481466a6a5cb9560f1edb88 | Vendor (CNA) |
| Linux Linux | d3d858650933d44ac12c1f31337e7110c2071821 | Vendor (CNA) |
| Linux Linux | dcd51ab42b7a0431575689c5f74b8b6efd45fc2f | Vendor (CNA) |
| Linux Linux | e8a1e58345cf40b7b272e08ac7b32328b2543e40 | Vendor (CNA) |
| azl3 hyperv-daemons 6.6.22.1-2 on Azure Linux 3.0 | 6.6.35.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 hyperv-daemons 6.6.35.1-1 on Azure Linux 3.0 | 6.6.35.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 hyperv-daemons 5.15.153.1-1 on CBL Mariner 2.0 | 5.15.158.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 hyperv-daemons 5.15.158.1-1 on CBL Mariner 2.0 | 5.15.158.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| almalinux:bpftool | 7.3.0-427.42.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel | 5.14.0-427.42.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k | 5.14.0-427.42.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-core | 5.14.0-427.42.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 5.14.0-427.42.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 5.14.0-427.42.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 5.14.0-427.42.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 5.14.0-427.42.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 5.14.0-427.42.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 5.14.0-427.42.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 5.14.0-427.42.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 5.14.0-427.42.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| debian:linux | 6.1.85-1 · Debian:12 | Package registry (OSV) |
| red hat:bpftool | 0:4.18.0-477.81.1.el8_8 · Red Hat:rhel_eus:8.8::baseos | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:4.18.0-477.81.1.el8_8 · Red Hat:rhel_eus:8.8::baseos | Package registry (OSV) |
| red hat:kernel | 0:4.18.0-477.81.1.el8_8 · Red Hat:rhel_eus:8.8::baseos | Package registry (OSV) |
| red hat:kernel-abi-stablelists | 0:4.18.0-477.81.1.el8_8 · Red Hat:rhel_eus:8.8::baseos | Package registry (OSV) |
| red hat:kernel-core | 0:4.18.0-477.81.1.el8_8 · Red Hat:rhel_eus:8.8::baseos | Package registry (OSV) |
| red hat:kernel-debug | 0:4.18.0-477.81.1.el8_8 · Red Hat:rhel_eus:8.8::baseos | Package registry (OSV) |
+7
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-0387 · May 2, 2024(Linux Kernel Güncellemesi)
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- git.kernel.org/stable/c/20d3e1c8a1847497269f04d874b2a5818ec29e2d
- git.kernel.org/stable/c/49c8951680d7b76fceaee89dcfbab1363fb24fd1
- git.kernel.org/stable/c/640297c3e897bd7e1481466a6a5cb9560f1edb88
- git.kernel.org/stable/c/d3d858650933d44ac12c1f31337e7110c2071821
- git.kernel.org/stable/c/dcd51ab42b7a0431575689c5f74b8b6efd45fc2f
- git.kernel.org/stable/c/e8a1e58345cf40b7b272e08ac7b32328b2543e40
- lists.debian.org/debian-lts-announce/2024/06/msg00017.html
- cert-portal.siemens.com/productcert/html/ssa-265688.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.