CVE-2022-20567 json
In pppol2tp_create of l2tp_ppp.c, there is a possible use after free due to a race condition.
published 3y ago modified 4mo ago also EUVD-2022-25827
- cvss
- 7.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 3%
- public exploits
- 0
- none known
Summary
In pppol2tp_create of l2tp_ppp.c, there is a possible use after free due to a race condition. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-186777253References: Upstream kernel
Patch / fix
- linux Debian 14, Debian 13, Debian 12 4.15.11-1
debian advisories DEBIAN-CVE-2022-20567
- linux Ubuntu Pro 16.04 LTS 4.4.0-252.286
- linux-aws Ubuntu Pro 14.04 LTS 4.4.0-1129.135
- linux-aws Ubuntu Pro 16.04 LTS 4.4.0-1167.182
- linux-kvm Ubuntu Pro 16.04 LTS 4.4.0-1130.140
- linux-fips Ubuntu Pro FIPS-updates 16.04 LTS 4.4.0-1099.106
- linux-lts-xenial Ubuntu Pro 14.04 LTS 4.4.0-252.286~14.04.1
ubuntu advisories UBUNTU-CVE-2022-20567
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-default SLES for SAP 15 SP1, SLES 15 SP1-LTSS, SLE Live Patching 15 SP1 +3 more 4.12.14-150100.197.142.1
- kernel-vanilla openSUSE Leap 15.4 4.12.14-150100.197.142.1
- kernel-kvmsmall openSUSE Leap 15.4 4.12.14-150100.197.142.1
- kernel-zfcpdump SLES 15 SP1-LTSS, openSUSE Leap 15.4 4.12.14-150100.197.142.1
- drbd SLE High Availability Extension 12 SP4 9.0.14+git.62f906cf-4.26.2
- kernel-syms SLES 12 SP4-LTSS, SLES 12 SP4-ESPOS, OpenStack Cloud Crowbar 9 +1 more 4.12.14-95.125.1
- kernel-source SLES 12 SP4-LTSS, SLES 12 SP4-ESPOS, OpenStack Cloud Crowbar 9 +1 more 4.12.14-95.125.1
- kernel-default SLES 12 SP4-LTSS, SLES 12 SP4-ESPOS, SLE Live Patching 12 SP4 +3 more 4.12.14-95.125.1
suse advisories SUSE-SU-2023:1848-1SUSE-SU-2023:2232-1SUSE-SU-2023:1894-1SUSE-SU-2023:1803-1SUSE-SU-2023:1801-1
Is CVE-2022-20567 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2022-20567 updated cvss 6.4
kernel: race in pppol2tp_release
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Virtualization 4 redhat-virtualization-host-image-updatenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
0.14% chance of exploitation in the next 30 days, higher than 3% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 7.4 | CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 6.4 | CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 7.4 | CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- n/a Android
Classification
- Weakness
-
- CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization
References
-
source.android.com
/security/bulletin/pixel/2022-12-01
patch, vendor-advisory
Sources
- CVE List CVE-2022-20567
- NVD CVE-2022-20567
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.