NVD / CVE Program· CNA Linux

CVE-2024-26754: gtp: fix use-after-free and null-ptr-deref in gtp_genl_dump_pdp()

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.25% (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 136cfaca22567a03bbb3bf53a43d8cb5748b80ec, 2e534fd15e5c2ca15821c897352cf0e8a3e30dca, 3963f16cc7643b461271989b712329520374ad2a.
Mentioned 2 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 136cfaca22567a03bbb3bf53a43d8cb5748b80ec, 2e534fd15e5c2ca15821c897352cf0e8a3e30dca, 3963f16cc7643b461271989b712329520374ad2a 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: gtp: fix use-after-free and null-ptr-deref in gtp_genl_dump_pdp() The gtp_net_ops pernet operations structure for the subsystem must be registered before registering the generic netlink family. Syzkaller hit 'general protection fault in gtp_genl_dump_pdp' bug: general protection fault, probably for non-canonical address 0xdffffc0000000002: 0000 [#1] PREEMPT SMP KASAN NOPTI KASAN: null-ptr-deref in range [0x0000000000000010-0x0000000000000017] CPU: 1 PID: 5826 Comm: gtp Not tainted 6.8.0-rc3-std-def-alt1 #1 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.0-alt1 04/01/2014 RIP: 0010:gtp_genl_dump_pdp+0x1be/0x800 [gtp] Code: c6 89 c6 e8 64 e9 86 df 58 45 85 f6 0f 85 4e 04 00 00 e8 c5 ee 86 df 48 8b 54 24 18 48 b8 00 00 00 00 00 fc ff df 48 c1 ea 03 <80> 3c 02 00 0f 85 de 05 00 00 48 8b 44 24 18 4c 8b 30 4c 39 f0 74 RSP: 0018:ffff888014107220 EFLAGS: 00010202 RAX: dffffc0000000000 RBX: 0000000000000000 RCX: 0000000000000000 RDX: 0000000000000002 RSI: 0000000000000000 RDI: 0000000000000000 RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000 R13: ffff88800fcda588 R14: 0000000000000001 R15: 0000000000000000 FS: 00007f1be4eb05c0(0000) GS:ffff88806ce80000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f1be4e766cf CR3: 000000000c33e000 CR4: 0000000000750ef0 PKRU: 55555554 Call Trace: <TASK> ? show_regs+0x90/0xa0 ? die_addr+0x50/0xd0 ? exc_general_protection+0x148/0x220 ? asm_exc_general_protection+0x22/0x30 ? gtp_genl_dump_pdp+0x1be/0x800 [gtp] ? __alloc_skb+0x1dd/0x350 ? __pfx___alloc_skb+0x10/0x10 genl_dumpit+0x11d/0x230 netlink_dump+0x5b9/0xce0 ? lockdep_hardirqs_on_prepare+0x253/0x430 ? __pfx_netlink_dump+0x10/0x10 ? kasan_save_track+0x10/0x40 ? __kasan_kmalloc+0x9b/0xa0 ? genl_start+0x675/0x970 __netlink_dump_start+0x6fc/0x9f0 genl_family_rcv_msg_dumpit+0x1bb/0x2d0 ? __pfx_genl_family_rcv_msg_dumpit+0x10/0x10 ? genl_op_from_small+0x2a/0x440 ? cap_capable+0x1d0/0x240 ? __pfx_genl_start+0x10/0x10 ? __pfx_genl_dumpit+0x10/0x10 ? __pfx_genl_done+0x10/0x10 ? security_capable+0x9d/0xe0

HighCVSS 7.8 · v3.1—No exploit Fix available

Memory safety

BDU:2024-03681

Published: Apr 3, 2024
Updated: Jun 17, 2026
EPSS: 0.2% · 17th 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.

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 kernel4.20 and later · before 5.4.270
linux linux kernel5.5 and later · before 5.10.211
linux linux kernel5.11 and later · before 5.15.150
linux linux kernel4.7 and later · before 4.19.308
linux linux kernel6.2 and later · before 6.6.19
linux linux kernel6.7 and later · before 6.7.7
linux linux kernel5.16 and later · before 6.1.80
linux linux kernel6.8

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
- 4.7affected
- 459aa660eb1d8ce67080da1983bb81d716aa5a69 and later · before f0ecdfa679189d26aedfe24212d4e69e42c2c861affected · git
- 459aa660eb1d8ce67080da1983bb81d716aa5a69 and later · before f8cbd1791900b5d96466eede8e9439a5b9ca4de7affected · git
- 459aa660eb1d8ce67080da1983bb81d716aa5a69 and later · before 2e534fd15e5c2ca15821c897352cf0e8a3e30dcaaffected · git
- 459aa660eb1d8ce67080da1983bb81d716aa5a69 and later · before a576308800be28f2eaa099e7caad093b97d66e77affected · git
- 459aa660eb1d8ce67080da1983bb81d716aa5a69 and later · before 3963f16cc7643b461271989b712329520374ad2aaffected · git
- 459aa660eb1d8ce67080da1983bb81d716aa5a69 and later · before ba6b8b02a3314e62571a540efa96560888c5f03eaffected · git
- 459aa660eb1d8ce67080da1983bb81d716aa5a69 and later · before 5013bd54d283eda5262c9ae3bcc966d01daf8576affected · git
- 459aa660eb1d8ce67080da1983bb81d716aa5a69 and later · before 136cfaca22567a03bbb3bf53a43d8cb5748b80ecaffected · git
- before 4.7not 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.82-1	6.1.82-1
Debian:13	linux	before 6.7.7-1	6.7.7-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-26752Apr 3, 2024 · l2tp: pass correct message length to ip6_append_data
22Monitor
← EarlierCVE-2024-26753Apr 3, 2024 · crypto: virtio/akcipher - Fix stack overflow on memcpy
31Monitor
Later →CVE-2024-26755Apr 3, 2024 · md: Don't suspend the array for interrupted reshape
21Monitor

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	136cfaca22567a03bbb3bf53a43d8cb5748b80ec	Vendor (CNA)
Linux Linux	2e534fd15e5c2ca15821c897352cf0e8a3e30dca	Vendor (CNA)
Linux Linux	3963f16cc7643b461271989b712329520374ad2a	Vendor (CNA)
Linux Linux	5013bd54d283eda5262c9ae3bcc966d01daf8576	Vendor (CNA)
Linux Linux	a576308800be28f2eaa099e7caad093b97d66e77	Vendor (CNA)
Linux Linux	ba6b8b02a3314e62571a540efa96560888c5f03e	Vendor (CNA)
Linux Linux	f0ecdfa679189d26aedfe24212d4e69e42c2c861	Vendor (CNA)
Linux Linux	f8cbd1791900b5d96466eede8e9439a5b9ca4de7	Vendor (CNA)
debian:linux	6.1.82-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)
TR-24-0265 · Apr 4, 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:11 PM UTC

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

References

git.kernel.org/stable/c/136cfaca22567a03bbb3bf53a43d8cb5748b80ec

Show all references (9 more)

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

All records