Look up another CVE · open CVE-2022-0185 in the interactive tracker
CVE-2022-0185
A heap-based buffer overflow flaw was found in the way the legacy_parse_param function in the Filesystem Context functionality of the Linux kernel verified the…
The kernel CNA record carries no publication date. Subsystem unknown. Debian urgency: not yet assigned.
What to do, per Debian release
Debian's own status for CVE-2022-0185 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | fixed | 5.15.15-1 | Update the kernel and reboot. Fixed in 5.15.15-1. A running kernel keeps the old code until the machine restarts. |
| Debian 13trixie | fixed | 5.15.15-1 | Update the kernel and reboot. Fixed in 5.15.15-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 5.15.15-1 | Update the kernel and reboot. Fixed in 5.15.15-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 5.15.15-1 | Update the kernel and reboot. Fixed in 5.15.15-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
A heap-based buffer overflow flaw was found in the way the legacy_parse_param function in the Filesystem Context functionality of the Linux kernel verified the supplied parameters length. An unprivileged (in case of unprivileged user namespaces enabled, otherwise needs namespaced CAP_SYS_ADMIN privilege) local user able to open a filesystem that does not support the Filesystem Context API (and thus fallbacks to legacy handling) could use this flaw to escalate their privileges on the system.
Where it lives
Show whether Debian builds this, per release
Not established. This site could not find the build rule for the affected file in the kernel trees Debian ships, so it has no answer about whether Debian compiles this code. Read that as unknown, never as absent.
- bookworm, trixie, forky, sid?
- ?
- not established - no Makefile entry for the affected file
Where a release above reads "not established", no build rule for the affected file was found in that release's kernel tree. That is a gap in this lookup, not a finding that the code is absent.
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.
Known to be exploited in the wild
- Added to KEV
- 2024-08-21
- Federal due date
- 2024-09-11
- Ransomware use
- unknown
- Required action
- Apply updates per vendor instructions or discontinue use of the product if updates are unavailable.
Signals
- Published
- unknown
- CVSS
- no vector published, unrated
- Attack vector
- not published
- EPSS
- 25.15%, higher than 97.9% of all CVEssource
- CISA KEV
- listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- Subsystem
- unknown
Debian advisories
| Advisory | Date | Shipped to | Debian |
|---|---|---|---|
| DSA-5050-1 | 2022-01-20 | bullseye 5.10.92-1 | tracker |
Why the CNA scored it this way
The kernel CNA published no CVSS vector and no reasoning for CVE-2022-0185, which is why it is shown as unrated rather than given an invented score. 6,405 of the 20,413 CVEs here carry reasoning; this is not one of them.