What the advisory says

A version number alone can give the wrong answer when a Linux distribution backports a security fix to a maintained release. The upstream version may look older than the fixed release, while the vendor package includes the relevant patch. The reverse can also happen with software bundled by another supplier.

The useful evidence is the exact package name, distribution release, package revision and vendor security notice. For a container or appliance, also identify the image or product build. Do not infer that a patch is present because a changelog mentions a similar issue; confirm the CVE and build mapping.

Checks for your systems

Collect the package query output and repository source from the affected host. Search the operating system vendor’s security tracker for the CVE, then compare its fixed package revision with the installed one. Ask the supplier when the product manages its own runtime or hides package details.

Keep the advisory reference and verification result with the change record. Recheck after rebuilds and image updates, because a fixed host package does not update a separate container or embedded runtime. If vendor status is unclear, request confirmation from the supplier before closing the exposure review.