SECUFOCUSNOW
Home›CVE index›CVE-2023-54142
Review reviewHigh

CVE-2023-54142

Linux

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-...

CVSS
7.8
EPSS
0.14%
3.49% percentile
CISA KEV
Not listed
Published
2025.12.24
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.14%
Technical severityCVSS 7.8

Vulnerability overview

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-...

Affected product and versions

Product
Linux
Affected versions
>= 01f3c64e405ab3d25887d080a103ad76f30661d2 < d38039697184aacff1cf576e14ef583112fdefef, >= e117a04133c673cc54292e12086a8177cd9bd4a4 < e5aa6d829831a55a693dbaeb58f8d22ba7f2b3e6, >= e198987e7dd7d3645a53875151cd6f8fc425b706 < 9c9662e2512b5e4ee7b03108802c5222e0fa77a4, >= e198987e7dd7d3645a53875151cd6f8fc425b706 < bccc7ace12e69dee4684a3bb4b69737972e570d6, >= e198987e7dd7d3645a53875151cd6f8fc425b706 < ebd6d2077a083329110695a996c00e8ca94bc640, >= e198987e7dd7d3645a53875151cd6f8fc425b706 < 17d6b6354f0025b7c10a56da783fd0cbb3819c5d, >= e198987e7dd7d3645a53875151cd6f8fc425b706 < dae6095bdb24f537b4798ffd9201515b97bac94e, >= e198987e7dd7d3645a53875151cd6f8fc425b706 < 58fa341327fdb4bdf92597fd8796a9abc8d20ea3, >= e198987e7dd7d3645a53875151cd6f8fc425b706 < ce3aee7114c575fab32a5e9e939d4bbb3dcca79f, >= bf75202df8e473d4ee914894542f213158066d8b, >= 76357f65f18f180f44ccbbbf713461881d0ab219, >= 4.14.135 < 4.14.322, >= 4.19.61 < 4.19.291, >= 5.1.20 < 5.2, >= 5.2.3 < 5.3, >= 5.3
Fixed versions
No verified fixed-version field is available yet

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
Not available