dbcve.org
LibinputApplication · Freedesktop

CVE-2022-1215

HIGH · 7.8 CVSS v3.1 Published 2022-06-02
Fix available
A fix is available. Upgrade to 1.18.2 / 1.19.4 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A format string vulnerability was found in libinput

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · low confidence

A format string vulnerability exists in libinput, a library used for handling input device events. This type of flaw occurs when user-supplied input is passed directly to format string functions (e.g., printf, sprintf) without proper sanitization, potentially allowing attackers to read from or write to arbitrary memory locations.

MitigationUpdate libinput to the latest version containing the security patch. If patching is not immediately possible, ensure input data passed to logging or output functions is sanitized and does not contain unsanitized user-controlled format specifiers.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
LibinputApplication
Affected:>= 1.10.0, < 1.18.2>= 1.19.0, < 1.19.4= 1.20.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if libinput is installed
    Run 'pkg-config --modversion libinput' or check for libinput package via your system package manager (e.g., 'dpkg -l libinput' on Debian/Ubuntu, 'rpm -qi libinput' on RHEL/CentOS, or 'brew list libinput' on macOS)
    Affected if libinput is not found on the system, then this CVE does not apply
  2. Identify the installed libinput version
    Run 'libinput --version' if available, or check the library file directly with 'pkg-config --modversion libinput', or examine the shared library with 'ls -la /usr/lib/x86_64-linux-gnu/libinput*' and check package version as shown by your package manager
    Affected if the version displayed cannot be determined or is ambiguous
  3. Compare against affected version ranges
    Parse the version number from step 2 and compare against: 1.10.0 <= version < 1.18.2, OR 1.19.0 <= version < 1.19.4, OR version = 1.20.0
    Affected if the installed version falls into any of these ranges: 1.10.0 through 1.18.1, 1.19.0 through 1.19.3, or exactly 1.20.0
  4. Verify if libinput is actively used
    Check if any display manager, desktop environment, or compositor process links to libinput by running 'ldd <path-to-display-manager-or-compositor>' or 'ps aux | grep -E "(gdm|lightdm|sddm|wayland|Xorg| compositor)" | xargs ldd 2>/dev/null | grep libinput"
    Affected if libinput is loaded and linked to running display/input processes, and the version is in the affected range from step 3

A system is affected if libinput is installed with a version matching 1.10.0 to 1.18.1, 1.19.0 to 1.19.3, or exactly 1.20.0, and the library is actively in use by the display or input handling stack.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.18.2 / 1.19.4 or later
Fixed in 1.18.21.19.4
Interim mitigation

Update libinput to the latest version containing the security patch. If patching is not immediately possible, ensure input data passed to logging or output functions is sanitized and does not contain unsanitized user-controlled format specifiers.

Recommended fix High confidence

libinput 1.20.1 or later (or 1.19.4 / 1.18.2 depending on your release branch)

  1. 1. Identify the current installed version of libinput using: pkg-config --modversion libinput or libinput --version
  2. 2. Based on the current version, upgrade to the appropriate fixed release:
  3. - If using 1.10.0-1.18.x: upgrade to libinput 1.18.2 or later
  4. - If using 1.19.x: upgrade to libinput 1.19.4 or later
  5. - If using 1.20.0: upgrade to libinput 1.20.1 or later
  6. 3. Obtain the fixed version from your distribution's package manager or compile from source available at https://gitlab.freedesktop.org/libinput/libinput/-/releases
  7. 4. Restart any services or log out/in of the desktop session to ensure the new libinput version is loaded

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Libinput Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-1215 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-1215 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data