CVE-2023-54142

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-12-24. The CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory
Trending — 3 sources updated this week

Also known asEUVD-2023-60303 (ENISA EUVD) · GHSA-frp2-qrfx-2m63 (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

gtp: Fix use-after-free in __gtp_encap_destroy().

syzkaller reported use-after-free in __gtp_encap_destroy(). [0]

It shows the same process freed sk and touched it illegally.

Commit e198987e7dd7 ("gtp: fix suspicious RCU usage") added lock_sock() and release_sock() in __gtp_encap_destroy() to protect sk->sk_user_data, but release_sock() is called after sock_put() releases the last refcnt.

[0]: BUG: KASAN: slab-use-after-free in instrument_atomic_read_write include/linux/instrumented.h:96 [inline] BUG: KASAN: slab-use-after-free in atomic_try_cmpxchg_acquire include/linux/atomic/atomic-instrumented.h:541 [inline] BUG: KASAN: slab-use-after-free in queued_spin_lock include/asm-generic/qspinlock.h:111 [inline] BUG: KASAN: slab-use-after-free in do_raw_spin_lock include/linux/spinlock.h:186 [inline] BUG: KASAN: slab-use-after-free in __raw_spin_lock_bh include/linux/spinlock_api_smp.h:127 [inline] BUG: KASAN: slab-use-after-free in _raw_spin_lock_bh+0x75/0xe0 kernel/locking/spinlock.c:178 Write of size 4 at addr ffff88800dbef398 by task syz-executor.2/2401

CPU: 1 PID: 2401 Comm: syz-executor.2 Not tainted 6.4.0-rc5-01219-gfa0e21fa4443 #2 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x72/0xa0 lib/dump_stack.c:106 print_address_description mm/kasan/report.c:351 [inline] print_report+0xcc/0x620 mm/kasan/report.c:462 kasan_report+0xb2/0xe0 mm/kasan/report.c:572 check_region_inline mm/kasan/generic.c:181 [inline] kasan_check_range+0x39/0x1c0 mm/kasan/generic.c:187 instrument_atomic_read_write include/linux/instrumented.h:96 [inline] atomic_try_cmpxchg_acquire include/linux/atomic/atomic-instrumented.h:541 [inline] queued_spin_lock include/asm-generic/qspinlock.h:111 [inline] do_raw_spin_lock include/linux/spinlock.h:186 [inline] __raw_spin_lock_bh include/linux/spinlock_api_smp.h:127 [inline] _raw_spin_lock_bh+0x75/0xe0 kernel/locking/spinlock.c:178 spin_lock_bh include/linux/spinlock.h:355 [inline] release_sock+0x1f/0x1a0 net/core/sock.c:3526 gtp_encap_disable_sock drivers/net/gtp.c:651 [inline] gtp_encap_disable+0xb9/0x220 drivers/net/gtp.c:664 gtp_dev_uninit+0x19/0x50 drivers/net/gtp.c:728 unregister_netdevice_many_notify+0x97e/0x1520 net/core/dev.c:10841 rtnl_delete_link net/core/rtnetlink.c:3216 [inline] rtnl_dellink+0x3c0/0xb30 net/core/rtnetlink.c:3268 rtnetlink_rcv_msg+0x450/0xb10 net/core/rtnetlink.c:6423 netlink_rcv_skb+0x15d/0x450 net/netlink/af_netlink.c:2548 netlink_unicast_kernel net/netlink/af_netlink.c:1339 [inline] netlink_unicast+0x700/0x930 net/netlink/af_netlink.c:1365 netlink_sendmsg+0x91c/0xe30 net/netlink/af_netlink.c:1913 sock_sendmsg_nosec net/socket.c:724 [inline] sock_sendmsg+0x1b7/0x200 net/socket.c:747 ____sys_sendmsg+0x75a/0x990 net/socket.c:2493 ___sys_sendmsg+0x11d/0x1c0 net/socket.c:2547 __sys_sendmsg+0xfe/0x1d0 net/socket.c:2576 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3f/0x90 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x72/0xdc RIP: 0033:0x7f1168b1fe5d Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 73 9f 1b 00 f7 d8 64 89 01 48 RSP: 002b:00007f1167edccc8 EFLAGS: 00000246 ORIG_RAX: 000000000000002e RAX: ffffffffffffffda RBX: 00000000004bbf80 RCX: 00007f1168b1fe5d RDX: 0000000000000000 RSI: 00000000200002c0 RDI: 0000000000000003 RBP: 00000000004bbf80 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 000000000000000b R14: 00007f1168b80530 R15: 0000000000000000

Allocated by task 1483: kasan_save_stack+0x22/0x50 mm/kasan/common.c:45 kasan_set_track+0x25/0x30 mm/kasan/common.c:52 __kasan_slab_alloc+0x ---truncated---

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
4th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-02). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

December 24, 2025

Last Modified

August 5, 2026

Advisory Details (9)

Auto-updated Aug 4, 2026
Patch available.
Web page

