USB ID: 06cb:00b7
Reported in: HP ProBook 450 G6, HP ZBook 17 G6, HP EliteBook 840 G6
Source: devices/06cb:00b7/README.md

Validity/Synaptics VCSFW 0xd51 (USB 06cb:00b7)

Status: WIP (unmerged upstream MR). MR !626 is still untested on hardware, but the python-validity route below works on an HP EliteBook 840 G6 (#32).

Device ID(s): 06cb:00b7

A Synaptics/Validity VCSFW sensor: TLS-paired, match-on-chip, with enroll, matching and template storage all happening on the sensor. libfprint has no driver for these today, so they do not work under current fprintd at all.

Hardware

HP ProBook 450 G6, HP ZBook 17 G6, and other HP G6-series models.

Upstream merge request

libfprint MR !626: https://gitlab.freedesktop.org/libfprint/libfprint/-/merge_requests/626
Author: Gary T. Giesen (@ggiesen)

This continues @lewohart's !579, which has been inactive since April 2026; !579's driver is preserved inside it as a single commit with authorship intact. !626 is the branch to build.

What it does

Implements the full FpDevice surface (open/close, enroll, verify, identify, list, delete, clear-storage) and handles the on-chip TLS session, host pairing, calibration and the flash template database in-driver. Each device loads a per-device data package at runtime; see the MR description for details.

The MR author reports daily-driver use, including PAM screen unlock.

Because this ID is registered from python-validity's device data rather than tested, a report either way is especially useful here.

How to use it

The code lives in the merge request, not in this repo:

git clone https://gitlab.freedesktop.org/libfprint/libfprint.git
cd libfprint
git fetch origin merge-requests/626/head:mr-626
git checkout mr-626

Then build and install per docs/BUILD.md.

Hardware report: python-validity route

The first hardware result for this ID came from a different route than MR !626: python-validity PR #256 (head 128a9eb) with open-fprintd replacing fprintd, built as .deb packages (#32).

On an HP EliteBook 840 G6 (sensor 57K0 FM-3439-001, type 0xd51, factory-provisioned) under Ubuntu 26.04, the reporter verified enroll, verify, wrong-finger rejection (3 of 3 refused), sudo through Ubuntu's own pam_fprintd.so, suspend/resume without restarting the service, GDM lock-screen and login fingerprint, and reboot persistence. The one caveat is GNOME's "login keyring not unlocked" dialog after a fingerprint login, which is expected for any fingerprint login. Full details are in the PR comment.

A report from MR !626 itself is still wanted.

138a:0097 - the wider VCSFW family entry, covering 138a:0090, 138a:0097, 138a:009d and 06cb:009a.
06cb:009a - python-validity, the established userspace route for part of this family.

Pairing caveat

These sensors store host pairing data on-chip, so pairing with Linux can invalidate a Windows Hello pairing. Dual-booters should expect to re-enroll on one side.

Tested on

Not tested on this exact ID; the ID is registered from python-validity data.
More reports welcome, especially distro + libfprint version.

License

Part of libfprint (LGPL-2.1).