CVE-2022-20566
In l2cap_chan_put of l2cap_core, there is a possible use after free due to improper locking.
Published Dec 16, 2022 · updated Oct 14, 2026 · google android
In l2cap_chan_put of l2cap_core, there is a possible use after free due to improper locking. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-165329981References: Upstream kernel
Timeline
Detection, updates, and resolution for this record.
Dec 16, 2022 · NIST NVD
Detected
In l2cap_chan_put of l2cap_core, there is a possible use after free due to improper locking. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-165329981References: Upstream kernel
Oct 14, 2026 · NIST NVD
Updated
In l2cap_chan_put of l2cap_core, there is a possible use after free due to improper locking. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-165329981References: Upstream kernel
Affected
- cpe google/androidversion unspecified
Sources
- CVE.orgCVE-2022-20566
Official CVE identifier
cve.org - FIRST EPSSCVE-2022-20566
30-day exploitation probability 0.2%
first.org - NIST NVDCVE-2022-20566
In l2cap_chan_put of l2cap_core, there is a possible use after free due to improper locking. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAn
nvd.nist.gov