Hi ,
I read #15731. It explains Wazuh matches your installed packages with Canonical/NVD data, so sometimes they don’t agree and you still see CVEs even on the latest kernel.
What you can do:
Check the CVE in Canonical (Ubuntu CVE Tracker / USN).
Open one Wazuh event and see which source is reporting it (Canonical or NVD).
If Canonical says it’s fixed and you just want it quiet, ignore it with a local rule (match package/CVE → level 0).
dpkg -s linux-image-6.8.0-90-generic | grep -E "(Package|Version)"
Package: linux-image-6.8.0-90-generic
Version: 6.8.0-90.91
apt install linux-image-generic linux-headers-generic
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
linux-image-generic is already the newest version (6.8.0-90.91).
linux-image-generic set to manually installed.
linux-headers-generic is already the newest version (6.8.0-90.91).
linux-headers-generic set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
apt dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following upgrades have been deferred due to phasing:
python3-distupgrade ubuntu-release-upgrader-core
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
Hi CreativeWolf
sorry for the late reply, and thanks for the details. If you just want to silence those kernel findings, an easy workaround is a local rule on the manager to set the alert level to 0 for that package.
On the Wazuh manager, edit:
/var/ossec/etc/rules/local_rules.xml