NVD / CVE Program· CNA Linux

CVE-2024-26951: wireguard: netlink: check for dangling peer via is_dead instead of empty list

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.23% (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 13d107794304306164481d31ce33f8fdb25a9c04, 302b2dfc013baca3dea7ceda383930d9297d231d, 55b6c738673871c9b0edae05d0c97995c1ff08c4; 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 13d107794304306164481d31ce33f8fdb25a9c04, 302b2dfc013baca3dea7ceda383930d9297d231d, 55b6c738673871c9b0edae05d0c97995c1ff08c4; 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: wireguard: netlink: check for dangling peer via is_dead instead of empty list If all peers are removed via wg_peer_remove_all(), rather than setting peer_list to empty, the peer is added to a temporary list with a head on the stack of wg_peer_remove_all(). If a netlink dump is resumed and the cursored peer is one that has been removed via wg_peer_remove_all(), it will iterate from that peer and then attempt to dump freed peers. Fix this by instead checking peer->is_dead, which was explictly created for this purpose. Also move up the device_update_lock lockdep assertion, since reading is_dead relies on that. It can be reproduced by a small script like: echo "Setting config..." ip link add dev wg0 type wireguard wg setconf wg0 /big-config ( while true; do echo "Showing config..." wg showconf wg0 > /dev/null done ) & sleep 4 wg setconf wg0 <(printf "[Peer]\nPublicKey=$(wg genkey)\n") Resulting in: BUG: KASAN: slab-use-after-free in __lock_acquire+0x182a/0x1b20 Read of size 8 at addr ffff88811956ec70 by task wg/59 CPU: 2 PID: 59 Comm: wg Not tainted 6.8.0-rc2-debug+ #5 Call Trace: <TASK> dump_stack_lvl+0x47/0x70 print_address_description.constprop.0+0x2c/0x380 print_report+0xab/0x250 kasan_report+0xba/0xf0 __lock_acquire+0x182a/0x1b20 lock_acquire+0x191/0x4b0 down_read+0x80/0x440 get_peer+0x140/0xcb0 wg_get_device_dump+0x471/0x1130

HighCVSS 7.8 · v3.1—No exploit Fix available

Memory safety

BDU:2024-09398

Published: May 1, 2024
Updated: Oct 15, 2026
EPSS: 0.2% · 14th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

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.8; agree

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.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi 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 help

Affected 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
debian	debian linux	cpe:2.3:o:debian:debian_linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

debian debian linux10.0
linux linux kernel5.11 and later · before 5.15.154
linux linux kernel5.16 and later · before 6.1.84
linux linux kernel5.6 and later · before 5.10.215
linux linux kernel6.7 and later · before 6.7.12
linux linux kernel6.8 and later · before 6.8.3
linux linux kernel6.2 and later · before 6.6.24

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
- 5.6affected
- e7096c131e5161fa3b8e52a650d7719d2857adfd and later · before f52be46e3e6ecefc2539119784324f0cbc09620aaffected · git
- e7096c131e5161fa3b8e52a650d7719d2857adfd and later · before 710a177f347282eea162aec8712beb1f42d5ad87affected · git
- e7096c131e5161fa3b8e52a650d7719d2857adfd and later · before b7cea3a9af0853fdbb1b16633a458f991dde6aacaffected · git
- e7096c131e5161fa3b8e52a650d7719d2857adfd and later · before 13d107794304306164481d31ce33f8fdb25a9c04affected · git
- e7096c131e5161fa3b8e52a650d7719d2857adfd and later · before 7bedfe4cfa38771840a355970e4437cd52d4046baffected · git
- e7096c131e5161fa3b8e52a650d7719d2857adfd and later · before 302b2dfc013baca3dea7ceda383930d9297d231daffected · git
- e7096c131e5161fa3b8e52a650d7719d2857adfd and later · before 55b6c738673871c9b0edae05d0c97995c1ff08c4affected · git
- before 5.6not affected · semver
- 5.10.215 and later · up to and including 5.10.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:12	linux	before 6.1.85-1	6.1.85-1
Debian:13	linux	before 6.7.12-1	6.7.12-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
90Now
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 KEV
89Now
CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
85Now

Published before and after this one in the same product

← EarlierCVE-2024-26948May 1, 2024 · drm/amd/display: Add a dc_state NULL check in dc_state_release
22Monitor
← EarlierCVE-2024-26950May 1, 2024 · wireguard: netlink: access device through ctx instead of peer
31Monitor
Later →CVE-2024-26953May 1, 2024 · net: esp: fix bad handling of pages from page_pool
22Monitor

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	13d107794304306164481d31ce33f8fdb25a9c04	Vendor (CNA)
Linux Linux	302b2dfc013baca3dea7ceda383930d9297d231d	Vendor (CNA)
Linux Linux	55b6c738673871c9b0edae05d0c97995c1ff08c4	Vendor (CNA)
Linux Linux	710a177f347282eea162aec8712beb1f42d5ad87	Vendor (CNA)
Linux Linux	7bedfe4cfa38771840a355970e4437cd52d4046b	Vendor (CNA)
Linux Linux	b7cea3a9af0853fdbb1b16633a458f991dde6aac	Vendor (CNA)
Linux Linux	f52be46e3e6ecefc2539119784324f0cbc09620a	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)
debian:linux	6.1.85-1 · Debian:12	Package registry (OSV)

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.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

TR-24-0494 · May 16, 2024(Linux Kernel Güncellemesi)

All national notices →

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 Free

CVSS 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 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&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

Fix✗ → ✓Sep 28, 2026, 10:10 PM UTC

For records you follow, these changes also arrive as notifications. →

References

git.kernel.org/stable/c/13d107794304306164481d31ce33f8fdb25a9c04

Show all references (8 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records