gtp: Fix use-after-free in __gtp_encap_destroy(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ebd6d2077a083329110695a996c00e8ca94bc640
Web page

gtp: Fix use-after-free in __gtp_encap_destroy(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e5aa6d829831a55a693dbaeb58f8d22ba7f2b3e6
Web page

gtp: Fix use-after-free in __gtp_encap_destroy(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/dae6095bdb24f537b4798ffd9201515b97bac94e
Web page

gtp: Fix use-after-free in __gtp_encap_destroy(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d38039697184aacff1cf576e14ef583112fdefef
Web page

gtp: Fix use-after-free in __gtp_encap_destroy(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ce3aee7114c575fab32a5e9e939d4bbb3dcca79f
Web page

gtp: Fix use-after-free in __gtp_encap_destroy(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bccc7ace12e69dee4684a3bb4b69737972e570d6
Web page

gtp: Fix use-after-free in __gtp_encap_destroy(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9c9662e2512b5e4ee7b03108802c5222e0fa77a4
Web page

gtp: Fix use-after-free in __gtp_encap_destroy(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/58fa341327fdb4bdf92597fd8796a9abc8d20ea3
Web page

gtp: Fix use-after-free in __gtp_encap_destroy(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/17d6b6354f0025b7c10a56da783fd0cbb3819c5d

Vendor Advisories for CVE-2023-54142(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 4.14.322 (fixes >=0)—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (33 versions)
  • every version up to 5.10.191-1: fixed in 5.10.191-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.27-1 ... 6.1.38-4~bpo11+1 (8 versions)
  • every version up to 6.1.52-1: fixed in 6.1.52-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.4.4-1: fixed in 6.4.4-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.4.4-1: fixed in 6.4.4-1
—

Data Freshness Timeline

(refreshed 9× in last 7d / 41× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 94 of 236 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 6 repeat rows among the latest 100 are merged into the row they repeat. The 142 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-06 16:31 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  2. 2026-11-05 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  3. 2026-11-04 16:31 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  4. 2026-11-03 16:41 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  5. 2026-11-03 06:52 UTCEG score recompute
  6. 2026-11-03 06:52 UTCGHSA enrichmentGHSA-frp2-qrfx-2m63 · GitHub severity HIGH · GitHub CVSS 7.8
  7. 2026-11-02 16:40 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  8. 2026-11-01 16:31 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  9. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  10. 2026-10-30 16:31 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  11. 2026-10-29 16:30 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  12. 2026-10-28 16:29 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  13. 2026-10-27 20:00 UTCEG score recompute
  14. 2026-10-27 20:00 UTCGHSA enrichmentGHSA-frp2-qrfx-2m63 · GitHub severity HIGH · GitHub CVSS 7.8
  15. 2026-10-27 16:29 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  16. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  17. 2026-10-25 17:27 UTCEG score recompute
  18. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  19. 2026-10-24 16:29 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  20. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  21. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  22. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  23. 2026-10-20 21:12 UTCEG score recompute
  24. 2026-10-20 21:12 UTCGHSA enrichmentGHSA-frp2-qrfx-2m63 · GitHub severity HIGH · GitHub CVSS 7.8
  25. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.2% · 4th percentile
Show 69 more
  1. 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  2. 2026-10-18 16:29 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  3. 2026-10-18 07:40 UTCEG score recompute
  4. 2026-10-17 16:30 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  5. 2026-10-16 16:36 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  6. 2026-10-15 16:29 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  7. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  8. 2026-10-13 16:30 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  9. 2026-10-12 18:11 UTCEG score recompute
  10. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  11. 2026-10-11 21:37 UTCEG score recompute
  12. 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  13. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  14. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  15. 2026-10-08 17:06 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  16. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  17. 2026-10-06 15:15 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  18. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  19. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  20. 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  21. 2026-10-03 12:39 UTCOSV refresh
  22. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  23. 2026-09-30 16:38 UTCEG score recompute
  24. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  25. 2026-09-29 15:17 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  26. 2026-09-28 13:49 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  27. 2026-09-26 00:22 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  28. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  29. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  30. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  31. 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  32. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  33. 2026-09-16 05:11 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  34. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  35. 2026-09-14 05:49 UTCOSV refresh
  36. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  37. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  38. 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  39. 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  40. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  41. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  42. 2026-09-05 15:26 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  43. 2026-09-04 05:04 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  44. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  45. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  46. 2026-09-01 04:36 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  47. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  48. 2026-08-30 01:20 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  49. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  50. 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  51. 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  52. 2026-08-26 06:43 UTCOSV refresh
  53. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  54. 2026-08-23 00:17 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  55. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  56. 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  57. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  58. 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  59. 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  60. 2026-08-16 02:12 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  61. 2026-08-15 01:28 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  62. 2026-08-13 21:58 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  63. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  64. 2026-08-11 13:40 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  65. 2026-08-10 23:58 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  66. 2026-08-09 22:46 UTCEG score recompute
  67. 2026-08-09 22:46 UTCGHSA enrichmentGHSA-frp2-qrfx-2m63 · GitHub severity HIGH · GitHub CVSS 7.8
  68. 2026-08-09 13:44 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  69. 2026-08-08 16:35 UTCEPSS rescoreEPSS 0.1% · 3rd percentile

Frequently asked(5)

What is CVE-2023-54142?
CVE-2023-54142 is a high-severity vulnerability; its CVE record was published on December 24, 2025. In the Linux kernel, the following vulnerability has been resolved: gtp: Fix use-after-free in __gtp_encap_destroy(). syzkaller reported use-after-free in __gtp_encap_destroy(). [0] It shows the same process freed sk and touched it illegally. Commit e198987e7dd7 ("gtp: fix suspicious RCU usage")…
When was the CVE record for CVE-2023-54142 published?
The CVE record for CVE-2023-54142 was published on December 24, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 5, 2026; the record at its source may have been updated since.
Is CVE-2023-54142 actively exploited?
CVE-2023-54142 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-54142?
CVE-2023-54142 has a CVSS base score of 7.8 (the CNA's own assessment, by linux; NVD's own analysis pending).
How do I remediate CVE-2023-54142?
A fix for CVE-2023-54142 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-54142 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-54142

Explore →

Is Your Infrastructure Affected by CVE-2023-54142?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs