RaspberryPiOsLite 2026-06-18Firmware60,123 components
Recommended remediation deadlines
We recommend preparing a remediation plan or risk justification.
A finding is a match between a component's name and version and a vulnerability database; whether this product uses the vulnerable code is not checked, so some findings may not apply. A source scan also leaves out test, example and sample folders by default.
| Severity | CVE | Package | Installed | Fixed | Deadline |
|---|---|---|---|---|---|
| Critical | CVE-2026-111497 | libbrotli1 | 1.1.0-2+b7 | 1.1.0-2+deb13u1 | within 7 days |
| Critical | CVE-2026-58016 | libglib2.0-0t64 | 2.84.4-3~deb13u3 | 2.84.4-3~deb13u4 | within 7 days |
| Critical | CVE-2026-58016 | libglib2.0-data | 2.84.4-3~deb13u3 | 2.84.4-3~deb13u4 | within 7 days |
| Critical | CVE-2026-13221 | libperl5.40 | 5.40.1-6 | 5.40.1-6+deb13u1 | within 7 days |
| Critical | CVE-2026-42496 | libperl5.40 | 5.40.1-6 | 5.40.1-6+deb13u1 | within 7 days |
| Critical | CVE-2026-8376 | libperl5.40 | 5.40.1-6 | 5.40.1-6+deb13u1 | within 7 days |
| Critical | CVE-2026-6653 | libxml2 | 2.12.7+dfsg+really2.9.14-2.1+deb13u2 | No fix yet | within 7 days |
| Critical | CVE-2026-60002 | openssh-client | 1:10.0p1-7+deb13u4 | No fix yet | within 7 days |
| Critical | CVE-2026-60002 | openssh-server | 1:10.0p1-7+deb13u4 | No fix yet | within 7 days |
| Critical | CVE-2026-60002 | openssh-sftp-server | 1:10.0p1-7+deb13u4 | No fix yet | within 7 days |
| Critical | CVE-2026-13221 | perl | 5.40.1-6 | 5.40.1-6+deb13u1 | within 7 days |
| Critical | CVE-2026-42496 | perl | 5.40.1-6 | 5.40.1-6+deb13u1 | within 7 days |
| Critical | CVE-2026-8376 | perl | 5.40.1-6 | 5.40.1-6+deb13u1 | within 7 days |
| Critical | CVE-2026-13221 | perl-base | 5.40.1-6 | 5.40.1-6+deb13u1 | within 7 days |
| Critical | CVE-2026-42496 | perl-base | 5.40.1-6 | 5.40.1-6+deb13u1 | within 7 days |
| Critical | CVE-2026-8376 | perl-base | 5.40.1-6 | 5.40.1-6+deb13u1 | within 7 days |
| Critical | CVE-2026-13221 | perl-modules-5.40 | 5.40.1-6 | 5.40.1-6+deb13u1 | within 7 days |
| Critical | CVE-2026-42496 | perl-modules-5.40 | 5.40.1-6 | 5.40.1-6+deb13u1 | within 7 days |
| Critical | CVE-2026-8376 | perl-modules-5.40 | 5.40.1-6 | 5.40.1-6+deb13u1 | within 7 days |
| Critical | CVE-2026-102266 | python3-jwt | 2.10.1-2+deb13u1 | No fix yet | within 7 days |
| Critical | CVE-2026-102267 | python3-jwt | 2.10.1-2+deb13u1 | No fix yet | within 7 days |
| Critical | CVE-2026-102268 | python3-jwt | 2.10.1-2+deb13u1 | No fix yet | within 7 days |
| Critical | CVE-2026-60002 | ssh | 1:10.0p1-7+deb13u4 | No fix yet | within 7 days |
| Critical | GHSA-6q48-6c7w-9gw2 | certifi | 2025.1.31 | 2026.10.18 | within 7 days |
| Critical | CVE-2026-102268 | pyjwt | 2.10.1 | 2.14.0 | within 7 days |
| Critical | CVE-2026-100075 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-31501 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-31589 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-43414 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-46316 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-52924 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-53131 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-53151 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-53175 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-53176 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-53186 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-53215 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-53216 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-53221 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-53224 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-53225 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-53228 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-53246 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-53247 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-53260 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-53355 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-53363 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-53384 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-53398 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-53399 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-63795 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-63800 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-63808 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-63825 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-63830 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-63886 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-63887 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-63888 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-63912 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-63922 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-63924 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-63938 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-63939 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-63940 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-63978 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-63979 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-63984 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-63992 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-63993 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-63994 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-64000 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-64007 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-64067 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-64068 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-64160 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-64268 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-64269 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-64303 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-64319 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-64320 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-64355 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-64383 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-64384 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-64385 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-64386 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-64387 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-64391 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-64392 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-64393 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-64397 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-64399 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-64439 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-64450 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-64459 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-64523 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-64530 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-64534 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-64535 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-64541 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-64551 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-64564 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-64566 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| Critical | CVE-2026-98432 | linux_kernel | 6.18.34 | No fix yet | within 7 days |
| High | CVE-2026-14266 | 7zip | 25.01+dfsg-1~deb13u2 | No fix yet | within 30 days |
| High | CVE-2026-48095 | 7zip | 25.01+dfsg-1~deb13u2 | No fix yet | within 30 days |
| High | CVE-2026-109518 | apt | 3.0.3 | 3.0.4 | within 30 days |
| High | CVE-2026-109518 | apt-utils | 3.0.3 | 3.0.4 | within 30 days |
| High | CVE-2023-44431 | bluez | 5.82-1.1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-19774 | bluez | 5.82-1.1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-80186 | bluez | 5.82-1.1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-85218 | bluez | 5.82-1.1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-53612 | bsdextrautils | 2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-53613 | bsdextrautils | 2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-53614 | bsdextrautils | 2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-53615 | bsdextrautils | 2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-76642 | bsdextrautils | 2.41-5 | No fix yet | within 30 days |
| High | CVE-2026-78408 | bsdextrautils | 2.41-5 | No fix yet | within 30 days |
| High | CVE-2026-78409 | bsdextrautils | 2.41-5 | No fix yet | within 30 days |
| High | CVE-2026-78410 | bsdextrautils | 2.41-5 | No fix yet | within 30 days |
| High | CVE-2026-53612 | bsdutils | 1:2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-53613 | bsdutils | 1:2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-53614 | bsdutils | 1:2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-53615 | bsdutils | 1:2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-76642 | bsdutils | 1:2.41-5 | No fix yet | within 30 days |
| High | CVE-2026-78408 | bsdutils | 1:2.41-5 | No fix yet | within 30 days |
| High | CVE-2026-78409 | bsdutils | 1:2.41-5 | No fix yet | within 30 days |
| High | CVE-2026-78410 | bsdutils | 1:2.41-5 | No fix yet | within 30 days |
| High | CVE-2023-39810 | busybox | 1:1.37.0-6+b8 | No fix yet | within 30 days |
| High | CVE-2026-124737 | busybox | 1:1.37.0-6+b8 | No fix yet | within 30 days |
| High | CVE-2026-124739 | busybox | 1:1.37.0-6+b8 | No fix yet | within 30 days |
| High | CVE-2026-124741 | busybox | 1:1.37.0-6+b8 | No fix yet | within 30 days |
| High | CVE-2026-124747 | busybox | 1:1.37.0-6+b8 | No fix yet | within 30 days |
| High | CVE-2026-26157 | busybox | 1:1.37.0-6+b8 | No fix yet | within 30 days |
| High | CVE-2026-26158 | busybox | 1:1.37.0-6+b8 | No fix yet | within 30 days |
| High | CVE-2026-29004 | busybox | 1:1.37.0-6+b8 | No fix yet | within 30 days |
| High | CVE-2026-38754 | busybox | 1:1.37.0-6+b8 | No fix yet | within 30 days |
| High | CVE-2026-88830 | busybox | 1:1.37.0-6+b8 | No fix yet | within 30 days |
| High | CVE-2026-88832 | busybox | 1:1.37.0-6+b8 | No fix yet | within 30 days |
| High | CVE-2026-90954 | busybox | 1:1.37.0-6+b8 | No fix yet | within 30 days |
| High | CVE-2026-104715 | cifs-utils | 2:7.4-1 | 2:7.4-1+deb13u1 | within 30 days |
| High | CVE-2026-12505 | cifs-utils | 2:7.4-1 | 2:7.4-1+deb13u1 | within 30 days |
| High | CVE-2026-12064 | curl | 8.14.1-2+deb13u3 | No fix yet | within 30 days |
| High | CVE-2026-5773 | curl | 8.14.1-2+deb13u3 | 8.14.1-2+deb13u4 | within 30 days |
| High | CVE-2026-6276 | curl | 8.14.1-2+deb13u3 | 8.14.1-2+deb13u4 | within 30 days |
| High | CVE-2026-8286 | curl | 8.14.1-2+deb13u3 | 8.14.1-2+deb13u7 | within 30 days |
| High | CVE-2026-8458 | curl | 8.14.1-2+deb13u3 | No fix yet | within 30 days |
| High | CVE-2026-8927 | curl | 8.14.1-2+deb13u3 | 8.14.1-2+deb13u7 | within 30 days |
| High | CVE-2026-92392 | curl | 8.14.1-2+deb13u3 | 8.14.1-2+deb13u7 | within 30 days |
| High | CVE-2026-24882 | dirmngr | 2.4.7-21+deb13u1+b3 | No fix yet | within 30 days |
| High | CVE-2026-93008 | dnsmasq-base | 2.91-1+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-15816 | dracut-install | 106-6 | No fix yet | within 30 days |
| High | CVE-2026-16445 | dracut-install | 106-6 | No fix yet | within 30 days |
| High | CVE-2026-6893 | dracut-install | 106-6 | No fix yet | within 30 days |
| High | CVE-2026-53612 | eject | 2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-53613 | eject | 2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-53614 | eject | 2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-53615 | eject | 2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-76642 | eject | 2.41-5 | No fix yet | within 30 days |
| High | CVE-2026-78408 | eject | 2.41-5 | No fix yet | within 30 days |
| High | CVE-2026-78409 | eject | 2.41-5 | No fix yet | within 30 days |
| High | CVE-2026-78410 | eject | 2.41-5 | No fix yet | within 30 days |
| High | CVE-2026-53612 | fdisk | 2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-53613 | fdisk | 2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-53614 | fdisk | 2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-53615 | fdisk | 2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-76642 | fdisk | 2.41-5 | No fix yet | within 30 days |
| High | CVE-2026-78408 | fdisk | 2.41-5 | No fix yet | within 30 days |
| High | CVE-2026-78409 | fdisk | 2.41-5 | No fix yet | within 30 days |
| High | CVE-2026-78410 | fdisk | 2.41-5 | No fix yet | within 30 days |
| High | CVE-2026-24882 | gnupg | 2.4.7-21+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-24882 | gnupg-l10n | 2.4.7-21+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-24882 | gnupg-utils | 2.4.7-21+deb13u1+b3 | No fix yet | within 30 days |
| High | CVE-2026-24882 | gpg | 2.4.7-21+deb13u1+b3 | No fix yet | within 30 days |
| High | CVE-2026-24882 | gpg-agent | 2.4.7-21+deb13u1+b3 | No fix yet | within 30 days |
| High | CVE-2026-24882 | gpg-wks-client | 2.4.7-21+deb13u1+b3 | No fix yet | within 30 days |
| High | CVE-2026-24882 | gpgconf | 2.4.7-21+deb13u1+b3 | No fix yet | within 30 days |
| High | CVE-2026-24882 | gpgsm | 2.4.7-21+deb13u1+b3 | No fix yet | within 30 days |
| High | CVE-2026-24882 | gpgv | 2.4.7-21+deb13u1+b3 | No fix yet | within 30 days |
| High | CVE-2026-41992 | gzip | 1.13-1 | 1.13-1+deb13u1 | within 30 days |
| High | CVE-2026-54369 | libacl1 | 2.3.2-2+b1 | No fix yet | within 30 days |
| High | CVE-2026-109518 | libapt-pkg7.0 | 3.0.3 | 3.0.4 | within 30 days |
| High | CVE-2026-53612 | libblkid1 | 2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-53613 | libblkid1 | 2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-53614 | libblkid1 | 2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-53615 | libblkid1 | 2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-76642 | libblkid1 | 2.41-5 | No fix yet | within 30 days |
| High | CVE-2026-78408 | libblkid1 | 2.41-5 | No fix yet | within 30 days |
| High | CVE-2026-78409 | libblkid1 | 2.41-5 | No fix yet | within 30 days |
| High | CVE-2026-78410 | libblkid1 | 2.41-5 | No fix yet | within 30 days |
| High | CVE-2023-44431 | libbluetooth3 | 5.82-1.1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-19774 | libbluetooth3 | 5.82-1.1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-80186 | libbluetooth3 | 5.82-1.1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-85218 | libbluetooth3 | 5.82-1.1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-12064 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | No fix yet | within 30 days |
| High | CVE-2026-5773 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | 8.14.1-2+deb13u4 | within 30 days |
| High | CVE-2026-6276 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | 8.14.1-2+deb13u4 | within 30 days |
| High | CVE-2026-8286 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | 8.14.1-2+deb13u7 | within 30 days |
| High | CVE-2026-8458 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | No fix yet | within 30 days |
| High | CVE-2026-8927 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | 8.14.1-2+deb13u7 | within 30 days |
| High | CVE-2026-92392 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | 8.14.1-2+deb13u7 | within 30 days |
| High | CVE-2026-12064 | libcurl4t64 | 8.14.1-2+deb13u3 | No fix yet | within 30 days |
| High | CVE-2026-5773 | libcurl4t64 | 8.14.1-2+deb13u3 | 8.14.1-2+deb13u4 | within 30 days |
| High | CVE-2026-6276 | libcurl4t64 | 8.14.1-2+deb13u3 | 8.14.1-2+deb13u4 | within 30 days |
| High | CVE-2026-8286 | libcurl4t64 | 8.14.1-2+deb13u3 | 8.14.1-2+deb13u7 | within 30 days |
| High | CVE-2026-8458 | libcurl4t64 | 8.14.1-2+deb13u3 | No fix yet | within 30 days |
| High | CVE-2026-8927 | libcurl4t64 | 8.14.1-2+deb13u3 | 8.14.1-2+deb13u7 | within 30 days |
| High | CVE-2026-92392 | libcurl4t64 | 8.14.1-2+deb13u3 | 8.14.1-2+deb13u7 | within 30 days |
| High | CVE-2025-59375 | libexpat1 | 2.7.1-2 | 2.8.2-1~deb13u1 | within 30 days |
| High | CVE-2026-113351 | libexpat1 | 2.7.1-2 | No fix yet | within 30 days |
| High | CVE-2026-115506 | libexpat1 | 2.7.1-2 | No fix yet | within 30 days |
| High | CVE-2026-117610 | libexpat1 | 2.7.1-2 | No fix yet | within 30 days |
| High | CVE-2026-118370 | libexpat1 | 2.7.1-2 | No fix yet | within 30 days |
| High | CVE-2026-25210 | libexpat1 | 2.7.1-2 | 2.8.2-1~deb13u1 | within 30 days |
| High | CVE-2026-45186 | libexpat1 | 2.7.1-2 | 2.8.2-1~deb13u1 | within 30 days |
| High | CVE-2026-66046 | libexpat1 | 2.7.1-2 | 2.9.0-1~deb13u1 | within 30 days |
| High | CVE-2026-76956 | libexpat1 | 2.7.1-2 | 2.9.0-1~deb13u1 | within 30 days |
| High | CVE-2026-76957 | libexpat1 | 2.7.1-2 | 2.9.0-1~deb13u1 | within 30 days |
| High | CVE-2026-77214 | libexpat1 | 2.7.1-2 | 2.9.0-1~deb13u1 | within 30 days |
| High | CVE-2026-93990 | libexpat1 | 2.7.1-2 | 2.9.0-1~deb13u1 | within 30 days |
| High | CVE-2026-53612 | libfdisk1 | 2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-53613 | libfdisk1 | 2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-53614 | libfdisk1 | 2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-53615 | libfdisk1 | 2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-76642 | libfdisk1 | 2.41-5 | No fix yet | within 30 days |
| High | CVE-2026-78408 | libfdisk1 | 2.41-5 | No fix yet | within 30 days |
| High | CVE-2026-78409 | libfdisk1 | 2.41-5 | No fix yet | within 30 days |
| High | CVE-2026-78410 | libfdisk1 | 2.41-5 | No fix yet | within 30 days |
| High | CVE-2026-58010 | libglib2.0-0t64 | 2.84.4-3~deb13u3 | 2.84.4-3~deb13u4 | within 30 days |
| High | CVE-2026-58011 | libglib2.0-0t64 | 2.84.4-3~deb13u3 | 2.84.4-3~deb13u4 | within 30 days |
| High | CVE-2026-58012 | libglib2.0-0t64 | 2.84.4-3~deb13u3 | 2.84.4-3~deb13u4 | within 30 days |
| High | CVE-2026-58013 | libglib2.0-0t64 | 2.84.4-3~deb13u3 | 2.84.4-3~deb13u4 | within 30 days |
| High | CVE-2026-58014 | libglib2.0-0t64 | 2.84.4-3~deb13u3 | 2.84.4-3~deb13u4 | within 30 days |
| High | CVE-2026-58015 | libglib2.0-0t64 | 2.84.4-3~deb13u3 | 2.84.4-3~deb13u4 | within 30 days |
| High | CVE-2026-58010 | libglib2.0-data | 2.84.4-3~deb13u3 | 2.84.4-3~deb13u4 | within 30 days |
| High | CVE-2026-58011 | libglib2.0-data | 2.84.4-3~deb13u3 | 2.84.4-3~deb13u4 | within 30 days |
| High | CVE-2026-58012 | libglib2.0-data | 2.84.4-3~deb13u3 | 2.84.4-3~deb13u4 | within 30 days |
| High | CVE-2026-58013 | libglib2.0-data | 2.84.4-3~deb13u3 | 2.84.4-3~deb13u4 | within 30 days |
| High | CVE-2026-58014 | libglib2.0-data | 2.84.4-3~deb13u3 | 2.84.4-3~deb13u4 | within 30 days |
| High | CVE-2026-58015 | libglib2.0-data | 2.84.4-3~deb13u3 | 2.84.4-3~deb13u4 | within 30 days |
| High | CVE-2026-107364 | libgssapi-krb5-2 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-112315 | libgssapi-krb5-2 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-112316 | libgssapi-krb5-2 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-112317 | libgssapi-krb5-2 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-112318 | libgssapi-krb5-2 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-112319 | libgssapi-krb5-2 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-112320 | libgssapi-krb5-2 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-112321 | libgssapi-krb5-2 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-112322 | libgssapi-krb5-2 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-112323 | libgssapi-krb5-2 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-118380 | libgssapi-krb5-2 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-119079 | libgssapi-krb5-2 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-71199 | libgssapi-krb5-2 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-71200 | libgssapi-krb5-2 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-107364 | libk5crypto3 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-112315 | libk5crypto3 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-112316 | libk5crypto3 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-112317 | libk5crypto3 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-112318 | libk5crypto3 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-112319 | libk5crypto3 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-112320 | libk5crypto3 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-112321 | libk5crypto3 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-112322 | libk5crypto3 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-112323 | libk5crypto3 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-118380 | libk5crypto3 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-119079 | libk5crypto3 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-71199 | libk5crypto3 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-71200 | libk5crypto3 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-107364 | libkrb5-3 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-112315 | libkrb5-3 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-112316 | libkrb5-3 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-112317 | libkrb5-3 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-112318 | libkrb5-3 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-112319 | libkrb5-3 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-112320 | libkrb5-3 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-112321 | libkrb5-3 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-112322 | libkrb5-3 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-112323 | libkrb5-3 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-118380 | libkrb5-3 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-119079 | libkrb5-3 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-71199 | libkrb5-3 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-71200 | libkrb5-3 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-107364 | libkrb5support0 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-112315 | libkrb5support0 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-112316 | libkrb5support0 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-112317 | libkrb5support0 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-112318 | libkrb5support0 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-112319 | libkrb5support0 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-112320 | libkrb5support0 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-112321 | libkrb5support0 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-112322 | libkrb5support0 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-112323 | libkrb5support0 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-118380 | libkrb5support0 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-119079 | libkrb5support0 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-71199 | libkrb5support0 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-71200 | libkrb5support0 | 1.21.3-5+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-53612 | liblastlog2-2 | 2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-53613 | liblastlog2-2 | 2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-53614 | liblastlog2-2 | 2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-53615 | liblastlog2-2 | 2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-76642 | liblastlog2-2 | 2.41-5 | No fix yet | within 30 days |
| High | CVE-2026-78408 | liblastlog2-2 | 2.41-5 | No fix yet | within 30 days |
| High | CVE-2026-78409 | liblastlog2-2 | 2.41-5 | No fix yet | within 30 days |
| High | CVE-2026-78410 | liblastlog2-2 | 2.41-5 | No fix yet | within 30 days |
| High | CVE-2026-53612 | libmount1 | 2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-53613 | libmount1 | 2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-53614 | libmount1 | 2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-53615 | libmount1 | 2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-76642 | libmount1 | 2.41-5 | No fix yet | within 30 days |
| High | CVE-2026-78408 | libmount1 | 2.41-5 | No fix yet | within 30 days |
| High | CVE-2026-78409 | libmount1 | 2.41-5 | No fix yet | within 30 days |
| High | CVE-2026-78410 | libmount1 | 2.41-5 | No fix yet | within 30 days |
| High | CVE-2025-69720 | libncursesw6 | 6.5+20250216-2 | No fix yet | within 30 days |
| High | CVE-2026-42616 | libntfs-3g89t64 | 1:2022.10.3-5+deb13u1 | 1:2022.10.3-5+deb13u2 | within 30 days |
| High | CVE-2026-42617 | libntfs-3g89t64 | 1:2022.10.3-5+deb13u1 | 1:2022.10.3-5+deb13u2 | within 30 days |
| High | CVE-2026-42618 | libntfs-3g89t64 | 1:2022.10.3-5+deb13u1 | 1:2022.10.3-5+deb13u2 | within 30 days |
| High | CVE-2026-46569 | libntfs-3g89t64 | 1:2022.10.3-5+deb13u1 | 1:2022.10.3-5+deb13u2 | within 30 days |
| High | CVE-2026-46570 | libntfs-3g89t64 | 1:2022.10.3-5+deb13u1 | 1:2022.10.3-5+deb13u2 | within 30 days |
| High | CVE-2026-46572 | libntfs-3g89t64 | 1:2022.10.3-5+deb13u1 | 1:2022.10.3-5+deb13u2 | within 30 days |
| High | CVE-2026-56135 | libntfs-3g89t64 | 1:2022.10.3-5+deb13u1 | 1:2022.10.3-5+deb13u2 | within 30 days |
| High | CVE-2026-16742 | libpam-systemd | 257.13-1~deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-0799 | libpcap0.8t64 | 1.10.5-2 | No fix yet | within 30 days |
| High | CVE-2026-6554 | libpcap0.8t64 | 1.10.5-2 | No fix yet | within 30 days |
| High | CVE-2026-103111 | libpcre2-16-0 | 10.46-1~deb13u1 | 10.46-1~deb13u3 | within 30 days |
| High | CVE-2026-86145 | libpcre2-16-0 | 10.46-1~deb13u1 | 10.46-1~deb13u2 | within 30 days |
| High | CVE-2026-89157 | libpcre2-16-0 | 10.46-1~deb13u1 | 10.46-1~deb13u2 | within 30 days |
| High | CVE-2026-89161 | libpcre2-16-0 | 10.46-1~deb13u1 | 10.46-1~deb13u2 | within 30 days |
| High | CVE-2026-103111 | libpcre2-8-0 | 10.46-1~deb13u1 | 10.46-1~deb13u3 | within 30 days |
| High | CVE-2026-86145 | libpcre2-8-0 | 10.46-1~deb13u1 | 10.46-1~deb13u2 | within 30 days |
| High | CVE-2026-89157 | libpcre2-8-0 | 10.46-1~deb13u1 | 10.46-1~deb13u2 | within 30 days |
| High | CVE-2026-89161 | libpcre2-8-0 | 10.46-1~deb13u1 | 10.46-1~deb13u2 | within 30 days |
| High | CVE-2026-42497 | libperl5.40 | 5.40.1-6 | 5.40.1-6+deb13u1 | within 30 days |
| High | CVE-2026-48962 | libperl5.40 | 5.40.1-6 | 5.40.1-6+deb13u1 | within 30 days |
| High | CVE-2026-57432 | libperl5.40 | 5.40.1-6 | 5.40.1-6+deb13u1 | within 30 days |
| High | CVE-2026-57433 | libperl5.40 | 5.40.1-6 | 5.40.1-6+deb13u1 | within 30 days |
| High | CVE-2026-9538 | libperl5.40 | 5.40.1-6 | No fix yet | within 30 days |
| High | CVE-2026-11940 | libpython3.13 | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u5 | within 30 days |
| High | CVE-2026-15308 | libpython3.13 | 3.13.5-2+deb13u2 | No fix yet | within 30 days |
| High | CVE-2026-19445 | libpython3.13 | 3.13.5-2+deb13u2 | No fix yet | within 30 days |
| High | CVE-2026-19553 | libpython3.13 | 3.13.5-2+deb13u2 | No fix yet | within 30 days |
| High | CVE-2026-7210 | libpython3.13 | 3.13.5-2+deb13u2 | No fix yet | within 30 days |
| High | CVE-2026-82049 | libpython3.13 | 3.13.5-2+deb13u2 | No fix yet | within 30 days |
| High | CVE-2026-8328 | libpython3.13 | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u3 | within 30 days |
| High | CVE-2026-11940 | libpython3.13-minimal | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u5 | within 30 days |
| High | CVE-2026-15308 | libpython3.13-minimal | 3.13.5-2+deb13u2 | No fix yet | within 30 days |
| High | CVE-2026-19445 | libpython3.13-minimal | 3.13.5-2+deb13u2 | No fix yet | within 30 days |
| High | CVE-2026-19553 | libpython3.13-minimal | 3.13.5-2+deb13u2 | No fix yet | within 30 days |
| High | CVE-2026-7210 | libpython3.13-minimal | 3.13.5-2+deb13u2 | No fix yet | within 30 days |
| High | CVE-2026-82049 | libpython3.13-minimal | 3.13.5-2+deb13u2 | No fix yet | within 30 days |
| High | CVE-2026-8328 | libpython3.13-minimal | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u3 | within 30 days |
| High | CVE-2026-11940 | libpython3.13-stdlib | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u5 | within 30 days |
| High | CVE-2026-15308 | libpython3.13-stdlib | 3.13.5-2+deb13u2 | No fix yet | within 30 days |
| High | CVE-2026-19445 | libpython3.13-stdlib | 3.13.5-2+deb13u2 | No fix yet | within 30 days |
| High | CVE-2026-19553 | libpython3.13-stdlib | 3.13.5-2+deb13u2 | No fix yet | within 30 days |
| High | CVE-2026-7210 | libpython3.13-stdlib | 3.13.5-2+deb13u2 | No fix yet | within 30 days |
| High | CVE-2026-82049 | libpython3.13-stdlib | 3.13.5-2+deb13u2 | No fix yet | within 30 days |
| High | CVE-2026-8328 | libpython3.13-stdlib | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u3 | within 30 days |
| High | CVE-2026-16762 | libqt6core6t64 | 6.8.2+dfsg-9+deb13u2 | No fix yet | within 30 days |
| High | CVE-2026-76151 | libqt6core6t64 | 6.8.2+dfsg-9+deb13u2 | No fix yet | within 30 days |
| High | CVE-2026-53612 | libsmartcols1 | 2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-53613 | libsmartcols1 | 2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-53614 | libsmartcols1 | 2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-53615 | libsmartcols1 | 2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-76642 | libsmartcols1 | 2.41-5 | No fix yet | within 30 days |
| High | CVE-2026-78408 | libsmartcols1 | 2.41-5 | No fix yet | within 30 days |
| High | CVE-2026-78409 | libsmartcols1 | 2.41-5 | No fix yet | within 30 days |
| High | CVE-2026-78410 | libsmartcols1 | 2.41-5 | No fix yet | within 30 days |
| High | CVE-2026-11822 | libsqlite3-0 | 3.46.1-7+deb13u1 | 3.46.1-7+deb13u2 | within 30 days |
| High | CVE-2026-11824 | libsqlite3-0 | 3.46.1-7+deb13u1 | 3.46.1-7+deb13u2 | within 30 days |
| High | CVE-2026-119373 | libsqlite3-0 | 3.46.1-7+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-119374 | libsqlite3-0 | 3.46.1-7+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-119379 | libsqlite3-0 | 3.46.1-7+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-55199 | libssh2-1t64 | 1.11.1-1 | 1.11.1-1+deb13u1 | within 30 days |
| High | CVE-2026-55200 | libssh2-1t64 | 1.11.1-1 | 1.11.1-1+deb13u1 | within 30 days |
| High | CVE-2026-58050 | libssh2-1t64 | 1.11.1-1 | 1.11.1-1+deb13u2 | within 30 days |
| High | CVE-2026-7598 | libssh2-1t64 | 1.11.1-1 | 1.11.1-1+deb13u1 | within 30 days |
| High | CVE-2026-124709 | libssl3t64 | 3.5.6-1~deb13u2+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-14456 | libssl3t64 | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u2 | within 30 days |
| High | CVE-2026-84782 | libssl3t64 | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u3 | within 30 days |
| High | CVE-2026-16742 | libsystemd-shared | 257.13-1~deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-16742 | libsystemd0 | 257.13-1~deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-58221 | libtalloc2 | 2:2.4.3+samba4.22.8+dfsg-0+deb13u2 | 2:4.22.10+dfsg-0+deb13u2 | within 30 days |
| High | CVE-2026-58222 | libtalloc2 | 2:2.4.3+samba4.22.8+dfsg-0+deb13u2 | 2:4.22.10+dfsg-0+deb13u2 | within 30 days |
| High | CVE-2026-6949 | libtalloc2 | 2:2.4.3+samba4.22.8+dfsg-0+deb13u2 | 2:4.22.10+dfsg-0+deb13u2 | within 30 days |
| High | CVE-2026-12912 | libtiff6 | 4.7.0-3+deb13u2 | 4.7.0-3+deb13u3 | within 30 days |
| High | CVE-2026-36849 | libtiff6 | 4.7.0-3+deb13u2 | No fix yet | within 30 days |
| High | CVE-2026-52490 | libtiff6 | 4.7.0-3+deb13u2 | No fix yet | within 30 days |
| High | CVE-2025-69720 | libtinfo6 | 6.5+20250216-2 | No fix yet | within 30 days |
| High | CVE-2026-16742 | libudev1 | 257.13-1~deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-7867 | libudisks2-0 | 2.10.1-12.1+deb13u1 | 2.10.1-12.1+deb13u2 | within 30 days |
| High | CVE-2026-53612 | libuuid1 | 2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-53613 | libuuid1 | 2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-53614 | libuuid1 | 2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-53615 | libuuid1 | 2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-76642 | libuuid1 | 2.41-5 | No fix yet | within 30 days |
| High | CVE-2026-78408 | libuuid1 | 2.41-5 | No fix yet | within 30 days |
| High | CVE-2026-78409 | libuuid1 | 2.41-5 | No fix yet | within 30 days |
| High | CVE-2026-78410 | libuuid1 | 2.41-5 | No fix yet | within 30 days |
| High | CVE-2026-58221 | libwbclient0 | 2:4.22.8+dfsg-0+deb13u2 | 2:4.22.10+dfsg-0+deb13u2 | within 30 days |
| High | CVE-2026-58222 | libwbclient0 | 2:4.22.8+dfsg-0+deb13u2 | 2:4.22.10+dfsg-0+deb13u2 | within 30 days |
| High | CVE-2026-6949 | libwbclient0 | 2:4.22.8+dfsg-0+deb13u2 | 2:4.22.10+dfsg-0+deb13u2 | within 30 days |
| High | CVE-2026-88806 | libx11-6 | 2:1.8.12-1 | No fix yet | within 30 days |
| High | CVE-2026-88806 | libx11-data | 2:1.8.12-1 | No fix yet | within 30 days |
| High | CVE-2026-74860 | libxml2 | 2.12.7+dfsg+really2.9.14-2.1+deb13u2 | No fix yet | within 30 days |
| High | CVE-2026-86138 | libxml2 | 2.12.7+dfsg+really2.9.14-2.1+deb13u2 | No fix yet | within 30 days |
| High | CVE-2026-86139 | libxml2 | 2.12.7+dfsg+really2.9.14-2.1+deb13u2 | No fix yet | within 30 days |
| High | CVE-2026-86140 | libxml2 | 2.12.7+dfsg+really2.9.14-2.1+deb13u2 | No fix yet | within 30 days |
| High | CVE-2026-86142 | libxml2 | 2.12.7+dfsg+really2.9.14-2.1+deb13u2 | No fix yet | within 30 days |
| High | CVE-2026-86143 | libxml2 | 2.12.7+dfsg+really2.9.14-2.1+deb13u2 | No fix yet | within 30 days |
| High | CVE-2026-86144 | libxml2 | 2.12.7+dfsg+really2.9.14-2.1+deb13u2 | No fix yet | within 30 days |
| High | CVE-2013-7445 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2019-19449 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2019-19814 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2021-3847 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2021-3864 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2024-21803 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2024-21963 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2024-58015 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-0004 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-23102 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-31568 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-46279 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-72042 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-89675 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-90315 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-98118 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-98364 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99272 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99312 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99387 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99568 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99580 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99583 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99590 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99591 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99603 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99634 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99636 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99659 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99661 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99662 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99677 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99679 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99707 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99709 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99748 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99754 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99758 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99785 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99798 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2013-7445 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2019-19449 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2019-19814 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2021-3847 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2021-3864 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2024-21803 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2024-21963 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2024-58015 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-0004 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-23102 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-31568 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-46279 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-72042 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-89675 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-90315 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-98118 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-98364 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99272 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99312 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99387 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99568 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99580 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99583 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99590 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99591 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99603 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99634 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99636 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99659 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99661 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99662 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99677 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99679 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99707 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99709 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99748 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99754 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99758 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99785 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99798 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2013-7445 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2019-19449 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2019-19814 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2021-3847 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2021-3864 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2024-21803 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2024-21963 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2024-58015 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-0004 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-23102 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-31568 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-46279 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-72042 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-89675 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-90315 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-98118 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-98364 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99272 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99312 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99387 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99568 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99580 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99583 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99590 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99591 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99603 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99634 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99636 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99659 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99661 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99662 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99677 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99679 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99707 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99709 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99748 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99754 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99758 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99785 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99798 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2013-7445 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2019-19449 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2019-19814 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2021-3847 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2021-3864 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2024-21803 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2024-21963 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2024-58015 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-0004 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-23102 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-31568 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-46279 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-72042 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-89675 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-90315 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-98118 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-98364 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99272 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99312 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99387 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99568 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99580 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99583 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99590 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99591 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99603 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99634 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99636 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99659 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99661 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99662 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99677 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99679 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99707 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99709 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99748 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99754 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99758 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99785 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99798 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2013-7445 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2019-19449 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2019-19814 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2021-3847 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2021-3864 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2024-21803 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2024-21963 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2024-58015 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-0004 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-23102 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-31568 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-46279 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-72042 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-89675 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-90315 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-98118 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-98364 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99272 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99312 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99387 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99568 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99580 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99583 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99590 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99591 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99603 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99634 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99636 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99659 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99661 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99662 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99677 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99679 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99707 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99709 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99748 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99754 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99758 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99785 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99798 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2013-7445 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2019-19449 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2019-19814 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2021-3847 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2021-3864 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2024-21803 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2024-21963 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2024-58015 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-0004 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-23102 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-31568 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-46279 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-72042 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-89675 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-90315 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-98118 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-98364 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99272 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99312 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99387 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99568 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99580 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99583 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99590 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99591 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99603 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99634 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99636 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99659 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99661 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99662 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99677 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99679 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99707 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99709 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99748 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99754 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99758 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99785 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99798 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2013-7445 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2019-19449 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2019-19814 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2021-3847 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2021-3864 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2024-21803 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2024-21963 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2024-58015 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-0004 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-23102 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-31568 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-46279 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-72042 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-89675 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-90315 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-98118 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-98364 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99272 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99312 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99387 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99568 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99580 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99583 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99590 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99591 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99603 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99634 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99636 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99659 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99661 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99662 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99677 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99679 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99707 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99709 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99748 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99754 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99758 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99785 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99798 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2013-7445 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2019-19449 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2019-19814 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2021-3847 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2021-3864 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2024-21803 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2024-21963 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2024-58015 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-0004 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-23102 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-31568 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-46279 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-72042 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-89675 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-90315 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-98118 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-98364 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99272 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99312 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99387 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99568 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99580 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99583 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99590 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99591 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99603 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99634 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99636 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99659 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99661 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99662 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99677 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99679 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99707 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99709 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99748 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99754 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99758 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99785 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99798 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2013-7445 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2019-19449 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2019-19814 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2021-3847 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2021-3864 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2024-21803 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2024-21963 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2024-58015 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-0004 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-23102 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-31568 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-46279 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-72042 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-89675 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-90315 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-98118 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-98364 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99272 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99312 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99387 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99568 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99580 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99583 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99590 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99591 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99603 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99634 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99636 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99659 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99661 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99662 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99677 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99679 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99707 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99709 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99748 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99754 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99758 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99785 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99798 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2013-7445 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2019-19449 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2019-19814 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2021-3847 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2021-3864 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2024-21803 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2024-21963 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2024-58015 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-0004 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-23102 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-31568 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-46279 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-72042 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-89675 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-90315 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-98118 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-98364 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99272 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99312 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99387 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99568 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99580 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99583 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99590 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99591 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99603 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99634 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99636 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99659 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99661 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99662 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99677 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99679 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99707 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99709 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99748 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99754 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99758 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99785 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99798 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2013-7445 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2019-19449 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2019-19814 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2021-3847 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2021-3864 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2024-21803 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2024-21963 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2024-58015 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-0004 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-23102 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-31568 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-46279 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-72042 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-89675 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-90315 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-98118 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-98364 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99272 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99312 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99387 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99568 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99580 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99583 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99590 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99591 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99603 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99634 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99636 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99659 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99661 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99662 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99677 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99679 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99707 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99709 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99748 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99754 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99758 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99785 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99798 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2013-7445 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2019-19449 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2019-19814 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2021-3847 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2021-3864 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2024-21803 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2024-21963 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2024-58015 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-0004 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-23102 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-31568 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-46279 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-72042 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-89675 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-90315 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-98118 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-98364 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99272 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99312 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99387 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99568 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99580 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99583 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99590 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99591 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99603 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99634 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99636 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99659 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99661 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99662 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99677 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99679 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99707 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99709 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99748 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99754 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99758 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99785 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99798 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2013-7445 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2019-19449 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2019-19814 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2021-3847 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2021-3864 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2024-21803 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2024-21963 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2024-58015 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-0004 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-23102 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-31568 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-46279 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-72042 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-89675 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-90315 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-98118 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-98364 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99272 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99312 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99387 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99568 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99580 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99583 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99590 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99591 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99603 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99634 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99636 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99659 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99661 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99662 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99677 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99679 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99707 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99709 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99748 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99754 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99758 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99785 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99798 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2013-7445 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2019-19449 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2019-19814 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2021-3847 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2021-3864 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2024-21803 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2024-21963 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2024-58015 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-0004 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-23102 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-31568 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-46279 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-72042 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-89675 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-90315 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-98118 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-98364 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99272 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99312 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99387 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99568 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99580 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99583 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99590 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99591 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99603 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99634 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99636 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99659 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99661 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99662 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99677 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99679 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99707 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99709 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99748 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99754 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99758 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99785 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99798 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2013-7445 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2019-19449 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2019-19814 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2021-3847 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2021-3864 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2024-21803 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2024-21963 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2024-58015 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-0004 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-23102 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-31568 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-46279 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-72042 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-89675 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-90315 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-98118 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-98364 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99272 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99312 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99387 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99568 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99580 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99583 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99590 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99591 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99603 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99634 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99636 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99659 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99661 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99662 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99677 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99679 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99707 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99709 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99748 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99754 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99758 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99785 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-99798 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-53612 | login | 1:4.16.0-2+really2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-53613 | login | 1:4.16.0-2+really2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-53614 | login | 1:4.16.0-2+really2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-53615 | login | 1:4.16.0-2+really2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-76642 | login | 1:4.16.0-2+really2.41-5 | No fix yet | within 30 days |
| High | CVE-2026-78408 | login | 1:4.16.0-2+really2.41-5 | No fix yet | within 30 days |
| High | CVE-2026-78409 | login | 1:4.16.0-2+really2.41-5 | No fix yet | within 30 days |
| High | CVE-2026-78410 | login | 1:4.16.0-2+really2.41-5 | No fix yet | within 30 days |
| High | CVE-2026-90783 | mkvtoolnix | 92.0-1 | 92.0-1+deb13u1 | within 30 days |
| High | CVE-2026-53612 | mount | 2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-53613 | mount | 2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-53614 | mount | 2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-53615 | mount | 2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-76642 | mount | 2.41-5 | No fix yet | within 30 days |
| High | CVE-2026-78408 | mount | 2.41-5 | No fix yet | within 30 days |
| High | CVE-2026-78409 | mount | 2.41-5 | No fix yet | within 30 days |
| High | CVE-2026-78410 | mount | 2.41-5 | No fix yet | within 30 days |
| High | CVE-2025-69720 | ncurses-base | 6.5+20250216-2 | No fix yet | within 30 days |
| High | CVE-2025-69720 | ncurses-bin | 6.5+20250216-2 | No fix yet | within 30 days |
| High | CVE-2025-69720 | ncurses-term | 6.5+20250216-2 | No fix yet | within 30 days |
| High | CVE-2026-42616 | ntfs-3g | 1:2022.10.3-5+deb13u1 | 1:2022.10.3-5+deb13u2 | within 30 days |
| High | CVE-2026-42617 | ntfs-3g | 1:2022.10.3-5+deb13u1 | 1:2022.10.3-5+deb13u2 | within 30 days |
| High | CVE-2026-42618 | ntfs-3g | 1:2022.10.3-5+deb13u1 | 1:2022.10.3-5+deb13u2 | within 30 days |
| High | CVE-2026-46569 | ntfs-3g | 1:2022.10.3-5+deb13u1 | 1:2022.10.3-5+deb13u2 | within 30 days |
| High | CVE-2026-46570 | ntfs-3g | 1:2022.10.3-5+deb13u1 | 1:2022.10.3-5+deb13u2 | within 30 days |
| High | CVE-2026-46572 | ntfs-3g | 1:2022.10.3-5+deb13u1 | 1:2022.10.3-5+deb13u2 | within 30 days |
| High | CVE-2026-56135 | ntfs-3g | 1:2022.10.3-5+deb13u1 | 1:2022.10.3-5+deb13u2 | within 30 days |
| High | CVE-2026-106553 | openssh-client | 1:10.0p1-7+deb13u4 | No fix yet | within 30 days |
| High | CVE-2026-106555 | openssh-client | 1:10.0p1-7+deb13u4 | No fix yet | within 30 days |
| High | CVE-2026-106583 | openssh-client | 1:10.0p1-7+deb13u4 | No fix yet | within 30 days |
| High | CVE-2026-59999 | openssh-client | 1:10.0p1-7+deb13u4 | No fix yet | within 30 days |
| High | CVE-2026-60000 | openssh-client | 1:10.0p1-7+deb13u4 | No fix yet | within 30 days |
| High | CVE-2026-106553 | openssh-server | 1:10.0p1-7+deb13u4 | No fix yet | within 30 days |
| High | CVE-2026-106555 | openssh-server | 1:10.0p1-7+deb13u4 | No fix yet | within 30 days |
| High | CVE-2026-106583 | openssh-server | 1:10.0p1-7+deb13u4 | No fix yet | within 30 days |
| High | CVE-2026-59999 | openssh-server | 1:10.0p1-7+deb13u4 | No fix yet | within 30 days |
| High | CVE-2026-60000 | openssh-server | 1:10.0p1-7+deb13u4 | No fix yet | within 30 days |
| High | CVE-2026-106553 | openssh-sftp-server | 1:10.0p1-7+deb13u4 | No fix yet | within 30 days |
| High | CVE-2026-106555 | openssh-sftp-server | 1:10.0p1-7+deb13u4 | No fix yet | within 30 days |
| High | CVE-2026-106583 | openssh-sftp-server | 1:10.0p1-7+deb13u4 | No fix yet | within 30 days |
| High | CVE-2026-59999 | openssh-sftp-server | 1:10.0p1-7+deb13u4 | No fix yet | within 30 days |
| High | CVE-2026-60000 | openssh-sftp-server | 1:10.0p1-7+deb13u4 | No fix yet | within 30 days |
| High | CVE-2026-124709 | openssl | 3.5.6-1~deb13u2+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-14456 | openssl | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u2 | within 30 days |
| High | CVE-2026-84782 | openssl | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u3 | within 30 days |
| High | CVE-2026-124709 | openssl-provider-legacy | 3.5.6-1~deb13u2+rpt1 | No fix yet | within 30 days |
| High | CVE-2026-14456 | openssl-provider-legacy | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u2 | within 30 days |
| High | CVE-2026-84782 | openssl-provider-legacy | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u3 | within 30 days |
| High | CVE-2026-42497 | perl | 5.40.1-6 | 5.40.1-6+deb13u1 | within 30 days |
| High | CVE-2026-48962 | perl | 5.40.1-6 | 5.40.1-6+deb13u1 | within 30 days |
| High | CVE-2026-57432 | perl | 5.40.1-6 | 5.40.1-6+deb13u1 | within 30 days |
| High | CVE-2026-57433 | perl | 5.40.1-6 | 5.40.1-6+deb13u1 | within 30 days |
| High | CVE-2026-9538 | perl | 5.40.1-6 | No fix yet | within 30 days |
| High | CVE-2026-42497 | perl-base | 5.40.1-6 | 5.40.1-6+deb13u1 | within 30 days |
| High | CVE-2026-48962 | perl-base | 5.40.1-6 | 5.40.1-6+deb13u1 | within 30 days |
| High | CVE-2026-57432 | perl-base | 5.40.1-6 | 5.40.1-6+deb13u1 | within 30 days |
| High | CVE-2026-57433 | perl-base | 5.40.1-6 | 5.40.1-6+deb13u1 | within 30 days |
| High | CVE-2026-9538 | perl-base | 5.40.1-6 | No fix yet | within 30 days |
| High | CVE-2026-42497 | perl-modules-5.40 | 5.40.1-6 | 5.40.1-6+deb13u1 | within 30 days |
| High | CVE-2026-48962 | perl-modules-5.40 | 5.40.1-6 | 5.40.1-6+deb13u1 | within 30 days |
| High | CVE-2026-57432 | perl-modules-5.40 | 5.40.1-6 | 5.40.1-6+deb13u1 | within 30 days |
| High | CVE-2026-57433 | perl-modules-5.40 | 5.40.1-6 | 5.40.1-6+deb13u1 | within 30 days |
| High | CVE-2026-9538 | perl-modules-5.40 | 5.40.1-6 | No fix yet | within 30 days |
| High | CVE-2026-69249 | python3-cryptography | 43.0.0-3+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-101917 | python3-jwt | 2.10.1-2+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-101918 | python3-jwt | 2.10.1-2+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-102271 | python3-jwt | 2.10.1-2+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-102272 | python3-jwt | 2.10.1-2+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-102273 | python3-jwt | 2.10.1-2+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-102274 | python3-jwt | 2.10.1-2+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-102275 | python3-jwt | 2.10.1-2+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-48526 | python3-jwt | 2.10.1-2+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-118669 | python3-oauthlib | 3.2.2-3 | No fix yet | within 30 days |
| High | CVE-2026-49272 | python3-oauthlib | 3.2.2-3 | No fix yet | within 30 days |
| High | CVE-2026-23949 | python3-setuptools-whl | 78.1.1-0.1 | No fix yet | within 30 days |
| High | CVE-2025-66471 | python3-urllib3 | 2.3.0-3+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-97687 | python3-urllib3 | 2.3.0-3+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-97689 | python3-urllib3 | 2.3.0-3+deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-11940 | python3.13 | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u5 | within 30 days |
| High | CVE-2026-15308 | python3.13 | 3.13.5-2+deb13u2 | No fix yet | within 30 days |
| High | CVE-2026-19445 | python3.13 | 3.13.5-2+deb13u2 | No fix yet | within 30 days |
| High | CVE-2026-19553 | python3.13 | 3.13.5-2+deb13u2 | No fix yet | within 30 days |
| High | CVE-2026-7210 | python3.13 | 3.13.5-2+deb13u2 | No fix yet | within 30 days |
| High | CVE-2026-82049 | python3.13 | 3.13.5-2+deb13u2 | No fix yet | within 30 days |
| High | CVE-2026-8328 | python3.13 | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u3 | within 30 days |
| High | CVE-2026-11940 | python3.13-minimal | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u5 | within 30 days |
| High | CVE-2026-15308 | python3.13-minimal | 3.13.5-2+deb13u2 | No fix yet | within 30 days |
| High | CVE-2026-19445 | python3.13-minimal | 3.13.5-2+deb13u2 | No fix yet | within 30 days |
| High | CVE-2026-19553 | python3.13-minimal | 3.13.5-2+deb13u2 | No fix yet | within 30 days |
| High | CVE-2026-7210 | python3.13-minimal | 3.13.5-2+deb13u2 | No fix yet | within 30 days |
| High | CVE-2026-82049 | python3.13-minimal | 3.13.5-2+deb13u2 | No fix yet | within 30 days |
| High | CVE-2026-8328 | python3.13-minimal | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u3 | within 30 days |
| High | CVE-2026-11940 | python3.13-venv | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u5 | within 30 days |
| High | CVE-2026-15308 | python3.13-venv | 3.13.5-2+deb13u2 | No fix yet | within 30 days |
| High | CVE-2026-19445 | python3.13-venv | 3.13.5-2+deb13u2 | No fix yet | within 30 days |
| High | CVE-2026-19553 | python3.13-venv | 3.13.5-2+deb13u2 | No fix yet | within 30 days |
| High | CVE-2026-7210 | python3.13-venv | 3.13.5-2+deb13u2 | No fix yet | within 30 days |
| High | CVE-2026-82049 | python3.13-venv | 3.13.5-2+deb13u2 | No fix yet | within 30 days |
| High | CVE-2026-8328 | python3.13-venv | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u3 | within 30 days |
| High | CVE-2026-53612 | rfkill | 2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-53613 | rfkill | 2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-53614 | rfkill | 2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-53615 | rfkill | 2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-76642 | rfkill | 2.41-5 | No fix yet | within 30 days |
| High | CVE-2026-78408 | rfkill | 2.41-5 | No fix yet | within 30 days |
| High | CVE-2026-78409 | rfkill | 2.41-5 | No fix yet | within 30 days |
| High | CVE-2026-78410 | rfkill | 2.41-5 | No fix yet | within 30 days |
| High | CVE-2026-119741 | rsync | 3.4.1+ds1-5+deb13u3 | 3.5.0+ds1-0+deb13u2 | within 30 days |
| High | CVE-2026-53783 | rsync | 3.4.1+ds1-5+deb13u3 | 3.5.0+ds1-0+deb13u1 | within 30 days |
| High | CVE-2026-53784 | rsync | 3.4.1+ds1-5+deb13u3 | 3.5.0+ds1-0+deb13u1 | within 30 days |
| High | CVE-2026-53785 | rsync | 3.4.1+ds1-5+deb13u3 | 3.5.0+ds1-0+deb13u1 | within 30 days |
| High | CVE-2026-53789 | rsync | 3.4.1+ds1-5+deb13u3 | 3.5.0+ds1-0+deb13u1 | within 30 days |
| High | CVE-2026-53790 | rsync | 3.4.1+ds1-5+deb13u3 | 3.5.0+ds1-0+deb13u1 | within 30 days |
| High | CVE-2026-53791 | rsync | 3.4.1+ds1-5+deb13u3 | 3.5.0+ds1-0+deb13u1 | within 30 days |
| High | CVE-2026-53793 | rsync | 3.4.1+ds1-5+deb13u3 | 3.5.0+ds1-0+deb13u1 | within 30 days |
| High | CVE-2026-53795 | rsync | 3.4.1+ds1-5+deb13u3 | 3.5.0+ds1-0+deb13u1 | within 30 days |
| High | CVE-2026-53802 | rsync | 3.4.1+ds1-5+deb13u3 | 3.5.0+ds1-0+deb13u1 | within 30 days |
| High | CVE-2026-53803 | rsync | 3.4.1+ds1-5+deb13u3 | 3.5.0+ds1-0+deb13u1 | within 30 days |
| High | CVE-2026-70452 | rsync | 3.4.1+ds1-5+deb13u3 | 3.5.0+ds1-0+deb13u1 | within 30 days |
| High | CVE-2026-70455 | rsync | 3.4.1+ds1-5+deb13u3 | 3.5.0+ds1-0+deb13u1 | within 30 days |
| High | CVE-2026-70456 | rsync | 3.4.1+ds1-5+deb13u3 | 3.5.0+ds1-0+deb13u1 | within 30 days |
| High | CVE-2026-70457 | rsync | 3.4.1+ds1-5+deb13u3 | 3.5.0+ds1-0+deb13u1 | within 30 days |
| High | CVE-2026-70458 | rsync | 3.4.1+ds1-5+deb13u3 | 3.5.0+ds1-0+deb13u1 | within 30 days |
| High | CVE-2026-70460 | rsync | 3.4.1+ds1-5+deb13u3 | 3.5.0+ds1-0+deb13u1 | within 30 days |
| High | CVE-2026-70461 | rsync | 3.4.1+ds1-5+deb13u3 | 3.5.0+ds1-0+deb13u1 | within 30 days |
| High | CVE-2026-70463 | rsync | 3.4.1+ds1-5+deb13u3 | 3.5.0+ds1-0+deb13u1 | within 30 days |
| High | CVE-2026-70464 | rsync | 3.4.1+ds1-5+deb13u3 | 3.5.0+ds1-0+deb13u1 | within 30 days |
| High | CVE-2026-106553 | ssh | 1:10.0p1-7+deb13u4 | No fix yet | within 30 days |
| High | CVE-2026-106555 | ssh | 1:10.0p1-7+deb13u4 | No fix yet | within 30 days |
| High | CVE-2026-106583 | ssh | 1:10.0p1-7+deb13u4 | No fix yet | within 30 days |
| High | CVE-2026-59999 | ssh | 1:10.0p1-7+deb13u4 | No fix yet | within 30 days |
| High | CVE-2026-60000 | ssh | 1:10.0p1-7+deb13u4 | No fix yet | within 30 days |
| High | CVE-2026-96512 | sudo | 1.9.16p2-3+deb13u2 | 1.9.16p2-3+deb13u5 | within 30 days |
| High | CVE-2026-16742 | systemd | 257.13-1~deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-16742 | systemd-sysv | 257.13-1~deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-16742 | systemd-timesyncd | 257.13-1~deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-16742 | udev | 257.13-1~deb13u1 | No fix yet | within 30 days |
| High | CVE-2026-7867 | udisks2 | 2.10.1-12.1+deb13u1 | 2.10.1-12.1+deb13u2 | within 30 days |
| High | CVE-2026-53612 | util-linux | 2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-53613 | util-linux | 2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-53614 | util-linux | 2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-53615 | util-linux | 2.41-5 | 2.41.5-0+deb13u1 | within 30 days |
| High | CVE-2026-76642 | util-linux | 2.41-5 | No fix yet | within 30 days |
| High | CVE-2026-78408 | util-linux | 2.41-5 | No fix yet | within 30 days |
| High | CVE-2026-78409 | util-linux | 2.41-5 | No fix yet | within 30 days |
| High | CVE-2026-78410 | util-linux | 2.41-5 | No fix yet | within 30 days |
| High | CVE-2026-26269 | vim-common | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | within 30 days |
| High | CVE-2026-28417 | vim-common | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | within 30 days |
| High | CVE-2026-28421 | vim-common | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | within 30 days |
| High | CVE-2026-33412 | vim-common | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | within 30 days |
| High | CVE-2026-34982 | vim-common | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | within 30 days |
| High | CVE-2026-35177 | vim-common | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | within 30 days |
| High | CVE-2026-39881 | vim-common | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | within 30 days |
| High | CVE-2026-43961 | vim-common | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | within 30 days |
| High | CVE-2026-46483 | vim-common | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | within 30 days |
| High | CVE-2026-47162 | vim-common | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | within 30 days |
| High | CVE-2026-52858 | vim-common | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | within 30 days |
| High | CVE-2026-52859 | vim-common | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | within 30 days |
| High | CVE-2026-52860 | vim-common | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | within 30 days |
| High | CVE-2026-55693 | vim-common | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | within 30 days |
| High | CVE-2026-55895 | vim-common | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | within 30 days |
| High | CVE-2026-57455 | vim-common | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | within 30 days |
| High | CVE-2026-57456 | vim-common | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | within 30 days |
| High | CVE-2026-59856 | vim-common | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | within 30 days |
| High | CVE-2026-59858 | vim-common | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | within 30 days |
| High | CVE-2026-73072 | vim-common | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | within 30 days |
| High | CVE-2026-73073 | vim-common | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | within 30 days |
| High | CVE-2026-73076 | vim-common | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | within 30 days |
| High | CVE-2026-73077 | vim-common | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | within 30 days |
| High | CVE-2026-73078 | vim-common | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | within 30 days |
| High | CVE-2026-26269 | vim-tiny | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | within 30 days |
| High | CVE-2026-28417 | vim-tiny | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | within 30 days |
| High | CVE-2026-28421 | vim-tiny | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | within 30 days |
| High | CVE-2026-33412 | vim-tiny | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | within 30 days |
| High | CVE-2026-34982 | vim-tiny | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | within 30 days |
| High | CVE-2026-35177 | vim-tiny | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | within 30 days |
| High | CVE-2026-39881 | vim-tiny | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | within 30 days |
| High | CVE-2026-43961 | vim-tiny | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | within 30 days |
| High | CVE-2026-46483 | vim-tiny | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | within 30 days |
| High | CVE-2026-47162 | vim-tiny | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | within 30 days |
| High | CVE-2026-52858 | vim-tiny | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | within 30 days |
| High | CVE-2026-52859 | vim-tiny | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | within 30 days |
| High | CVE-2026-52860 | vim-tiny | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | within 30 days |
| High | CVE-2026-55693 | vim-tiny | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | within 30 days |
| High | CVE-2026-55895 | vim-tiny | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | within 30 days |
| High | CVE-2026-57455 | vim-tiny | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | within 30 days |
| High | CVE-2026-57456 | vim-tiny | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | within 30 days |
| High | CVE-2026-59856 | vim-tiny | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | within 30 days |
| High | CVE-2026-59858 | vim-tiny | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | within 30 days |
| High | CVE-2026-73072 | vim-tiny | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | within 30 days |
| High | CVE-2026-73073 | vim-tiny | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | within 30 days |
| High | CVE-2026-73076 | vim-tiny | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | within 30 days |
| High | CVE-2026-73077 | vim-tiny | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | within 30 days |
| High | CVE-2026-73078 | vim-tiny | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | within 30 days |
| High | CVE-2026-58471 | wget | 1.25.0-2 | No fix yet | within 30 days |
| High | CVE-2026-58472 | wget | 1.25.0-2 | No fix yet | within 30 days |
| High | CVE-2026-78807 | wpasupplicant | 2:2.10-24 | No fix yet | within 30 days |
| High | CVE-2026-85091 | zlib1g | 1:1.3.dfsg+really1.3.1-1+b1 | 1:1.3.dfsg+really1.3.1-1+deb13u1 | within 30 days |
| High | CVE-2026-56854 | golang.org/x/crypto | v0.53.0 | 0.55.0 | within 30 days |
| High | CVE-2026-46600 | golang.org/x/net | v0.55.0 | 0.56.0 | within 30 days |
| High | CVE-2026-78661 | golang.org/x/net | v0.55.0 | 0.62.0 | within 30 days |
| High | CVE-2026-78669 | golang.org/x/net | v0.55.0 | 0.60.0 | within 30 days |
| High | CVE-2026-111943 | stdlib | 1.26.4 | 1.26.10, 1.27.3 | within 30 days |
| High | CVE-2026-33818 | stdlib | 1.26.4 | 1.25.13, 1.26.6, 1.27.0-rc.3 | within 30 days |
| High | CVE-2026-39821 | stdlib | 1.26.4 | 1.25.13, 1.26.6, 1.27.0-rc.3 | within 30 days |
| High | CVE-2026-39822 | stdlib | 1.26.4 | 1.25.12, 1.26.5, 1.27.0-rc.2 | within 30 days |
| High | CVE-2026-46600 | stdlib | 1.26.4 | 1.26.6, 1.27.0-rc.3 | within 30 days |
| High | CVE-2026-56853 | stdlib | 1.26.4 | 1.25.13, 1.26.6, 1.27.0-rc.3 | within 30 days |
| High | CVE-2026-56858 | stdlib | 1.26.4 | 1.25.13, 1.26.6, 1.27.0-rc.3 | within 30 days |
| High | CVE-2026-56859 | stdlib | 1.26.4 | 1.25.13, 1.26.6, 1.27.0-rc.3 | within 30 days |
| High | CVE-2026-56860 | stdlib | 1.26.4 | 1.25.13, 1.26.6, 1.27.0-rc.3 | within 30 days |
| High | CVE-2026-56862 | stdlib | 1.26.4 | 1.25.13, 1.26.6, 1.27.0-rc.3 | within 30 days |
| High | CVE-2026-78667 | stdlib | 1.26.4 | 1.26.9, 1.27.2 | within 30 days |
| High | CVE-2026-78669 | stdlib | 1.26.4 | 1.26.9, 1.27.2 | within 30 days |
| High | CVE-2026-97031 | stdlib | 1.26.4 | 1.26.9, 1.27.2 | within 30 days |
| High | CVE-2026-26007 | cryptography | 43.0.0 | 46.0.5 | within 30 days |
| High | CVE-2026-69249 | cryptography | 43.0.0 | 49.0.0 | within 30 days |
| High | GHSA-537c-gmf6-5ccf | cryptography | 43.0.0 | 48.0.1 | within 30 days |
| High | CVE-2026-118669 | oauthlib | 3.2.2 | 4.0.0 | within 30 days |
| High | CVE-2026-102267 | pyjwt | 2.10.1 | 2.14.0 | within 30 days |
| High | CVE-2026-102271 | pyjwt | 2.10.1 | 2.14.0 | within 30 days |
| High | CVE-2026-32597 | pyjwt | 2.10.1 | 2.12.0 | within 30 days |
| High | CVE-2026-48526 | pyjwt | 2.10.1 | 2.13.0 | within 30 days |
| High | GHSA-pxh4-856f-4h89 | pyjwt | 2.10.1 | 2.14.0 | within 30 days |
| High | CVE-2025-66418 | urllib3 | 2.3.0 | 2.6.0 | within 30 days |
| High | CVE-2025-66471 | urllib3 | 2.3.0 | 2.6.0 | within 30 days |
| High | CVE-2026-21441 | urllib3 | 2.3.0 | 2.6.3 | within 30 days |
| High | CVE-2026-44431 | urllib3 | 2.3.0 | 2.7.0 | within 30 days |
| High | CVE-2026-97687 | urllib3 | 2.3.0 | 2.8.0 | within 30 days |
| High | CVE-2026-97689 | urllib3 | 2.3.0 | 2.8.0 | within 30 days |
| High | CVE-2026-24049 | wheel | 0.45.1 | 0.46.2 | within 30 days |
| High | CVE-2007-2764 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2008-4609 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2016-3699 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2017-6264 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2018-10902 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2019-14899 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2020-1749 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2020-25672 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2020-27815 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2021-20194 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2021-3864 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2022-0400 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2022-1247 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2023-3397 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2023-3640 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2023-39179 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2023-6610 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2025-71074 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2025-71289 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2025-71306 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-100072 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-23327 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-23459 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-31709 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-31771 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-43009 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-43042 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-43391 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-45945 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-45991 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-46054 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-46130 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-46203 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-46210 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-46311 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-46317 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-46320 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-46321 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-46322 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-46330 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-46331 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-52908 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-52909 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-52910 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-52917 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-52923 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-52927 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-52929 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-52932 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-52935 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-52942 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-52943 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-52946 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-52947 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-52956 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-52960 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-52988 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53005 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53009 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53024 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53025 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53070 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53078 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53089 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53090 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53091 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53132 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53133 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53136 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53137 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53138 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53143 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53145 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53146 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53147 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53148 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53149 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53153 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53156 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53157 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53159 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53160 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53161 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53162 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53178 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53179 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53180 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53182 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53183 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53184 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53185 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53187 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53188 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53189 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53191 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53192 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53193 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53194 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53195 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53198 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53199 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53202 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53203 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53205 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53209 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53212 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53217 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53223 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53229 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53230 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53232 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53233 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53234 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53235 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53239 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53240 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53242 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53248 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53250 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53253 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53254 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53255 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53256 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53259 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53262 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53264 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53265 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53266 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53267 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53268 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53270 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53272 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53273 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53275 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53277 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53329 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53330 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53341 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53346 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53354 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53356 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53358 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53359 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53360 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53361 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53362 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53366 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53381 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53383 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53386 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53387 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53388 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53389 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53390 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53391 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53392 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53394 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53397 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53400 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53401 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-53402 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63794 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63796 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63797 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63801 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63802 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63803 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63804 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63805 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63806 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63807 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63809 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63812 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63814 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63815 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63816 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63817 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63818 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63819 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63822 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63823 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63824 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63826 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63827 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63828 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63829 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63831 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63832 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63833 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63834 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63858 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63867 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63869 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63870 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63874 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63875 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63879 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63881 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63883 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63884 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63885 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63889 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63892 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63893 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63894 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63898 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63899 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63901 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63902 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63903 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63904 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63905 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63906 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63909 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63911 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63913 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63914 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63915 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63916 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63917 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63918 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63919 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63920 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63921 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63923 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63925 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63926 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63927 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63928 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63930 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63934 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63937 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63941 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63942 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63943 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63944 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63945 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63946 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63947 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63949 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63950 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63952 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63954 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63956 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63957 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63967 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63968 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63970 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63971 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63972 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63974 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63975 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63976 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63977 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63980 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63985 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63987 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63995 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-63996 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64001 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64002 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64003 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64004 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64005 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64008 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64009 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64010 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64011 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64014 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64017 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64020 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64026 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64057 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64082 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64117 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64123 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64124 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64188 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64189 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64191 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64206 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64210 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64222 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64235 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64237 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64239 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64242 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64243 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64245 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64246 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64247 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64249 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64251 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64255 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64259 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64260 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64261 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64265 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64266 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64270 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64271 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64272 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64273 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64274 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64276 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64277 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64279 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64280 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64283 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64284 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64286 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64287 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64293 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64296 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64298 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64299 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64300 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64304 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64305 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64311 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64312 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64313 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64315 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64317 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64318 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64322 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64323 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64324 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64329 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64330 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64333 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64339 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64340 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64341 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64342 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64343 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64344 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64346 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64348 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64352 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64354 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64361 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64362 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64363 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64364 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64365 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64366 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64367 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64368 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64372 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64374 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64375 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64377 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64378 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64379 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64380 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64381 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64382 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64388 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64389 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64390 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64394 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64395 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64396 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64398 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64400 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64401 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64402 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64403 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64406 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64407 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64408 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64411 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64412 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64413 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64414 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64418 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64420 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64421 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64422 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64423 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64424 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64430 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64432 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64433 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64435 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64436 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64438 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64440 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64441 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64442 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64443 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64444 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64445 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64446 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64447 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64448 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64449 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64452 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64453 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64455 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64456 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64460 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64463 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64467 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64468 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64469 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64470 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64471 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64475 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64477 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64481 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64485 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64487 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64490 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64491 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64495 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64496 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64501 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64502 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64510 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64524 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64529 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64531 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64532 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64533 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64536 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64539 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64540 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64543 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64544 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64545 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64546 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64547 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64548 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64549 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64550 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64552 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64554 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64555 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64556 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64557 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64558 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64559 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64560 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64561 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64562 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64563 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64565 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64567 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64568 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64570 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64571 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-64600 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-98050 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-98052 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-98056 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-98060 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-98066 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-98069 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-98070 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-98071 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-98073 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-98076 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-98077 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-98083 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-98088 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-98093 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-98096 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-98103 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-98107 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-98108 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-98110 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-98111 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-98115 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-98116 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-98117 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-98118 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-98122 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-98130 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-98154 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-98155 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-98156 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| High | CVE-2026-98164 | linux_kernel | 6.18.34 | No fix yet | within 30 days |
| Medium | CVE-2026-58052 | 7zip | 25.01+dfsg-1~deb13u2 | No fix yet | Per policy |
| Medium | CVE-2024-52615 | avahi-daemon | 0.8-16 | No fix yet | Per policy |
| Medium | CVE-2024-52616 | avahi-daemon | 0.8-16 | No fix yet | Per policy |
| Medium | CVE-2025-59529 | avahi-daemon | 0.8-16 | No fix yet | Per policy |
| Medium | CVE-2025-68276 | avahi-daemon | 0.8-16 | No fix yet | Per policy |
| Medium | CVE-2025-68468 | avahi-daemon | 0.8-16 | No fix yet | Per policy |
| Medium | CVE-2025-68471 | avahi-daemon | 0.8-16 | No fix yet | Per policy |
| Medium | CVE-2026-24401 | avahi-daemon | 0.8-16 | No fix yet | Per policy |
| Medium | CVE-2026-34933 | avahi-daemon | 0.8-16 | No fix yet | Per policy |
| Medium | CVE-2026-59987 | avahi-daemon | 0.8-16 | No fix yet | Per policy |
| Medium | CVE-2023-51580 | bluez | 5.82-1.1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-51589 | bluez | 5.82-1.1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-51592 | bluez | 5.82-1.1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-51594 | bluez | 5.82-1.1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-51596 | bluez | 5.82-1.1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-75032 | bluez | 5.82-1.1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80185 | bluez | 5.82-1.1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-13595 | bsdextrautils | 2.41-5 | 2.41.5-0+deb13u1 | Per policy |
| Medium | CVE-2026-27456 | bsdextrautils | 2.41-5 | 2.41.5-0+deb13u1 | Per policy |
| Medium | CVE-2026-3184 | bsdextrautils | 2.41-5 | No fix yet | Per policy |
| Medium | CVE-2026-13595 | bsdutils | 1:2.41-5 | 2.41.5-0+deb13u1 | Per policy |
| Medium | CVE-2026-27456 | bsdutils | 1:2.41-5 | 2.41.5-0+deb13u1 | Per policy |
| Medium | CVE-2026-3184 | bsdutils | 1:2.41-5 | No fix yet | Per policy |
| Medium | CVE-2023-42366 | busybox | 1:1.37.0-6+b8 | No fix yet | Per policy |
| Medium | CVE-2024-58251 | busybox | 1:1.37.0-6+b8 | No fix yet | Per policy |
| Medium | CVE-2026-108119 | busybox | 1:1.37.0-6+b8 | No fix yet | Per policy |
| Medium | CVE-2026-124738 | busybox | 1:1.37.0-6+b8 | No fix yet | Per policy |
| Medium | CVE-2026-124744 | busybox | 1:1.37.0-6+b8 | No fix yet | Per policy |
| Medium | CVE-2026-124745 | busybox | 1:1.37.0-6+b8 | No fix yet | Per policy |
| Medium | CVE-2026-38752 | busybox | 1:1.37.0-6+b8 | No fix yet | Per policy |
| Medium | CVE-2026-38753 | busybox | 1:1.37.0-6+b8 | No fix yet | Per policy |
| Medium | CVE-2026-38755 | busybox | 1:1.37.0-6+b8 | No fix yet | Per policy |
| Medium | CVE-2026-88829 | busybox | 1:1.37.0-6+b8 | No fix yet | Per policy |
| Medium | CVE-2026-88831 | busybox | 1:1.37.0-6+b8 | No fix yet | Per policy |
| Medium | CVE-2026-88833 | busybox | 1:1.37.0-6+b8 | No fix yet | Per policy |
| Medium | CVE-2026-88837 | busybox | 1:1.37.0-6+b8 | No fix yet | Per policy |
| Medium | CVE-2026-88838 | busybox | 1:1.37.0-6+b8 | No fix yet | Per policy |
| Medium | CVE-2026-88839 | busybox | 1:1.37.0-6+b8 | No fix yet | Per policy |
| Medium | CVE-2026-92205 | busybox | 1:1.37.0-6+b8 | No fix yet | Per policy |
| Medium | CVE-2026-42250 | bzip2 | 1.0.8-6 | No fix yet | Per policy |
| Medium | CVE-2026-66485 | cpio | 2.15+dfsg-2 | No fix yet | Per policy |
| Medium | CVE-2026-66486 | cpio | 2.15+dfsg-2 | No fix yet | Per policy |
| Medium | CVE-2026-102010 | cpp-14 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-114690 | cpp-14 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-114691 | cpp-14 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-115455 | cpp-14 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-125709 | cpp-14 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-95619 | cpp-14 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-102010 | cpp-14-aarch64-linux-gnu | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-114690 | cpp-14-aarch64-linux-gnu | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-114691 | cpp-14-aarch64-linux-gnu | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-115455 | cpp-14-aarch64-linux-gnu | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-125709 | cpp-14-aarch64-linux-gnu | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-95619 | cpp-14-aarch64-linux-gnu | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-102010 | cpp-14-for-host | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-114690 | cpp-14-for-host | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-114691 | cpp-14-for-host | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-115455 | cpp-14-for-host | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-125709 | cpp-14-for-host | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-95619 | cpp-14-for-host | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-10536 | curl | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Medium | CVE-2026-11856 | curl | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Medium | CVE-2026-1965 | curl | 8.14.1-2+deb13u3 | 8.14.1-2+deb13u4 | Per policy |
| Medium | CVE-2026-19931 | curl | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Medium | CVE-2026-3783 | curl | 8.14.1-2+deb13u3 | 8.14.1-2+deb13u4 | Per policy |
| Medium | CVE-2026-3784 | curl | 8.14.1-2+deb13u3 | 8.14.1-2+deb13u4 | Per policy |
| Medium | CVE-2026-3805 | curl | 8.14.1-2+deb13u3 | 8.14.1-2+deb13u4 | Per policy |
| Medium | CVE-2026-4873 | curl | 8.14.1-2+deb13u3 | 8.14.1-2+deb13u4 | Per policy |
| Medium | CVE-2026-5545 | curl | 8.14.1-2+deb13u3 | 8.14.1-2+deb13u4 | Per policy |
| Medium | CVE-2026-6253 | curl | 8.14.1-2+deb13u3 | 8.14.1-2+deb13u4 | Per policy |
| Medium | CVE-2026-6429 | curl | 8.14.1-2+deb13u3 | 8.14.1-2+deb13u4 | Per policy |
| Medium | CVE-2026-7168 | curl | 8.14.1-2+deb13u3 | 8.14.1-2+deb13u4 | Per policy |
| Medium | CVE-2026-8924 | curl | 8.14.1-2+deb13u3 | 8.14.1-2+deb13u7 | Per policy |
| Medium | CVE-2026-8926 | curl | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Medium | CVE-2026-8932 | curl | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Medium | CVE-2026-9079 | curl | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Medium | CVE-2026-9080 | curl | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Medium | CVE-2026-92388 | curl | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Medium | CVE-2026-9545 | curl | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Medium | CVE-2026-120749 | dbus | 1.16.2-2 | No fix yet | Per policy |
| Medium | CVE-2026-128886 | dbus | 1.16.2-2 | No fix yet | Per policy |
| Medium | CVE-2026-128987 | dbus | 1.16.2-2 | No fix yet | Per policy |
| Medium | CVE-2026-120749 | dbus-bin | 1.16.2-2 | No fix yet | Per policy |
| Medium | CVE-2026-128886 | dbus-bin | 1.16.2-2 | No fix yet | Per policy |
| Medium | CVE-2026-128987 | dbus-bin | 1.16.2-2 | No fix yet | Per policy |
| Medium | CVE-2026-120749 | dbus-daemon | 1.16.2-2 | No fix yet | Per policy |
| Medium | CVE-2026-128886 | dbus-daemon | 1.16.2-2 | No fix yet | Per policy |
| Medium | CVE-2026-128987 | dbus-daemon | 1.16.2-2 | No fix yet | Per policy |
| Medium | CVE-2026-120749 | dbus-session-bus-common | 1.16.2-2 | No fix yet | Per policy |
| Medium | CVE-2026-128886 | dbus-session-bus-common | 1.16.2-2 | No fix yet | Per policy |
| Medium | CVE-2026-128987 | dbus-session-bus-common | 1.16.2-2 | No fix yet | Per policy |
| Medium | CVE-2026-120749 | dbus-system-bus-common | 1.16.2-2 | No fix yet | Per policy |
| Medium | CVE-2026-128886 | dbus-system-bus-common | 1.16.2-2 | No fix yet | Per policy |
| Medium | CVE-2026-128987 | dbus-system-bus-common | 1.16.2-2 | No fix yet | Per policy |
| Medium | CVE-2026-120749 | dbus-user-session | 1.16.2-2 | No fix yet | Per policy |
| Medium | CVE-2026-128886 | dbus-user-session | 1.16.2-2 | No fix yet | Per policy |
| Medium | CVE-2026-128987 | dbus-user-session | 1.16.2-2 | No fix yet | Per policy |
| Medium | CVE-2025-70102 | dhcpcd-base | 1:10.1.0-11+deb13u2 | 1:10.1.0-11+deb13u3 | Per policy |
| Medium | CVE-2026-14258 | dhcpcd-base | 1:10.1.0-11+deb13u2 | 1:10.1.0-11+deb13u4 | Per policy |
| Medium | CVE-2026-56113 | dhcpcd-base | 1:10.1.0-11+deb13u2 | 1:10.1.0-11+deb13u3 | Per policy |
| Medium | CVE-2026-56114 | dhcpcd-base | 1:10.1.0-11+deb13u2 | 1:10.1.0-11+deb13u3 | Per policy |
| Medium | CVE-2026-56116 | dhcpcd-base | 1:10.1.0-11+deb13u2 | 1:10.1.0-11+deb13u3 | Per policy |
| Medium | CVE-2026-56117 | dhcpcd-base | 1:10.1.0-11+deb13u2 | 1:10.1.0-11+deb13u3 | Per policy |
| Medium | CVE-2025-68972 | dirmngr | 2.4.7-21+deb13u1+b3 | No fix yet | Per policy |
| Medium | CVE-2026-12725 | dnsmasq-base | 2.91-1+deb13u1 | 2.91-1+deb13u2 | Per policy |
| Medium | CVE-2026-93007 | dnsmasq-base | 2.91-1+deb13u1 | No fix yet | Per policy |
| Medium | CVE-2026-93011 | dnsmasq-base | 2.91-1+deb13u1 | No fix yet | Per policy |
| Medium | CVE-2026-13595 | eject | 2.41-5 | 2.41.5-0+deb13u1 | Per policy |
| Medium | CVE-2026-27456 | eject | 2.41-5 | 2.41.5-0+deb13u1 | Per policy |
| Medium | CVE-2026-3184 | eject | 2.41-5 | No fix yet | Per policy |
| Medium | CVE-2026-13595 | fdisk | 2.41-5 | 2.41.5-0+deb13u1 | Per policy |
| Medium | CVE-2026-27456 | fdisk | 2.41-5 | 2.41.5-0+deb13u1 | Per policy |
| Medium | CVE-2026-3184 | fdisk | 2.41-5 | No fix yet | Per policy |
| Medium | CVE-2026-20731 | firmware-atheros | 1:20250410-2+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-20769 | firmware-atheros | 1:20250410-2+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-20783 | firmware-atheros | 1:20250410-2+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-20786 | firmware-atheros | 1:20250410-2+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-20731 | firmware-brcm80211 | 1:20250410-2+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-20769 | firmware-brcm80211 | 1:20250410-2+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-20783 | firmware-brcm80211 | 1:20250410-2+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-20786 | firmware-brcm80211 | 1:20250410-2+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-20731 | firmware-libertas | 1:20250410-2+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-20769 | firmware-libertas | 1:20250410-2+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-20783 | firmware-libertas | 1:20250410-2+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-20786 | firmware-libertas | 1:20250410-2+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-20731 | firmware-mediatek | 1:20250410-2+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-20769 | firmware-mediatek | 1:20250410-2+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-20783 | firmware-mediatek | 1:20250410-2+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-20786 | firmware-mediatek | 1:20250410-2+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-20731 | firmware-realtek | 1:20250410-2+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-20769 | firmware-realtek | 1:20250410-2+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-20783 | firmware-realtek | 1:20250410-2+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-20786 | firmware-realtek | 1:20250410-2+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-102010 | g++-14 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-114690 | g++-14 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-114691 | g++-14 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-115455 | g++-14 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-125709 | g++-14 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-95619 | g++-14 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-102010 | g++-14-aarch64-linux-gnu | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-114690 | g++-14-aarch64-linux-gnu | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-114691 | g++-14-aarch64-linux-gnu | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-115455 | g++-14-aarch64-linux-gnu | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-125709 | g++-14-aarch64-linux-gnu | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-95619 | g++-14-aarch64-linux-gnu | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-102010 | gcc-14 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-114690 | gcc-14 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-114691 | gcc-14 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-115455 | gcc-14 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-125709 | gcc-14 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-95619 | gcc-14 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-102010 | gcc-14-aarch64-linux-gnu | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-114690 | gcc-14-aarch64-linux-gnu | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-114691 | gcc-14-aarch64-linux-gnu | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-115455 | gcc-14-aarch64-linux-gnu | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-125709 | gcc-14-aarch64-linux-gnu | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-95619 | gcc-14-aarch64-linux-gnu | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-102010 | gcc-14-base | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-114690 | gcc-14-base | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-114691 | gcc-14-base | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-115455 | gcc-14-base | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-125709 | gcc-14-base | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-95619 | gcc-14-base | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-102010 | gcc-14-for-host | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-114690 | gcc-14-for-host | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-114691 | gcc-14-for-host | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-115455 | gcc-14-for-host | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-125709 | gcc-14-for-host | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-95619 | gcc-14-for-host | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2025-68972 | gnupg | 2.4.7-21+deb13u1 | No fix yet | Per policy |
| Medium | CVE-2025-68972 | gnupg-l10n | 2.4.7-21+deb13u1 | No fix yet | Per policy |
| Medium | CVE-2025-68972 | gnupg-utils | 2.4.7-21+deb13u1+b3 | No fix yet | Per policy |
| Medium | CVE-2025-68972 | gpg | 2.4.7-21+deb13u1+b3 | No fix yet | Per policy |
| Medium | CVE-2025-68972 | gpg-agent | 2.4.7-21+deb13u1+b3 | No fix yet | Per policy |
| Medium | CVE-2025-68972 | gpg-wks-client | 2.4.7-21+deb13u1+b3 | No fix yet | Per policy |
| Medium | CVE-2025-68972 | gpgconf | 2.4.7-21+deb13u1+b3 | No fix yet | Per policy |
| Medium | CVE-2025-68972 | gpgsm | 2.4.7-21+deb13u1+b3 | No fix yet | Per policy |
| Medium | CVE-2025-68972 | gpgv | 2.4.7-21+deb13u1+b3 | No fix yet | Per policy |
| Medium | CVE-2026-41991 | gzip | 1.13-1 | 1.13-1+deb13u1 | Per policy |
| Medium | CVE-2026-72693 | kbd | 2.7.1-2 | No fix yet | Per policy |
| Medium | CVE-2026-54370 | libacl1 | 2.3.2-2+b1 | No fix yet | Per policy |
| Medium | CVE-2026-102010 | libasan8 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-114690 | libasan8 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-114691 | libasan8 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-115455 | libasan8 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-125709 | libasan8 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-95619 | libasan8 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-90781 | libasound2-data | 1.2.14-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-96674 | libasound2-data | 1.2.14-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-96675 | libasound2-data | 1.2.14-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90781 | libasound2t64 | 1.2.14-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-96674 | libasound2t64 | 1.2.14-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-96675 | libasound2t64 | 1.2.14-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-102010 | libatomic1 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-114690 | libatomic1 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-114691 | libatomic1 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-115455 | libatomic1 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-125709 | libatomic1 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-95619 | libatomic1 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-90781 | libatopology2t64 | 1.2.14-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-96674 | libatopology2t64 | 1.2.14-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-96675 | libatopology2t64 | 1.2.14-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-54371 | libattr1 | 1:2.5.2-3 | No fix yet | Per policy |
| Medium | CVE-2024-52615 | libavahi-common-data | 0.8-16 | No fix yet | Per policy |
| Medium | CVE-2024-52616 | libavahi-common-data | 0.8-16 | No fix yet | Per policy |
| Medium | CVE-2025-59529 | libavahi-common-data | 0.8-16 | No fix yet | Per policy |
| Medium | CVE-2025-68276 | libavahi-common-data | 0.8-16 | No fix yet | Per policy |
| Medium | CVE-2025-68468 | libavahi-common-data | 0.8-16 | No fix yet | Per policy |
| Medium | CVE-2025-68471 | libavahi-common-data | 0.8-16 | No fix yet | Per policy |
| Medium | CVE-2026-24401 | libavahi-common-data | 0.8-16 | No fix yet | Per policy |
| Medium | CVE-2026-34933 | libavahi-common-data | 0.8-16 | No fix yet | Per policy |
| Medium | CVE-2026-59987 | libavahi-common-data | 0.8-16 | No fix yet | Per policy |
| Medium | CVE-2024-52615 | libavahi-common3 | 0.8-16 | No fix yet | Per policy |
| Medium | CVE-2024-52616 | libavahi-common3 | 0.8-16 | No fix yet | Per policy |
| Medium | CVE-2025-59529 | libavahi-common3 | 0.8-16 | No fix yet | Per policy |
| Medium | CVE-2025-68276 | libavahi-common3 | 0.8-16 | No fix yet | Per policy |
| Medium | CVE-2025-68468 | libavahi-common3 | 0.8-16 | No fix yet | Per policy |
| Medium | CVE-2025-68471 | libavahi-common3 | 0.8-16 | No fix yet | Per policy |
| Medium | CVE-2026-24401 | libavahi-common3 | 0.8-16 | No fix yet | Per policy |
| Medium | CVE-2026-34933 | libavahi-common3 | 0.8-16 | No fix yet | Per policy |
| Medium | CVE-2026-59987 | libavahi-common3 | 0.8-16 | No fix yet | Per policy |
| Medium | CVE-2024-52615 | libavahi-core7 | 0.8-16 | No fix yet | Per policy |
| Medium | CVE-2024-52616 | libavahi-core7 | 0.8-16 | No fix yet | Per policy |
| Medium | CVE-2025-59529 | libavahi-core7 | 0.8-16 | No fix yet | Per policy |
| Medium | CVE-2025-68276 | libavahi-core7 | 0.8-16 | No fix yet | Per policy |
| Medium | CVE-2025-68468 | libavahi-core7 | 0.8-16 | No fix yet | Per policy |
| Medium | CVE-2025-68471 | libavahi-core7 | 0.8-16 | No fix yet | Per policy |
| Medium | CVE-2026-24401 | libavahi-core7 | 0.8-16 | No fix yet | Per policy |
| Medium | CVE-2026-34933 | libavahi-core7 | 0.8-16 | No fix yet | Per policy |
| Medium | CVE-2026-59987 | libavahi-core7 | 0.8-16 | No fix yet | Per policy |
| Medium | CVE-2026-13595 | libblkid1 | 2.41-5 | 2.41.5-0+deb13u1 | Per policy |
| Medium | CVE-2026-27456 | libblkid1 | 2.41-5 | 2.41.5-0+deb13u1 | Per policy |
| Medium | CVE-2026-3184 | libblkid1 | 2.41-5 | No fix yet | Per policy |
| Medium | CVE-2023-51580 | libbluetooth3 | 5.82-1.1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-51589 | libbluetooth3 | 5.82-1.1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-51592 | libbluetooth3 | 5.82-1.1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-51594 | libbluetooth3 | 5.82-1.1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-51596 | libbluetooth3 | 5.82-1.1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-75032 | libbluetooth3 | 5.82-1.1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80185 | libbluetooth3 | 5.82-1.1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-42250 | libbz2-1.0 | 1.0.8-6 | No fix yet | Per policy |
| Medium | CVE-2026-115819 | libc-bin | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Medium | CVE-2026-84243 | libc-bin | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Medium | CVE-2026-115819 | libc-dev-bin | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Medium | CVE-2026-84243 | libc-dev-bin | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Medium | CVE-2026-115819 | libc-l10n | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Medium | CVE-2026-84243 | libc-l10n | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Medium | CVE-2026-115819 | libc6 | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Medium | CVE-2026-84243 | libc6 | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Medium | CVE-2026-115819 | libc6-dev | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Medium | CVE-2026-84243 | libc6-dev | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Medium | CVE-2026-102010 | libcc1-0 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-114690 | libcc1-0 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-114691 | libcc1-0 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-115455 | libcc1-0 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-125709 | libcc1-0 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-95619 | libcc1-0 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-10536 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Medium | CVE-2026-11856 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Medium | CVE-2026-1965 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | 8.14.1-2+deb13u4 | Per policy |
| Medium | CVE-2026-19931 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Medium | CVE-2026-3783 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | 8.14.1-2+deb13u4 | Per policy |
| Medium | CVE-2026-3784 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | 8.14.1-2+deb13u4 | Per policy |
| Medium | CVE-2026-3805 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | 8.14.1-2+deb13u4 | Per policy |
| Medium | CVE-2026-4873 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | 8.14.1-2+deb13u4 | Per policy |
| Medium | CVE-2026-5545 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | 8.14.1-2+deb13u4 | Per policy |
| Medium | CVE-2026-6253 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | 8.14.1-2+deb13u4 | Per policy |
| Medium | CVE-2026-6429 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | 8.14.1-2+deb13u4 | Per policy |
| Medium | CVE-2026-7168 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | 8.14.1-2+deb13u4 | Per policy |
| Medium | CVE-2026-8924 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | 8.14.1-2+deb13u7 | Per policy |
| Medium | CVE-2026-8926 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Medium | CVE-2026-8932 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Medium | CVE-2026-9079 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Medium | CVE-2026-9080 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Medium | CVE-2026-92388 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Medium | CVE-2026-9545 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Medium | CVE-2026-10536 | libcurl4t64 | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Medium | CVE-2026-11856 | libcurl4t64 | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Medium | CVE-2026-1965 | libcurl4t64 | 8.14.1-2+deb13u3 | 8.14.1-2+deb13u4 | Per policy |
| Medium | CVE-2026-19931 | libcurl4t64 | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Medium | CVE-2026-3783 | libcurl4t64 | 8.14.1-2+deb13u3 | 8.14.1-2+deb13u4 | Per policy |
| Medium | CVE-2026-3784 | libcurl4t64 | 8.14.1-2+deb13u3 | 8.14.1-2+deb13u4 | Per policy |
| Medium | CVE-2026-3805 | libcurl4t64 | 8.14.1-2+deb13u3 | 8.14.1-2+deb13u4 | Per policy |
| Medium | CVE-2026-4873 | libcurl4t64 | 8.14.1-2+deb13u3 | 8.14.1-2+deb13u4 | Per policy |
| Medium | CVE-2026-5545 | libcurl4t64 | 8.14.1-2+deb13u3 | 8.14.1-2+deb13u4 | Per policy |
| Medium | CVE-2026-6253 | libcurl4t64 | 8.14.1-2+deb13u3 | 8.14.1-2+deb13u4 | Per policy |
| Medium | CVE-2026-6429 | libcurl4t64 | 8.14.1-2+deb13u3 | 8.14.1-2+deb13u4 | Per policy |
| Medium | CVE-2026-7168 | libcurl4t64 | 8.14.1-2+deb13u3 | 8.14.1-2+deb13u4 | Per policy |
| Medium | CVE-2026-8924 | libcurl4t64 | 8.14.1-2+deb13u3 | 8.14.1-2+deb13u7 | Per policy |
| Medium | CVE-2026-8926 | libcurl4t64 | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Medium | CVE-2026-8932 | libcurl4t64 | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Medium | CVE-2026-9079 | libcurl4t64 | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Medium | CVE-2026-9080 | libcurl4t64 | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Medium | CVE-2026-92388 | libcurl4t64 | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Medium | CVE-2026-9545 | libcurl4t64 | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Medium | CVE-2026-120749 | libdbus-1-3 | 1.16.2-2 | No fix yet | Per policy |
| Medium | CVE-2026-128886 | libdbus-1-3 | 1.16.2-2 | No fix yet | Per policy |
| Medium | CVE-2026-128987 | libdbus-1-3 | 1.16.2-2 | No fix yet | Per policy |
| Medium | CVE-2026-12216 | libduktape207 | 2.7.0-2+b2 | No fix yet | Per policy |
| Medium | CVE-2025-66382 | libexpat1 | 2.7.1-2 | No fix yet | Per policy |
| Medium | CVE-2026-102633 | libexpat1 | 2.7.1-2 | 2.9.0-1~deb13u1 | Per policy |
| Medium | CVE-2026-32776 | libexpat1 | 2.7.1-2 | 2.8.2-1~deb13u1 | Per policy |
| Medium | CVE-2026-32777 | libexpat1 | 2.7.1-2 | 2.8.2-1~deb13u1 | Per policy |
| Medium | CVE-2026-32778 | libexpat1 | 2.7.1-2 | 2.8.2-1~deb13u1 | Per policy |
| Medium | CVE-2026-50219 | libexpat1 | 2.7.1-2 | 2.8.2-1~deb13u1 | Per policy |
| Medium | CVE-2026-56131 | libexpat1 | 2.7.1-2 | 2.8.2-1~deb13u1 | Per policy |
| Medium | CVE-2026-56132 | libexpat1 | 2.7.1-2 | 2.8.2-1~deb13u1 | Per policy |
| Medium | CVE-2026-56403 | libexpat1 | 2.7.1-2 | 2.8.2-1~deb13u1 | Per policy |
| Medium | CVE-2026-56404 | libexpat1 | 2.7.1-2 | 2.8.2-1~deb13u1 | Per policy |
| Medium | CVE-2026-56405 | libexpat1 | 2.7.1-2 | 2.8.2-1~deb13u1 | Per policy |
| Medium | CVE-2026-56406 | libexpat1 | 2.7.1-2 | 2.8.2-1~deb13u1 | Per policy |
| Medium | CVE-2026-56407 | libexpat1 | 2.7.1-2 | 2.8.2-1~deb13u1 | Per policy |
| Medium | CVE-2026-56408 | libexpat1 | 2.7.1-2 | 2.8.2-1~deb13u1 | Per policy |
| Medium | CVE-2026-56409 | libexpat1 | 2.7.1-2 | 2.8.2-1~deb13u1 | Per policy |
| Medium | CVE-2026-56410 | libexpat1 | 2.7.1-2 | 2.8.2-1~deb13u1 | Per policy |
| Medium | CVE-2026-56411 | libexpat1 | 2.7.1-2 | 2.8.2-1~deb13u1 | Per policy |
| Medium | CVE-2026-56412 | libexpat1 | 2.7.1-2 | 2.8.2-1~deb13u1 | Per policy |
| Medium | CVE-2026-72522 | libexpat1 | 2.7.1-2 | 2.8.3-1~deb13u1 | Per policy |
| Medium | CVE-2026-13595 | libfdisk1 | 2.41-5 | 2.41.5-0+deb13u1 | Per policy |
| Medium | CVE-2026-27456 | libfdisk1 | 2.41-5 | 2.41.5-0+deb13u1 | Per policy |
| Medium | CVE-2026-3184 | libfdisk1 | 2.41-5 | No fix yet | Per policy |
| Medium | CVE-2026-132199 | libflac14 | 1.5.0+ds-2 | No fix yet | Per policy |
| Medium | CVE-2026-132857 | libflac14 | 1.5.0+ds-2 | No fix yet | Per policy |
| Medium | CVE-2026-102010 | libgcc-14-dev | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-114690 | libgcc-14-dev | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-114691 | libgcc-14-dev | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-115455 | libgcc-14-dev | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-125709 | libgcc-14-dev | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-95619 | libgcc-14-dev | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-102010 | libgcc-s1 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-114690 | libgcc-s1 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-114691 | libgcc-s1 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-115455 | libgcc-s1 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-125709 | libgcc-s1 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-95619 | libgcc-s1 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-15588 | libglib2.0-0t64 | 2.84.4-3~deb13u3 | 2.84.4-3~deb13u4 | Per policy |
| Medium | CVE-2026-16118 | libglib2.0-0t64 | 2.84.4-3~deb13u3 | 2.84.4-3~deb13u5 | Per policy |
| Medium | CVE-2026-86469 | libglib2.0-0t64 | 2.84.4-3~deb13u3 | No fix yet | Per policy |
| Medium | CVE-2026-15588 | libglib2.0-data | 2.84.4-3~deb13u3 | 2.84.4-3~deb13u4 | Per policy |
| Medium | CVE-2026-16118 | libglib2.0-data | 2.84.4-3~deb13u3 | 2.84.4-3~deb13u5 | Per policy |
| Medium | CVE-2026-86469 | libglib2.0-data | 2.84.4-3~deb13u3 | No fix yet | Per policy |
| Medium | CVE-2026-102010 | libgomp1 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-114690 | libgomp1 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-114691 | libgomp1 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-115455 | libgomp1 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-125709 | libgomp1 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-95619 | libgomp1 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-107708 | libgssapi-krb5-2 | 1.21.3-5+deb13u1 | No fix yet | Per policy |
| Medium | CVE-2026-107778 | libgssapi-krb5-2 | 1.21.3-5+deb13u1 | No fix yet | Per policy |
| Medium | CVE-2026-107884 | libgssapi-krb5-2 | 1.21.3-5+deb13u1 | No fix yet | Per policy |
| Medium | CVE-2026-111423 | libgssapi-krb5-2 | 1.21.3-5+deb13u1 | No fix yet | Per policy |
| Medium | CVE-2026-112314 | libgssapi-krb5-2 | 1.21.3-5+deb13u1 | No fix yet | Per policy |
| Medium | CVE-2026-102010 | libhwasan0 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-114690 | libhwasan0 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-114691 | libhwasan0 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-115455 | libhwasan0 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-125709 | libhwasan0 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-95619 | libhwasan0 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-102010 | libitm1 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-114690 | libitm1 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-114691 | libitm1 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-115455 | libitm1 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-125709 | libitm1 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-95619 | libitm1 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-107708 | libk5crypto3 | 1.21.3-5+deb13u1 | No fix yet | Per policy |
| Medium | CVE-2026-107778 | libk5crypto3 | 1.21.3-5+deb13u1 | No fix yet | Per policy |
| Medium | CVE-2026-107884 | libk5crypto3 | 1.21.3-5+deb13u1 | No fix yet | Per policy |
| Medium | CVE-2026-111423 | libk5crypto3 | 1.21.3-5+deb13u1 | No fix yet | Per policy |
| Medium | CVE-2026-112314 | libk5crypto3 | 1.21.3-5+deb13u1 | No fix yet | Per policy |
| Medium | CVE-2026-107708 | libkrb5-3 | 1.21.3-5+deb13u1 | No fix yet | Per policy |
| Medium | CVE-2026-107778 | libkrb5-3 | 1.21.3-5+deb13u1 | No fix yet | Per policy |
| Medium | CVE-2026-107884 | libkrb5-3 | 1.21.3-5+deb13u1 | No fix yet | Per policy |
| Medium | CVE-2026-111423 | libkrb5-3 | 1.21.3-5+deb13u1 | No fix yet | Per policy |
| Medium | CVE-2026-112314 | libkrb5-3 | 1.21.3-5+deb13u1 | No fix yet | Per policy |
| Medium | CVE-2026-107708 | libkrb5support0 | 1.21.3-5+deb13u1 | No fix yet | Per policy |
| Medium | CVE-2026-107778 | libkrb5support0 | 1.21.3-5+deb13u1 | No fix yet | Per policy |
| Medium | CVE-2026-107884 | libkrb5support0 | 1.21.3-5+deb13u1 | No fix yet | Per policy |
| Medium | CVE-2026-111423 | libkrb5support0 | 1.21.3-5+deb13u1 | No fix yet | Per policy |
| Medium | CVE-2026-112314 | libkrb5support0 | 1.21.3-5+deb13u1 | No fix yet | Per policy |
| Medium | CVE-2026-13595 | liblastlog2-2 | 2.41-5 | 2.41.5-0+deb13u1 | Per policy |
| Medium | CVE-2026-27456 | liblastlog2-2 | 2.41-5 | 2.41.5-0+deb13u1 | Per policy |
| Medium | CVE-2026-3184 | liblastlog2-2 | 2.41-5 | No fix yet | Per policy |
| Medium | CVE-2026-102010 | liblsan0 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-114690 | liblsan0 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-114691 | liblsan0 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-115455 | liblsan0 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-125709 | liblsan0 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-95619 | liblsan0 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-34743 | liblzma5 | 5.8.1-1 | 5.8.1-1+deb13u1 | Per policy |
| Medium | CVE-2026-95622 | libmm-glib0 | 1.24.0-1+deb13u1 | No fix yet | Per policy |
| Medium | CVE-2026-13595 | libmount1 | 2.41-5 | 2.41.5-0+deb13u1 | Per policy |
| Medium | CVE-2026-27456 | libmount1 | 2.41-5 | 2.41.5-0+deb13u1 | Per policy |
| Medium | CVE-2026-3184 | libmount1 | 2.41-5 | No fix yet | Per policy |
| Medium | CVE-2026-58055 | libnghttp2-14 | 1.64.0-1.1+deb13u1 | 1.64.0-1.1+deb13u2 | Per policy |
| Medium | CVE-2026-10805 | libnm0 | 1.52.1-1+rpt4 | No fix yet | Per policy |
| Medium | CVE-2026-16389 | libnss3 | 2:3.110-1+deb13u2 | 2:3.110-1+deb13u4 | Per policy |
| Medium | CVE-2026-46571 | libntfs-3g89t64 | 1:2022.10.3-5+deb13u1 | 1:2022.10.3-5+deb13u2 | Per policy |
| Medium | CVE-2026-56136 | libntfs-3g89t64 | 1:2022.10.3-5+deb13u1 | 1:2022.10.3-5+deb13u2 | Per policy |
| Medium | CVE-2026-13757 | libp11-kit0 | 0.25.5-3 | No fix yet | Per policy |
| Medium | CVE-2026-18938 | libp11-kit0 | 0.25.5-3 | No fix yet | Per policy |
| Medium | CVE-2026-54411 | libpam-modules | 1.7.0-5 | No fix yet | Per policy |
| Medium | CVE-2026-54411 | libpam-modules-bin | 1.7.0-5 | No fix yet | Per policy |
| Medium | CVE-2026-54411 | libpam-runtime | 1.7.0-5 | No fix yet | Per policy |
| Medium | CVE-2026-15059 | libpam-systemd | 257.13-1~deb13u1 | No fix yet | Per policy |
| Medium | CVE-2026-54411 | libpam0g | 1.7.0-5 | No fix yet | Per policy |
| Medium | CVE-2026-89085 | libparted2t64 | 3.6-5 | 3.6-5+deb13u1 | Per policy |
| Medium | CVE-2026-89088 | libparted2t64 | 3.6-5 | 3.6-5+deb13u1 | Per policy |
| Medium | CVE-2026-31911 | libpcap0.8t64 | 1.10.5-2 | No fix yet | Per policy |
| Medium | CVE-2026-31912 | libpcap0.8t64 | 1.10.5-2 | No fix yet | Per policy |
| Medium | CVE-2026-6244 | libpcap0.8t64 | 1.10.5-2 | No fix yet | Per policy |
| Medium | CVE-2026-89156 | libpcre2-16-0 | 10.46-1~deb13u1 | 10.46-1~deb13u2 | Per policy |
| Medium | CVE-2026-89158 | libpcre2-16-0 | 10.46-1~deb13u1 | 10.46-1~deb13u2 | Per policy |
| Medium | CVE-2026-89160 | libpcre2-16-0 | 10.46-1~deb13u1 | 10.46-1~deb13u2 | Per policy |
| Medium | CVE-2026-89156 | libpcre2-8-0 | 10.46-1~deb13u1 | 10.46-1~deb13u2 | Per policy |
| Medium | CVE-2026-89158 | libpcre2-8-0 | 10.46-1~deb13u1 | 10.46-1~deb13u2 | Per policy |
| Medium | CVE-2026-89160 | libpcre2-8-0 | 10.46-1~deb13u1 | 10.46-1~deb13u2 | Per policy |
| Medium | CVE-2025-15649 | libperl5.40 | 5.40.1-6 | 5.40.1-6+deb13u1 | Per policy |
| Medium | CVE-2026-12087 | libperl5.40 | 5.40.1-6 | 5.40.1-6+deb13u1 | Per policy |
| Medium | CVE-2026-15534 | libperl5.40 | 5.40.1-6 | No fix yet | Per policy |
| Medium | CVE-2026-19487 | libperl5.40 | 5.40.1-6 | 5.40.1-6+deb13u1 | Per policy |
| Medium | CVE-2026-48959 | libperl5.40 | 5.40.1-6 | 5.40.1-6+deb13u1 | Per policy |
| Medium | CVE-2026-48961 | libperl5.40 | 5.40.1-6 | 5.40.1-6+deb13u1 | Per policy |
| Medium | CVE-2026-7010 | libperl5.40 | 5.40.1-6 | 5.40.1-6+deb13u1 | Per policy |
| Medium | CVE-2026-7017 | libperl5.40 | 5.40.1-6 | 5.40.1-6+deb13u1 | Per policy |
| Medium | CVE-2026-82560 | libperl5.40 | 5.40.1-6 | No fix yet | Per policy |
| Medium | CVE-2026-46675 | libpng16-16t64 | 1.6.48-1+deb13u5 | 1.6.48-1+deb13u6 | Per policy |
| Medium | CVE-2026-4897 | libpolkit-agent-1-0 | 126-2 | No fix yet | Per policy |
| Medium | CVE-2026-4897 | libpolkit-gobject-1-0 | 126-2 | No fix yet | Per policy |
| Medium | CVE-2025-12781 | libpython3.13 | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2025-15366 | libpython3.13 | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2025-15367 | libpython3.13 | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-0864 | libpython3.13 | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u5 | Per policy |
| Medium | CVE-2026-103995 | libpython3.13 | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-114583 | libpython3.13 | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-116566 | libpython3.13 | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-11972 | libpython3.13 | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u5 | Per policy |
| Medium | CVE-2026-12345 | libpython3.13 | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-124249 | libpython3.13 | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-1502 | libpython3.13 | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u3 | Per policy |
| Medium | CVE-2026-15310 | libpython3.13 | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-15806 | libpython3.13 | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-16052 | libpython3.13 | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-17084 | libpython3.13 | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-19672 | libpython3.13 | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-3276 | libpython3.13 | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u3 | Per policy |
| Medium | CVE-2026-4360 | libpython3.13 | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u5 | Per policy |
| Medium | CVE-2026-7774 | libpython3.13 | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u3 | Per policy |
| Medium | CVE-2026-87910 | libpython3.13 | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-9669 | libpython3.13 | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u3 | Per policy |
| Medium | CVE-2025-12781 | libpython3.13-minimal | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2025-15366 | libpython3.13-minimal | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2025-15367 | libpython3.13-minimal | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-0864 | libpython3.13-minimal | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u5 | Per policy |
| Medium | CVE-2026-103995 | libpython3.13-minimal | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-114583 | libpython3.13-minimal | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-116566 | libpython3.13-minimal | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-11972 | libpython3.13-minimal | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u5 | Per policy |
| Medium | CVE-2026-12345 | libpython3.13-minimal | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-124249 | libpython3.13-minimal | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-1502 | libpython3.13-minimal | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u3 | Per policy |
| Medium | CVE-2026-15310 | libpython3.13-minimal | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-15806 | libpython3.13-minimal | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-16052 | libpython3.13-minimal | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-17084 | libpython3.13-minimal | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-19672 | libpython3.13-minimal | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-3276 | libpython3.13-minimal | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u3 | Per policy |
| Medium | CVE-2026-4360 | libpython3.13-minimal | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u5 | Per policy |
| Medium | CVE-2026-7774 | libpython3.13-minimal | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u3 | Per policy |
| Medium | CVE-2026-87910 | libpython3.13-minimal | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-9669 | libpython3.13-minimal | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u3 | Per policy |
| Medium | CVE-2025-12781 | libpython3.13-stdlib | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2025-15366 | libpython3.13-stdlib | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2025-15367 | libpython3.13-stdlib | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-0864 | libpython3.13-stdlib | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u5 | Per policy |
| Medium | CVE-2026-103995 | libpython3.13-stdlib | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-114583 | libpython3.13-stdlib | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-116566 | libpython3.13-stdlib | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-11972 | libpython3.13-stdlib | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u5 | Per policy |
| Medium | CVE-2026-12345 | libpython3.13-stdlib | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-124249 | libpython3.13-stdlib | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-1502 | libpython3.13-stdlib | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u3 | Per policy |
| Medium | CVE-2026-15310 | libpython3.13-stdlib | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-15806 | libpython3.13-stdlib | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-16052 | libpython3.13-stdlib | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-17084 | libpython3.13-stdlib | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-19672 | libpython3.13-stdlib | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-3276 | libpython3.13-stdlib | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u3 | Per policy |
| Medium | CVE-2026-4360 | libpython3.13-stdlib | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u5 | Per policy |
| Medium | CVE-2026-7774 | libpython3.13-stdlib | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u3 | Per policy |
| Medium | CVE-2026-87910 | libpython3.13-stdlib | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-9669 | libpython3.13-stdlib | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u3 | Per policy |
| Medium | CVE-2026-105923 | libqt6core6t64 | 6.8.2+dfsg-9+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-105924 | libqt6core6t64 | 6.8.2+dfsg-9+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-105946 | libqt6core6t64 | 6.8.2+dfsg-9+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-15037 | libqt6core6t64 | 6.8.2+dfsg-9+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-19248 | libqt6core6t64 | 6.8.2+dfsg-9+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-78253 | libqt6core6t64 | 6.8.2+dfsg-9+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-96432 | libqt6core6t64 | 6.8.2+dfsg-9+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-107161 | libsasl2-2 | 2.1.28+dfsg1-9 | No fix yet | Per policy |
| Medium | CVE-2026-132138 | libsasl2-2 | 2.1.28+dfsg1-9 | No fix yet | Per policy |
| Medium | CVE-2026-107161 | libsasl2-modules | 2.1.28+dfsg1-9 | No fix yet | Per policy |
| Medium | CVE-2026-132138 | libsasl2-modules | 2.1.28+dfsg1-9 | No fix yet | Per policy |
| Medium | CVE-2026-107161 | libsasl2-modules-db | 2.1.28+dfsg1-9 | No fix yet | Per policy |
| Medium | CVE-2026-132138 | libsasl2-modules-db | 2.1.28+dfsg1-9 | No fix yet | Per policy |
| Medium | CVE-2026-13595 | libsmartcols1 | 2.41-5 | 2.41.5-0+deb13u1 | Per policy |
| Medium | CVE-2026-27456 | libsmartcols1 | 2.41-5 | 2.41.5-0+deb13u1 | Per policy |
| Medium | CVE-2026-3184 | libsmartcols1 | 2.41-5 | No fix yet | Per policy |
| Medium | CVE-2026-119371 | libsqlite3-0 | 3.46.1-7+deb13u1 | No fix yet | Per policy |
| Medium | CVE-2026-119372 | libsqlite3-0 | 3.46.1-7+deb13u1 | No fix yet | Per policy |
| Medium | CVE-2026-119375 | libsqlite3-0 | 3.46.1-7+deb13u1 | No fix yet | Per policy |
| Medium | CVE-2026-119376 | libsqlite3-0 | 3.46.1-7+deb13u1 | No fix yet | Per policy |
| Medium | CVE-2026-119378 | libsqlite3-0 | 3.46.1-7+deb13u1 | No fix yet | Per policy |
| Medium | CVE-2026-119591 | libsqlite3-0 | 3.46.1-7+deb13u1 | No fix yet | Per policy |
| Medium | CVE-2026-50812 | libsqlite3-0 | 3.46.1-7+deb13u1 | No fix yet | Per policy |
| Medium | CVE-2026-50813 | libsqlite3-0 | 3.46.1-7+deb13u1 | No fix yet | Per policy |
| Medium | CVE-2025-15661 | libssh2-1t64 | 1.11.1-1 | 1.11.1-1+deb13u1 | Per policy |
| Medium | CVE-2026-58051 | libssh2-1t64 | 1.11.1-1 | 1.11.1-1+deb13u2 | Per policy |
| Medium | CVE-2026-66032 | libssh2-1t64 | 1.11.1-1 | 1.11.1-1+deb13u2 | Per policy |
| Medium | CVE-2026-66033 | libssh2-1t64 | 1.11.1-1 | 1.11.1-1+deb13u2 | Per policy |
| Medium | CVE-2026-66034 | libssh2-1t64 | 1.11.1-1 | 1.11.1-1+deb13u2 | Per policy |
| Medium | CVE-2026-66035 | libssh2-1t64 | 1.11.1-1 | 1.11.1-1+deb13u2 | Per policy |
| Medium | CVE-2026-107496 | libssl3t64 | 3.5.6-1~deb13u2+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-121482 | libssl3t64 | 3.5.6-1~deb13u2+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-18798 | libssl3t64 | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u2 | Per policy |
| Medium | CVE-2026-35190 | libssl3t64 | 3.5.6-1~deb13u2+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-42772 | libssl3t64 | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u3 | Per policy |
| Medium | CVE-2026-54872 | libssl3t64 | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u3 | Per policy |
| Medium | CVE-2026-54873 | libssl3t64 | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u3 | Per policy |
| Medium | CVE-2026-54875 | libssl3t64 | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u3 | Per policy |
| Medium | CVE-2026-63072 | libssl3t64 | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u2 | Per policy |
| Medium | CVE-2026-63076 | libssl3t64 | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u2 | Per policy |
| Medium | CVE-2026-72897 | libssl3t64 | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u3 | Per policy |
| Medium | CVE-2026-75804 | libssl3t64 | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u3 | Per policy |
| Medium | CVE-2026-75805 | libssl3t64 | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u3 | Per policy |
| Medium | CVE-2026-75806 | libssl3t64 | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u3 | Per policy |
| Medium | CVE-2026-77696 | libssl3t64 | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u3 | Per policy |
| Medium | CVE-2026-84784 | libssl3t64 | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u3 | Per policy |
| Medium | CVE-2026-84786 | libssl3t64 | 3.5.6-1~deb13u2+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-95690 | libssl3t64 | 3.5.6-1~deb13u2+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-95691 | libssl3t64 | 3.5.6-1~deb13u2+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-95692 | libssl3t64 | 3.5.6-1~deb13u2+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-102010 | libstdc++-14-dev | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-114690 | libstdc++-14-dev | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-114691 | libstdc++-14-dev | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-115455 | libstdc++-14-dev | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-125709 | libstdc++-14-dev | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-95619 | libstdc++-14-dev | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-102010 | libstdc++6 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-114690 | libstdc++6 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-114691 | libstdc++6 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-115455 | libstdc++6 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-125709 | libstdc++6 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-95619 | libstdc++6 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-15059 | libsystemd-shared | 257.13-1~deb13u1 | No fix yet | Per policy |
| Medium | CVE-2026-15059 | libsystemd0 | 257.13-1~deb13u1 | No fix yet | Per policy |
| Medium | CVE-2026-15779 | libtalloc2 | 2:2.4.3+samba4.22.8+dfsg-0+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-58216 | libtalloc2 | 2:2.4.3+samba4.22.8+dfsg-0+deb13u2 | 2:4.22.10+dfsg-0+deb13u2 | Per policy |
| Medium | CVE-2026-58218 | libtalloc2 | 2:2.4.3+samba4.22.8+dfsg-0+deb13u2 | 2:4.22.10+dfsg-0+deb13u2 | Per policy |
| Medium | CVE-2026-58224 | libtalloc2 | 2:2.4.3+samba4.22.8+dfsg-0+deb13u2 | 2:4.22.10+dfsg-0+deb13u2 | Per policy |
| Medium | CVE-2026-18495 | libtiff6 | 4.7.0-3+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-104357 | libtirpc-common | 1.3.6+ds-1 | No fix yet | Per policy |
| Medium | CVE-2026-85231 | libtirpc-common | 1.3.6+ds-1 | No fix yet | Per policy |
| Medium | CVE-2026-85977 | libtirpc-common | 1.3.6+ds-1 | No fix yet | Per policy |
| Medium | CVE-2026-104357 | libtirpc3t64 | 1.3.6+ds-1 | No fix yet | Per policy |
| Medium | CVE-2026-85231 | libtirpc3t64 | 1.3.6+ds-1 | No fix yet | Per policy |
| Medium | CVE-2026-85977 | libtirpc3t64 | 1.3.6+ds-1 | No fix yet | Per policy |
| Medium | CVE-2026-102010 | libtsan2 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-114690 | libtsan2 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-114691 | libtsan2 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-115455 | libtsan2 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-125709 | libtsan2 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-95619 | libtsan2 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-102010 | libubsan1 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-114690 | libubsan1 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-114691 | libubsan1 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-115455 | libubsan1 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-125709 | libubsan1 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-95619 | libubsan1 | 14.2.0-19 | No fix yet | Per policy |
| Medium | CVE-2026-15059 | libudev1 | 257.13-1~deb13u1 | No fix yet | Per policy |
| Medium | CVE-2026-23679 | libusb-1.0-0 | 2:1.0.28-1 | No fix yet | Per policy |
| Medium | CVE-2026-47104 | libusb-1.0-0 | 2:1.0.28-1 | No fix yet | Per policy |
| Medium | CVE-2026-13595 | libuuid1 | 2.41-5 | 2.41.5-0+deb13u1 | Per policy |
| Medium | CVE-2026-27456 | libuuid1 | 2.41-5 | 2.41.5-0+deb13u1 | Per policy |
| Medium | CVE-2026-3184 | libuuid1 | 2.41-5 | No fix yet | Per policy |
| Medium | CVE-2026-15779 | libwbclient0 | 2:4.22.8+dfsg-0+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-58216 | libwbclient0 | 2:4.22.8+dfsg-0+deb13u2 | 2:4.22.10+dfsg-0+deb13u2 | Per policy |
| Medium | CVE-2026-58218 | libwbclient0 | 2:4.22.8+dfsg-0+deb13u2 | 2:4.22.10+dfsg-0+deb13u2 | Per policy |
| Medium | CVE-2026-58224 | libwbclient0 | 2:4.22.8+dfsg-0+deb13u2 | 2:4.22.10+dfsg-0+deb13u2 | Per policy |
| Medium | CVE-2026-94283 | libx11-6 | 2:1.8.12-1 | No fix yet | Per policy |
| Medium | CVE-2026-94284 | libx11-6 | 2:1.8.12-1 | No fix yet | Per policy |
| Medium | CVE-2026-94285 | libx11-6 | 2:1.8.12-1 | No fix yet | Per policy |
| Medium | CVE-2026-94283 | libx11-data | 2:1.8.12-1 | No fix yet | Per policy |
| Medium | CVE-2026-94284 | libx11-data | 2:1.8.12-1 | No fix yet | Per policy |
| Medium | CVE-2026-94285 | libx11-data | 2:1.8.12-1 | No fix yet | Per policy |
| Medium | CVE-2026-0990 | libxml2 | 2.12.7+dfsg+really2.9.14-2.1+deb13u2 | 2.12.7+dfsg+really2.9.14-2.1+deb13u3 | Per policy |
| Medium | CVE-2026-76781 | libxml2 | 2.12.7+dfsg+really2.9.14-2.1+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-86137 | libxml2 | 2.12.7+dfsg+really2.9.14-2.1+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2019-15213 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2019-16089 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2019-20794 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2020-14304 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2020-36694 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-31082 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-3397 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-37454 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-6238 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-6240 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-2193 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-24864 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-25740 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-56709 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-21752 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-21949 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-37880 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-38036 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-38311 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-39762 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-39822 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-40146 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-40217 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-40247 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-68304 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71117 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71188 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71202 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71302 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71315 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-23152 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-23265 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-23348 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31435 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31537 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31591 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31692 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31777 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43029 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43115 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43301 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43326 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43416 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46017 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46096 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46147 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46153 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46314 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46317 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-52953 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-52994 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-53106 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-53107 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-53246 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63805 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63819 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63858 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63941 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64066 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64067 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64078 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64160 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64212 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64255 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64520 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-68086 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-68382 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-72355 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-72365 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-72454 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74314 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74324 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74337 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74342 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74354 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74638 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80579 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80580 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80670 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80721 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80785 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80872 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80899 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89610 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89611 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89632 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89637 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89639 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89722 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89826 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89935 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90040 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90098 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90237 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90317 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90379 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90401 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-92500 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-92518 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93044 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93047 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93099 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93135 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93154 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93237 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93270 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93276 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97499 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97526 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97563 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97565 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98087 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98115 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98119 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98125 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98162 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98273 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98277 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98279 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98284 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98286 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98288 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98292 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98294 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98296 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98313 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98330 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98333 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98341 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98353 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98355 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98376 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98420 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98444 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98471 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98556 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98558 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98570 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98589 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98598 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98599 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98616 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98652 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98740 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98747 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98789 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98795 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98799 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98800 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98803 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98810 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98813 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98814 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98815 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98816 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98820 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98824 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98829 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98834 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98839 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98843 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98875 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98878 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98883 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98894 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98897 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98914 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98917 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98924 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98926 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98932 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98942 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98946 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98954 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98958 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98972 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98983 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98999 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99125 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99189 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99208 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99209 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99215 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99275 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99294 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99308 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99314 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99315 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99316 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99317 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99318 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99319 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99320 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99335 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99336 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99345 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99347 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99350 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99363 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99369 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99377 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99379 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99380 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99383 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99384 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99394 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99426 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99447 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99472 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99484 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99493 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99495 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99522 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99566 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99567 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99570 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99571 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99573 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99574 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99576 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99577 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99578 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99582 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99586 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99587 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99588 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99589 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99593 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99596 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99597 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99598 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99600 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99601 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99602 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99604 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99606 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99608 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99609 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99611 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99613 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99614 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99616 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99617 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99618 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99619 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99620 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99624 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99625 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99626 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99627 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99629 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99632 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99633 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99635 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99637 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99638 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99642 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99643 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99644 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99646 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99647 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99650 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99651 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99652 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99653 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99654 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99655 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99656 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99657 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99658 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99660 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99663 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99664 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99665 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99669 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99670 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99671 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99672 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99673 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99674 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99675 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99676 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99678 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99680 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99682 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99683 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99684 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99685 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99687 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99688 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99690 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99691 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99692 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99693 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99694 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99695 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99696 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99697 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99698 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99701 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99703 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99706 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99708 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99710 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99712 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99713 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99716 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99717 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99718 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99719 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99720 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99721 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99722 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99725 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99729 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99730 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99731 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99732 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99734 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99735 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99736 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99737 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99739 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99740 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99742 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99743 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99744 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99749 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99750 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99751 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99752 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99753 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99755 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99756 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99757 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99760 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99761 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99762 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99763 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99764 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99765 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99766 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99768 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99770 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99771 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99773 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99774 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99775 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99776 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99777 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99780 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99781 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99783 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99784 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99786 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99788 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99790 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99791 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99792 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99793 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99794 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99796 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99797 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2019-15213 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2019-16089 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2019-20794 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2020-14304 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2020-36694 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-31082 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-3397 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-37454 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-6238 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-6240 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-2193 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-24864 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-25740 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-56709 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-21752 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-21949 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-37880 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-38036 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-38311 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-39762 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-39822 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-40146 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-40217 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-40247 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-68304 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71117 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71188 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71202 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71302 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71315 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-23152 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-23265 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-23348 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31435 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31537 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31591 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31692 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31777 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43029 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43115 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43301 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43326 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43416 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46017 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46096 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46147 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46153 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46314 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46317 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-52953 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-52994 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-53106 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-53107 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-53246 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63805 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63819 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63858 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63941 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64066 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64067 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64078 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64160 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64212 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64255 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64520 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-68086 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-68382 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-72355 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-72365 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-72454 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74314 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74324 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74337 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74342 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74354 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74638 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80579 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80580 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80670 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80721 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80785 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80872 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80899 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89610 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89611 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89632 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89637 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89639 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89722 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89826 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89935 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90040 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90098 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90237 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90317 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90379 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90401 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-92500 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-92518 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93044 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93047 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93099 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93135 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93154 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93237 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93270 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93276 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97499 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97526 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97563 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97565 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98087 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98115 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98119 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98125 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98162 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98273 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98277 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98279 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98284 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98286 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98288 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98292 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98294 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98296 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98313 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98330 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98333 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98341 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98353 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98355 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98376 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98420 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98444 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98471 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98556 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98558 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98570 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98589 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98598 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98599 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98616 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98652 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98740 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98747 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98789 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98795 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98799 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98800 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98803 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98810 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98813 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98814 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98815 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98816 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98820 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98824 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98829 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98834 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98839 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98843 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98875 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98878 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98883 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98894 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98897 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98914 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98917 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98924 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98926 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98932 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98942 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98946 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98954 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98958 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98972 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98983 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98999 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99125 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99189 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99208 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99209 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99215 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99275 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99294 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99308 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99314 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99315 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99316 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99317 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99318 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99319 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99320 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99335 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99336 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99345 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99347 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99350 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99363 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99369 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99377 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99379 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99380 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99383 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99384 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99394 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99426 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99447 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99472 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99484 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99493 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99495 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99522 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99566 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99567 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99570 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99571 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99573 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99574 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99576 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99577 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99578 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99582 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99586 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99587 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99588 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99589 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99593 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99596 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99597 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99598 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99600 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99601 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99602 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99604 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99606 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99608 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99609 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99611 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99613 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99614 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99616 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99617 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99618 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99619 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99620 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99624 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99625 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99626 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99627 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99629 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99632 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99633 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99635 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99637 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99638 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99642 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99643 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99644 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99646 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99647 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99650 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99651 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99652 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99653 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99654 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99655 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99656 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99657 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99658 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99660 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99663 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99664 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99665 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99669 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99670 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99671 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99672 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99673 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99674 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99675 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99676 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99678 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99680 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99682 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99683 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99684 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99685 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99687 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99688 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99690 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99691 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99692 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99693 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99694 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99695 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99696 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99697 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99698 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99701 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99703 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99706 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99708 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99710 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99712 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99713 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99716 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99717 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99718 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99719 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99720 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99721 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99722 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99725 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99729 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99730 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99731 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99732 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99734 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99735 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99736 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99737 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99739 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99740 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99742 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99743 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99744 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99749 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99750 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99751 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99752 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99753 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99755 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99756 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99757 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99760 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99761 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99762 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99763 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99764 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99765 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99766 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99768 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99770 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99771 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99773 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99774 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99775 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99776 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99777 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99780 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99781 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99783 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99784 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99786 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99788 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99790 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99791 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99792 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99793 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99794 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99796 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99797 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2019-15213 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2019-16089 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2019-20794 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2020-14304 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2020-36694 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-31082 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-3397 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-37454 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-6238 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-6240 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-2193 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-24864 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-25740 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-56709 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-21752 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-21949 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-37880 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-38036 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-38311 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-39762 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-39822 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-40146 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-40217 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-40247 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-68304 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71117 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71188 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71202 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71302 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71315 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-23152 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-23265 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-23348 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31435 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31537 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31591 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31692 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31777 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43029 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43115 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43301 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43326 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43416 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46017 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46096 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46147 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46153 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46314 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46317 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-52953 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-52994 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-53106 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-53107 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-53246 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63805 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63819 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63858 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63941 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64066 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64067 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64078 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64160 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64212 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64255 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64520 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-68086 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-68382 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-72355 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-72365 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-72454 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74314 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74324 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74337 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74342 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74354 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74638 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80579 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80580 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80670 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80721 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80785 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80872 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80899 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89610 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89611 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89632 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89637 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89639 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89722 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89826 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89935 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90040 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90098 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90237 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90317 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90379 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90401 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-92500 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-92518 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93044 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93047 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93099 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93135 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93154 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93237 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93270 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93276 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97499 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97526 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97563 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97565 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98087 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98115 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98119 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98125 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98162 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98273 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98277 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98279 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98284 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98286 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98288 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98292 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98294 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98296 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98313 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98330 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98333 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98341 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98353 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98355 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98376 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98420 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98444 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98471 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98556 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98558 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98570 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98589 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98598 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98599 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98616 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98652 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98740 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98747 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98789 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98795 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98799 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98800 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98803 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98810 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98813 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98814 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98815 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98816 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98820 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98824 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98829 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98834 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98839 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98843 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98875 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98878 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98883 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98894 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98897 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98914 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98917 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98924 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98926 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98932 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98942 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98946 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98954 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98958 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98972 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98983 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98999 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99125 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99189 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99208 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99209 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99215 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99275 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99294 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99308 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99314 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99315 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99316 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99317 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99318 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99319 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99320 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99335 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99336 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99345 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99347 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99350 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99363 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99369 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99377 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99379 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99380 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99383 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99384 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99394 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99426 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99447 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99472 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99484 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99493 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99495 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99522 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99566 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99567 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99570 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99571 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99573 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99574 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99576 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99577 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99578 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99582 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99586 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99587 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99588 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99589 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99593 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99596 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99597 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99598 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99600 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99601 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99602 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99604 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99606 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99608 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99609 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99611 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99613 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99614 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99616 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99617 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99618 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99619 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99620 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99624 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99625 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99626 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99627 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99629 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99632 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99633 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99635 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99637 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99638 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99642 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99643 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99644 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99646 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99647 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99650 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99651 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99652 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99653 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99654 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99655 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99656 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99657 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99658 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99660 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99663 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99664 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99665 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99669 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99670 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99671 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99672 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99673 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99674 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99675 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99676 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99678 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99680 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99682 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99683 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99684 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99685 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99687 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99688 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99690 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99691 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99692 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99693 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99694 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99695 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99696 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99697 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99698 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99701 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99703 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99706 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99708 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99710 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99712 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99713 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99716 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99717 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99718 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99719 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99720 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99721 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99722 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99725 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99729 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99730 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99731 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99732 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99734 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99735 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99736 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99737 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99739 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99740 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99742 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99743 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99744 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99749 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99750 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99751 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99752 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99753 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99755 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99756 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99757 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99760 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99761 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99762 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99763 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99764 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99765 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99766 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99768 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99770 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99771 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99773 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99774 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99775 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99776 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99777 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99780 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99781 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99783 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99784 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99786 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99788 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99790 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99791 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99792 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99793 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99794 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99796 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99797 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2019-15213 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2019-16089 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2019-20794 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2020-14304 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2020-36694 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-31082 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-3397 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-37454 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-6238 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-6240 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-2193 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-24864 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-25740 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-56709 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-21752 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-21949 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-37880 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-38036 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-38311 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-39762 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-39822 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-40146 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-40217 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-40247 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-68304 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71117 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71188 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71202 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71302 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71315 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-23152 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-23265 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-23348 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31435 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31537 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31591 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31692 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31777 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43029 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43115 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43301 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43326 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43416 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46017 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46096 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46147 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46153 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46314 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46317 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-52953 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-52994 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-53106 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-53107 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-53246 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63805 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63819 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63858 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63941 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64066 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64067 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64078 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64160 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64212 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64255 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64520 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-68086 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-68382 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-72355 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-72365 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-72454 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74314 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74324 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74337 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74342 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74354 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74638 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80579 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80580 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80670 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80721 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80785 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80872 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80899 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89610 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89611 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89632 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89637 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89639 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89722 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89826 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89935 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90040 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90098 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90237 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90317 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90379 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90401 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-92500 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-92518 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93044 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93047 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93099 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93135 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93154 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93237 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93270 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93276 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97499 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97526 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97563 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97565 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98087 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98115 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98119 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98125 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98162 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98273 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98277 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98279 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98284 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98286 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98288 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98292 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98294 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98296 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98313 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98330 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98333 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98341 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98353 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98355 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98376 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98420 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98444 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98471 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98556 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98558 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98570 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98589 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98598 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98599 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98616 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98652 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98740 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98747 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98789 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98795 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98799 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98800 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98803 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98810 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98813 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98814 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98815 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98816 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98820 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98824 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98829 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98834 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98839 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98843 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98875 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98878 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98883 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98894 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98897 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98914 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98917 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98924 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98926 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98932 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98942 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98946 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98954 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98958 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98972 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98983 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98999 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99125 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99189 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99208 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99209 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99215 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99275 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99294 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99308 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99314 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99315 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99316 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99317 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99318 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99319 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99320 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99335 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99336 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99345 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99347 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99350 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99363 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99369 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99377 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99379 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99380 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99383 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99384 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99394 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99426 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99447 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99472 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99484 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99493 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99495 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99522 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99566 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99567 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99570 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99571 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99573 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99574 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99576 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99577 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99578 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99582 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99586 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99587 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99588 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99589 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99593 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99596 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99597 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99598 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99600 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99601 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99602 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99604 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99606 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99608 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99609 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99611 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99613 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99614 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99616 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99617 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99618 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99619 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99620 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99624 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99625 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99626 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99627 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99629 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99632 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99633 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99635 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99637 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99638 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99642 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99643 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99644 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99646 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99647 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99650 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99651 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99652 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99653 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99654 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99655 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99656 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99657 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99658 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99660 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99663 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99664 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99665 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99669 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99670 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99671 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99672 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99673 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99674 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99675 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99676 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99678 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99680 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99682 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99683 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99684 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99685 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99687 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99688 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99690 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99691 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99692 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99693 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99694 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99695 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99696 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99697 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99698 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99701 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99703 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99706 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99708 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99710 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99712 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99713 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99716 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99717 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99718 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99719 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99720 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99721 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99722 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99725 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99729 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99730 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99731 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99732 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99734 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99735 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99736 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99737 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99739 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99740 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99742 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99743 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99744 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99749 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99750 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99751 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99752 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99753 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99755 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99756 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99757 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99760 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99761 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99762 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99763 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99764 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99765 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99766 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99768 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99770 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99771 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99773 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99774 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99775 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99776 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99777 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99780 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99781 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99783 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99784 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99786 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99788 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99790 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99791 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99792 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99793 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99794 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99796 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99797 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2019-15213 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2019-16089 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2019-20794 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2020-14304 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2020-36694 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-31082 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-3397 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-37454 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-6238 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-6240 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-2193 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-24864 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-25740 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-56709 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-21752 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-21949 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-37880 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-38036 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-38311 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-39762 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-39822 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-40146 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-40217 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-40247 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-68304 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71117 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71188 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71202 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71302 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71315 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-23152 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-23265 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-23348 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31435 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31537 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31591 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31692 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31777 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43029 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43115 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43301 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43326 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43416 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46017 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46096 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46147 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46153 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46314 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46317 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-52953 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-52994 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-53106 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-53107 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-53246 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63805 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63819 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63858 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63941 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64066 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64067 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64078 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64160 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64212 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64255 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64520 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-68086 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-68382 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-72355 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-72365 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-72454 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74314 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74324 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74337 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74342 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74354 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74638 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80579 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80580 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80670 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80721 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80785 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80872 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80899 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89610 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89611 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89632 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89637 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89639 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89722 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89826 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89935 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90040 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90098 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90237 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90317 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90379 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90401 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-92500 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-92518 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93044 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93047 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93099 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93135 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93154 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93237 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93270 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93276 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97499 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97526 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97563 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97565 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98087 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98115 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98119 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98125 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98162 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98273 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98277 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98279 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98284 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98286 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98288 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98292 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98294 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98296 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98313 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98330 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98333 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98341 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98353 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98355 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98376 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98420 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98444 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98471 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98556 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98558 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98570 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98589 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98598 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98599 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98616 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98652 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98740 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98747 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98789 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98795 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98799 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98800 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98803 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98810 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98813 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98814 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98815 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98816 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98820 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98824 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98829 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98834 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98839 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98843 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98875 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98878 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98883 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98894 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98897 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98914 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98917 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98924 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98926 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98932 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98942 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98946 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98954 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98958 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98972 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98983 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98999 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99125 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99189 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99208 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99209 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99215 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99275 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99294 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99308 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99314 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99315 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99316 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99317 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99318 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99319 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99320 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99335 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99336 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99345 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99347 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99350 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99363 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99369 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99377 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99379 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99380 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99383 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99384 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99394 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99426 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99447 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99472 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99484 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99493 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99495 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99522 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99566 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99567 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99570 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99571 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99573 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99574 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99576 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99577 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99578 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99582 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99586 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99587 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99588 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99589 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99593 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99596 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99597 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99598 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99600 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99601 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99602 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99604 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99606 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99608 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99609 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99611 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99613 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99614 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99616 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99617 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99618 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99619 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99620 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99624 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99625 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99626 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99627 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99629 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99632 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99633 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99635 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99637 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99638 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99642 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99643 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99644 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99646 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99647 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99650 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99651 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99652 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99653 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99654 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99655 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99656 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99657 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99658 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99660 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99663 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99664 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99665 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99669 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99670 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99671 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99672 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99673 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99674 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99675 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99676 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99678 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99680 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99682 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99683 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99684 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99685 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99687 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99688 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99690 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99691 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99692 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99693 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99694 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99695 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99696 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99697 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99698 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99701 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99703 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99706 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99708 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99710 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99712 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99713 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99716 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99717 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99718 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99719 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99720 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99721 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99722 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99725 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99729 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99730 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99731 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99732 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99734 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99735 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99736 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99737 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99739 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99740 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99742 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99743 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99744 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99749 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99750 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99751 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99752 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99753 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99755 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99756 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99757 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99760 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99761 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99762 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99763 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99764 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99765 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99766 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99768 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99770 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99771 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99773 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99774 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99775 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99776 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99777 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99780 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99781 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99783 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99784 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99786 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99788 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99790 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99791 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99792 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99793 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99794 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99796 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99797 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2019-15213 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2019-16089 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2019-20794 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2020-14304 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2020-36694 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-31082 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-3397 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-37454 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-6238 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-6240 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-2193 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-24864 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-25740 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-56709 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-21752 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-21949 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-37880 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-38036 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-38311 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-39762 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-39822 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-40146 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-40217 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-40247 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-68304 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71117 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71188 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71202 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71302 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71315 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-23152 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-23265 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-23348 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31435 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31537 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31591 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31692 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31777 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43029 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43115 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43301 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43326 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43416 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46017 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46096 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46147 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46153 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46314 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46317 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-52953 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-52994 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-53106 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-53107 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-53246 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63805 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63819 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63858 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63941 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64066 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64067 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64078 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64160 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64212 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64255 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64520 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-68086 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-68382 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-72355 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-72365 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-72454 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74314 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74324 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74337 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74342 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74354 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74638 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80579 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80580 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80670 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80721 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80785 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80872 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80899 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89610 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89611 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89632 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89637 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89639 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89722 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89826 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89935 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90040 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90098 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90237 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90317 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90379 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90401 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-92500 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-92518 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93044 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93047 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93099 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93135 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93154 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93237 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93270 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93276 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97499 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97526 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97563 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97565 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98087 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98115 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98119 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98125 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98162 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98273 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98277 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98279 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98284 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98286 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98288 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98292 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98294 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98296 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98313 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98330 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98333 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98341 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98353 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98355 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98376 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98420 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98444 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98471 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98556 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98558 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98570 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98589 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98598 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98599 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98616 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98652 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98740 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98747 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98789 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98795 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98799 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98800 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98803 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98810 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98813 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98814 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98815 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98816 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98820 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98824 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98829 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98834 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98839 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98843 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98875 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98878 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98883 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98894 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98897 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98914 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98917 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98924 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98926 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98932 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98942 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98946 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98954 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98958 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98972 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98983 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98999 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99125 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99189 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99208 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99209 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99215 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99275 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99294 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99308 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99314 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99315 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99316 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99317 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99318 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99319 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99320 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99335 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99336 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99345 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99347 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99350 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99363 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99369 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99377 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99379 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99380 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99383 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99384 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99394 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99426 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99447 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99472 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99484 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99493 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99495 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99522 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99566 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99567 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99570 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99571 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99573 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99574 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99576 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99577 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99578 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99582 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99586 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99587 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99588 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99589 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99593 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99596 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99597 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99598 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99600 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99601 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99602 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99604 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99606 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99608 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99609 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99611 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99613 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99614 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99616 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99617 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99618 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99619 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99620 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99624 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99625 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99626 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99627 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99629 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99632 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99633 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99635 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99637 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99638 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99642 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99643 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99644 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99646 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99647 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99650 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99651 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99652 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99653 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99654 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99655 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99656 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99657 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99658 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99660 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99663 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99664 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99665 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99669 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99670 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99671 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99672 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99673 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99674 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99675 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99676 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99678 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99680 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99682 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99683 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99684 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99685 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99687 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99688 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99690 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99691 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99692 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99693 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99694 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99695 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99696 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99697 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99698 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99701 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99703 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99706 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99708 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99710 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99712 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99713 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99716 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99717 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99718 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99719 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99720 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99721 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99722 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99725 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99729 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99730 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99731 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99732 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99734 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99735 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99736 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99737 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99739 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99740 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99742 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99743 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99744 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99749 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99750 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99751 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99752 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99753 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99755 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99756 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99757 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99760 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99761 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99762 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99763 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99764 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99765 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99766 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99768 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99770 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99771 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99773 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99774 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99775 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99776 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99777 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99780 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99781 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99783 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99784 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99786 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99788 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99790 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99791 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99792 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99793 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99794 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99796 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99797 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2019-15213 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2019-16089 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2019-20794 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2020-14304 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2020-36694 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-31082 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-3397 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-37454 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-6238 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-6240 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-2193 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-24864 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-25740 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-56709 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-21752 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-21949 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-37880 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-38036 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-38311 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-39762 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-39822 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-40146 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-40217 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-40247 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-68304 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71117 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71188 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71202 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71302 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71315 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-23152 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-23265 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-23348 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31435 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31537 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31591 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31692 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31777 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43029 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43115 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43301 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43326 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43416 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46017 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46096 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46147 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46153 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46314 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46317 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-52953 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-52994 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-53106 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-53107 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-53246 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63805 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63819 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63858 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63941 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64066 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64067 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64078 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64160 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64212 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64255 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64520 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-68086 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-68382 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-72355 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-72365 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-72454 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74314 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74324 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74337 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74342 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74354 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74638 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80579 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80580 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80670 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80721 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80785 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80872 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80899 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89610 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89611 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89632 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89637 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89639 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89722 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89826 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89935 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90040 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90098 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90237 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90317 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90379 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90401 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-92500 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-92518 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93044 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93047 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93099 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93135 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93154 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93237 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93270 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93276 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97499 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97526 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97563 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97565 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98087 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98115 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98119 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98125 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98162 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98273 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98277 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98279 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98284 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98286 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98288 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98292 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98294 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98296 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98313 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98330 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98333 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98341 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98353 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98355 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98376 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98420 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98444 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98471 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98556 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98558 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98570 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98589 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98598 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98599 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98616 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98652 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98740 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98747 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98789 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98795 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98799 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98800 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98803 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98810 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98813 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98814 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98815 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98816 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98820 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98824 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98829 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98834 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98839 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98843 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98875 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98878 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98883 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98894 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98897 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98914 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98917 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98924 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98926 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98932 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98942 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98946 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98954 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98958 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98972 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98983 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98999 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99125 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99189 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99208 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99209 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99215 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99275 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99294 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99308 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99314 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99315 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99316 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99317 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99318 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99319 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99320 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99335 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99336 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99345 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99347 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99350 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99363 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99369 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99377 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99379 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99380 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99383 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99384 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99394 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99426 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99447 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99472 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99484 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99493 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99495 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99522 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99566 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99567 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99570 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99571 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99573 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99574 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99576 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99577 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99578 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99582 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99586 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99587 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99588 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99589 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99593 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99596 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99597 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99598 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99600 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99601 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99602 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99604 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99606 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99608 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99609 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99611 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99613 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99614 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99616 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99617 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99618 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99619 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99620 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99624 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99625 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99626 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99627 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99629 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99632 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99633 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99635 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99637 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99638 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99642 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99643 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99644 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99646 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99647 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99650 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99651 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99652 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99653 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99654 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99655 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99656 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99657 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99658 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99660 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99663 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99664 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99665 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99669 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99670 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99671 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99672 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99673 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99674 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99675 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99676 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99678 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99680 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99682 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99683 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99684 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99685 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99687 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99688 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99690 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99691 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99692 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99693 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99694 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99695 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99696 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99697 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99698 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99701 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99703 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99706 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99708 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99710 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99712 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99713 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99716 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99717 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99718 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99719 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99720 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99721 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99722 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99725 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99729 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99730 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99731 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99732 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99734 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99735 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99736 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99737 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99739 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99740 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99742 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99743 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99744 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99749 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99750 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99751 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99752 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99753 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99755 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99756 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99757 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99760 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99761 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99762 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99763 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99764 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99765 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99766 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99768 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99770 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99771 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99773 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99774 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99775 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99776 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99777 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99780 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99781 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99783 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99784 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99786 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99788 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99790 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99791 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99792 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99793 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99794 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99796 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99797 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2019-15213 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2019-16089 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2019-20794 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2020-14304 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2020-36694 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-31082 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-3397 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-37454 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-6238 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-6240 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-2193 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-24864 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-25740 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-56709 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-21752 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-21949 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-37880 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-38036 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-38311 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-39762 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-39822 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-40146 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-40217 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-40247 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-68304 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71117 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71188 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71202 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71302 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71315 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-23152 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-23265 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-23348 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31435 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31537 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31591 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31692 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31777 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43029 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43115 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43301 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43326 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43416 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46017 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46096 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46147 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46153 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46314 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46317 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-52953 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-52994 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-53106 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-53107 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-53246 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63805 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63819 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63858 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63941 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64066 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64067 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64078 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64160 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64212 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64255 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64520 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-68086 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-68382 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-72355 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-72365 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-72454 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74314 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74324 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74337 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74342 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74354 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74638 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80579 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80580 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80670 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80721 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80785 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80872 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80899 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89610 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89611 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89632 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89637 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89639 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89722 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89826 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89935 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90040 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90098 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90237 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90317 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90379 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90401 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-92500 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-92518 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93044 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93047 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93099 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93135 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93154 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93237 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93270 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93276 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97499 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97526 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97563 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97565 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98087 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98115 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98119 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98125 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98162 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98273 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98277 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98279 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98284 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98286 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98288 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98292 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98294 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98296 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98313 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98330 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98333 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98341 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98353 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98355 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98376 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98420 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98444 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98471 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98556 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98558 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98570 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98589 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98598 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98599 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98616 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98652 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98740 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98747 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98789 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98795 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98799 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98800 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98803 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98810 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98813 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98814 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98815 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98816 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98820 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98824 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98829 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98834 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98839 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98843 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98875 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98878 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98883 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98894 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98897 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98914 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98917 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98924 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98926 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98932 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98942 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98946 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98954 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98958 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98972 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98983 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98999 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99125 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99189 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99208 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99209 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99215 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99275 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99294 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99308 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99314 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99315 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99316 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99317 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99318 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99319 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99320 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99335 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99336 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99345 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99347 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99350 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99363 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99369 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99377 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99379 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99380 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99383 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99384 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99394 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99426 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99447 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99472 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99484 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99493 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99495 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99522 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99566 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99567 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99570 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99571 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99573 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99574 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99576 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99577 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99578 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99582 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99586 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99587 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99588 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99589 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99593 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99596 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99597 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99598 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99600 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99601 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99602 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99604 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99606 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99608 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99609 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99611 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99613 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99614 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99616 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99617 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99618 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99619 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99620 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99624 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99625 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99626 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99627 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99629 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99632 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99633 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99635 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99637 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99638 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99642 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99643 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99644 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99646 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99647 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99650 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99651 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99652 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99653 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99654 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99655 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99656 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99657 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99658 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99660 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99663 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99664 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99665 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99669 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99670 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99671 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99672 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99673 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99674 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99675 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99676 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99678 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99680 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99682 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99683 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99684 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99685 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99687 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99688 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99690 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99691 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99692 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99693 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99694 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99695 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99696 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99697 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99698 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99701 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99703 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99706 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99708 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99710 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99712 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99713 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99716 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99717 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99718 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99719 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99720 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99721 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99722 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99725 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99729 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99730 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99731 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99732 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99734 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99735 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99736 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99737 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99739 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99740 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99742 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99743 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99744 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99749 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99750 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99751 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99752 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99753 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99755 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99756 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99757 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99760 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99761 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99762 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99763 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99764 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99765 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99766 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99768 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99770 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99771 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99773 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99774 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99775 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99776 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99777 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99780 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99781 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99783 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99784 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99786 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99788 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99790 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99791 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99792 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99793 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99794 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99796 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99797 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2019-15213 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2019-16089 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2019-20794 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2020-14304 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2020-36694 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-31082 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-3397 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-37454 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-6238 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-6240 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-2193 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-24864 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-25740 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-56709 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-21752 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-21949 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-37880 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-38036 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-38311 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-39762 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-39822 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-40146 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-40217 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-40247 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-68304 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71117 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71188 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71202 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71302 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71315 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-23152 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-23265 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-23348 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31435 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31537 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31591 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31692 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31777 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43029 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43115 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43301 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43326 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43416 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46017 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46096 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46147 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46153 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46314 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46317 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-52953 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-52994 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-53106 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-53107 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-53246 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63805 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63819 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63858 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63941 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64066 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64067 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64078 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64160 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64212 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64255 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64520 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-68086 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-68382 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-72355 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-72365 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-72454 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74314 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74324 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74337 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74342 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74354 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74638 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80579 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80580 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80670 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80721 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80785 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80872 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80899 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89610 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89611 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89632 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89637 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89639 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89722 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89826 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89935 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90040 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90098 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90237 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90317 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90379 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90401 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-92500 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-92518 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93044 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93047 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93099 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93135 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93154 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93237 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93270 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93276 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97499 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97526 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97563 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97565 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98087 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98115 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98119 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98125 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98162 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98273 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98277 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98279 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98284 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98286 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98288 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98292 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98294 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98296 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98313 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98330 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98333 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98341 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98353 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98355 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98376 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98420 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98444 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98471 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98556 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98558 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98570 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98589 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98598 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98599 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98616 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98652 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98740 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98747 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98789 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98795 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98799 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98800 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98803 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98810 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98813 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98814 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98815 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98816 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98820 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98824 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98829 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98834 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98839 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98843 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98875 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98878 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98883 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98894 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98897 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98914 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98917 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98924 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98926 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98932 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98942 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98946 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98954 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98958 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98972 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98983 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98999 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99125 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99189 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99208 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99209 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99215 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99275 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99294 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99308 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99314 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99315 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99316 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99317 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99318 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99319 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99320 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99335 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99336 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99345 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99347 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99350 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99363 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99369 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99377 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99379 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99380 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99383 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99384 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99394 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99426 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99447 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99472 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99484 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99493 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99495 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99522 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99566 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99567 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99570 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99571 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99573 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99574 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99576 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99577 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99578 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99582 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99586 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99587 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99588 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99589 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99593 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99596 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99597 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99598 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99600 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99601 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99602 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99604 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99606 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99608 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99609 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99611 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99613 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99614 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99616 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99617 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99618 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99619 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99620 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99624 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99625 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99626 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99627 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99629 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99632 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99633 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99635 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99637 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99638 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99642 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99643 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99644 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99646 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99647 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99650 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99651 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99652 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99653 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99654 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99655 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99656 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99657 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99658 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99660 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99663 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99664 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99665 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99669 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99670 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99671 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99672 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99673 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99674 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99675 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99676 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99678 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99680 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99682 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99683 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99684 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99685 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99687 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99688 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99690 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99691 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99692 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99693 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99694 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99695 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99696 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99697 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99698 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99701 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99703 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99706 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99708 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99710 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99712 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99713 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99716 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99717 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99718 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99719 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99720 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99721 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99722 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99725 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99729 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99730 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99731 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99732 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99734 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99735 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99736 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99737 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99739 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99740 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99742 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99743 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99744 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99749 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99750 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99751 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99752 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99753 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99755 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99756 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99757 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99760 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99761 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99762 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99763 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99764 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99765 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99766 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99768 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99770 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99771 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99773 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99774 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99775 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99776 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99777 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99780 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99781 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99783 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99784 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99786 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99788 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99790 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99791 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99792 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99793 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99794 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99796 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99797 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2019-15213 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2019-16089 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2019-20794 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2020-14304 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2020-36694 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-31082 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-3397 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-37454 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-6238 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-6240 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-2193 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-24864 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-25740 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-56709 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-21752 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-21949 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-37880 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-38036 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-38311 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-39762 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-39822 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-40146 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-40217 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-40247 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-68304 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71117 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71188 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71202 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71302 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71315 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-23152 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-23265 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-23348 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31435 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31537 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31591 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31692 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31777 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43029 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43115 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43301 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43326 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43416 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46017 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46096 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46147 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46153 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46314 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46317 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-52953 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-52994 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-53106 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-53107 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-53246 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63805 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63819 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63858 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63941 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64066 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64067 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64078 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64160 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64212 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64255 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64520 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-68086 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-68382 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-72355 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-72365 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-72454 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74314 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74324 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74337 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74342 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74354 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74638 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80579 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80580 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80670 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80721 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80785 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80872 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80899 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89610 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89611 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89632 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89637 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89639 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89722 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89826 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89935 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90040 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90098 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90237 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90317 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90379 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90401 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-92500 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-92518 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93044 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93047 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93099 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93135 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93154 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93237 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93270 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93276 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97499 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97526 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97563 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97565 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98087 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98115 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98119 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98125 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98162 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98273 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98277 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98279 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98284 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98286 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98288 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98292 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98294 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98296 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98313 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98330 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98333 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98341 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98353 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98355 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98376 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98420 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98444 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98471 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98556 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98558 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98570 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98589 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98598 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98599 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98616 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98652 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98740 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98747 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98789 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98795 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98799 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98800 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98803 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98810 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98813 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98814 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98815 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98816 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98820 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98824 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98829 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98834 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98839 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98843 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98875 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98878 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98883 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98894 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98897 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98914 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98917 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98924 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98926 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98932 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98942 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98946 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98954 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98958 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98972 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98983 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98999 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99125 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99189 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99208 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99209 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99215 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99275 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99294 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99308 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99314 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99315 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99316 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99317 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99318 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99319 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99320 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99335 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99336 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99345 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99347 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99350 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99363 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99369 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99377 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99379 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99380 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99383 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99384 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99394 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99426 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99447 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99472 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99484 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99493 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99495 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99522 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99566 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99567 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99570 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99571 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99573 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99574 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99576 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99577 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99578 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99582 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99586 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99587 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99588 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99589 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99593 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99596 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99597 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99598 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99600 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99601 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99602 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99604 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99606 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99608 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99609 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99611 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99613 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99614 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99616 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99617 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99618 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99619 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99620 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99624 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99625 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99626 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99627 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99629 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99632 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99633 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99635 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99637 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99638 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99642 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99643 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99644 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99646 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99647 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99650 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99651 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99652 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99653 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99654 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99655 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99656 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99657 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99658 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99660 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99663 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99664 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99665 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99669 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99670 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99671 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99672 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99673 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99674 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99675 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99676 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99678 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99680 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99682 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99683 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99684 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99685 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99687 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99688 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99690 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99691 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99692 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99693 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99694 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99695 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99696 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99697 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99698 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99701 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99703 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99706 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99708 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99710 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99712 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99713 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99716 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99717 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99718 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99719 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99720 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99721 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99722 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99725 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99729 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99730 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99731 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99732 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99734 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99735 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99736 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99737 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99739 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99740 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99742 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99743 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99744 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99749 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99750 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99751 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99752 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99753 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99755 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99756 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99757 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99760 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99761 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99762 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99763 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99764 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99765 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99766 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99768 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99770 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99771 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99773 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99774 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99775 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99776 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99777 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99780 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99781 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99783 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99784 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99786 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99788 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99790 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99791 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99792 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99793 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99794 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99796 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99797 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2019-15213 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2019-16089 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2019-20794 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2020-14304 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2020-36694 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-31082 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-3397 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-37454 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-6238 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-6240 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-2193 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-24864 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-25740 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-56709 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-21752 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-21949 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-37880 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-38036 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-38311 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-39762 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-39822 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-40146 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-40217 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-40247 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-68304 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71117 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71188 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71202 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71302 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71315 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-23152 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-23265 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-23348 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31435 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31537 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31591 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31692 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31777 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43029 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43115 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43301 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43326 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43416 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46017 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46096 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46147 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46153 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46314 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46317 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-52953 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-52994 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-53106 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-53107 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-53246 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63805 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63819 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63858 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63941 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64066 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64067 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64078 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64160 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64212 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64255 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64520 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-68086 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-68382 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-72355 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-72365 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-72454 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74314 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74324 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74337 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74342 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74354 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74638 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80579 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80580 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80670 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80721 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80785 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80872 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80899 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89610 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89611 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89632 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89637 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89639 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89722 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89826 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89935 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90040 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90098 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90237 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90317 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90379 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90401 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-92500 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-92518 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93044 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93047 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93099 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93135 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93154 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93237 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93270 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93276 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97499 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97526 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97563 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97565 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98087 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98115 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98119 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98125 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98162 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98273 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98277 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98279 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98284 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98286 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98288 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98292 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98294 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98296 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98313 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98330 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98333 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98341 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98353 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98355 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98376 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98420 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98444 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98471 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98556 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98558 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98570 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98589 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98598 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98599 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98616 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98652 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98740 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98747 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98789 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98795 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98799 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98800 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98803 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98810 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98813 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98814 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98815 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98816 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98820 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98824 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98829 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98834 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98839 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98843 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98875 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98878 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98883 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98894 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98897 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98914 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98917 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98924 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98926 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98932 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98942 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98946 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98954 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98958 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98972 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98983 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98999 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99125 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99189 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99208 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99209 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99215 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99275 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99294 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99308 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99314 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99315 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99316 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99317 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99318 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99319 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99320 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99335 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99336 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99345 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99347 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99350 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99363 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99369 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99377 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99379 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99380 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99383 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99384 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99394 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99426 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99447 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99472 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99484 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99493 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99495 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99522 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99566 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99567 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99570 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99571 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99573 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99574 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99576 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99577 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99578 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99582 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99586 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99587 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99588 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99589 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99593 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99596 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99597 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99598 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99600 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99601 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99602 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99604 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99606 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99608 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99609 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99611 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99613 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99614 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99616 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99617 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99618 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99619 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99620 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99624 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99625 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99626 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99627 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99629 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99632 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99633 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99635 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99637 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99638 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99642 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99643 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99644 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99646 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99647 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99650 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99651 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99652 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99653 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99654 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99655 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99656 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99657 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99658 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99660 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99663 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99664 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99665 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99669 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99670 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99671 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99672 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99673 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99674 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99675 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99676 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99678 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99680 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99682 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99683 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99684 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99685 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99687 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99688 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99690 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99691 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99692 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99693 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99694 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99695 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99696 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99697 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99698 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99701 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99703 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99706 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99708 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99710 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99712 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99713 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99716 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99717 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99718 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99719 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99720 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99721 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99722 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99725 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99729 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99730 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99731 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99732 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99734 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99735 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99736 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99737 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99739 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99740 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99742 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99743 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99744 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99749 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99750 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99751 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99752 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99753 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99755 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99756 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99757 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99760 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99761 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99762 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99763 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99764 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99765 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99766 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99768 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99770 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99771 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99773 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99774 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99775 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99776 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99777 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99780 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99781 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99783 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99784 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99786 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99788 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99790 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99791 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99792 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99793 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99794 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99796 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99797 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2019-15213 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2019-16089 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2019-20794 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2020-14304 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2020-36694 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-31082 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-3397 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-37454 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-6238 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-6240 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-2193 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-24864 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-25740 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-56709 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-21752 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-21949 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-37880 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-38036 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-38311 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-39762 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-39822 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-40146 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-40217 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-40247 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-68304 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71117 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71188 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71202 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71302 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71315 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-23152 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-23265 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-23348 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31435 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31537 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31591 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31692 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31777 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43029 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43115 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43301 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43326 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43416 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46017 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46096 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46147 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46153 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46314 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46317 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-52953 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-52994 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-53106 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-53107 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-53246 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63805 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63819 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63858 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63941 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64066 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64067 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64078 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64160 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64212 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64255 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64520 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-68086 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-68382 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-72355 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-72365 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-72454 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74314 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74324 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74337 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74342 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74354 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74638 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80579 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80580 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80670 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80721 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80785 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80872 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80899 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89610 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89611 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89632 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89637 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89639 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89722 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89826 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89935 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90040 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90098 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90237 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90317 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90379 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90401 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-92500 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-92518 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93044 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93047 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93099 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93135 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93154 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93237 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93270 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93276 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97499 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97526 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97563 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97565 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98087 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98115 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98119 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98125 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98162 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98273 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98277 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98279 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98284 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98286 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98288 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98292 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98294 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98296 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98313 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98330 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98333 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98341 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98353 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98355 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98376 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98420 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98444 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98471 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98556 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98558 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98570 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98589 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98598 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98599 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98616 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98652 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98740 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98747 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98789 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98795 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98799 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98800 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98803 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98810 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98813 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98814 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98815 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98816 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98820 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98824 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98829 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98834 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98839 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98843 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98875 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98878 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98883 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98894 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98897 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98914 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98917 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98924 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98926 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98932 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98942 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98946 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98954 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98958 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98972 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98983 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98999 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99125 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99189 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99208 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99209 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99215 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99275 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99294 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99308 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99314 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99315 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99316 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99317 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99318 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99319 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99320 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99335 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99336 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99345 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99347 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99350 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99363 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99369 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99377 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99379 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99380 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99383 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99384 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99394 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99426 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99447 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99472 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99484 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99493 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99495 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99522 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99566 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99567 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99570 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99571 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99573 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99574 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99576 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99577 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99578 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99582 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99586 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99587 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99588 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99589 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99593 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99596 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99597 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99598 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99600 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99601 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99602 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99604 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99606 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99608 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99609 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99611 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99613 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99614 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99616 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99617 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99618 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99619 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99620 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99624 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99625 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99626 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99627 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99629 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99632 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99633 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99635 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99637 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99638 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99642 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99643 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99644 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99646 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99647 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99650 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99651 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99652 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99653 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99654 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99655 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99656 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99657 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99658 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99660 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99663 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99664 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99665 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99669 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99670 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99671 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99672 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99673 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99674 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99675 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99676 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99678 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99680 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99682 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99683 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99684 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99685 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99687 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99688 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99690 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99691 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99692 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99693 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99694 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99695 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99696 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99697 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99698 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99701 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99703 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99706 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99708 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99710 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99712 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99713 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99716 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99717 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99718 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99719 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99720 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99721 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99722 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99725 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99729 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99730 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99731 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99732 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99734 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99735 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99736 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99737 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99739 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99740 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99742 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99743 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99744 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99749 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99750 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99751 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99752 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99753 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99755 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99756 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99757 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99760 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99761 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99762 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99763 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99764 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99765 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99766 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99768 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99770 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99771 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99773 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99774 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99775 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99776 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99777 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99780 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99781 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99783 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99784 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99786 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99788 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99790 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99791 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99792 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99793 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99794 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99796 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99797 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2019-15213 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2019-16089 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2019-20794 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2020-14304 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2020-36694 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-31082 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-3397 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-37454 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-6238 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-6240 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-2193 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-24864 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-25740 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-56709 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-21752 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-21949 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-37880 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-38036 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-38311 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-39762 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-39822 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-40146 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-40217 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-40247 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-68304 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71117 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71188 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71202 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71302 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71315 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-23152 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-23265 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-23348 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31435 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31537 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31591 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31692 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31777 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43029 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43115 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43301 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43326 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43416 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46017 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46096 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46147 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46153 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46314 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46317 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-52953 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-52994 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-53106 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-53107 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-53246 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63805 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63819 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63858 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63941 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64066 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64067 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64078 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64160 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64212 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64255 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64520 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-68086 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-68382 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-72355 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-72365 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-72454 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74314 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74324 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74337 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74342 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74354 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74638 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80579 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80580 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80670 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80721 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80785 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80872 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80899 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89610 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89611 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89632 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89637 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89639 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89722 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89826 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89935 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90040 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90098 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90237 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90317 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90379 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90401 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-92500 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-92518 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93044 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93047 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93099 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93135 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93154 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93237 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93270 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93276 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97499 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97526 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97563 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97565 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98087 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98115 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98119 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98125 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98162 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98273 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98277 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98279 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98284 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98286 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98288 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98292 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98294 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98296 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98313 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98330 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98333 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98341 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98353 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98355 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98376 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98420 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98444 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98471 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98556 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98558 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98570 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98589 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98598 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98599 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98616 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98652 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98740 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98747 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98789 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98795 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98799 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98800 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98803 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98810 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98813 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98814 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98815 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98816 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98820 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98824 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98829 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98834 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98839 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98843 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98875 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98878 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98883 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98894 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98897 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98914 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98917 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98924 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98926 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98932 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98942 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98946 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98954 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98958 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98972 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98983 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98999 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99125 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99189 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99208 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99209 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99215 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99275 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99294 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99308 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99314 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99315 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99316 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99317 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99318 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99319 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99320 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99335 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99336 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99345 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99347 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99350 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99363 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99369 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99377 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99379 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99380 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99383 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99384 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99394 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99426 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99447 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99472 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99484 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99493 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99495 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99522 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99566 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99567 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99570 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99571 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99573 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99574 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99576 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99577 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99578 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99582 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99586 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99587 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99588 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99589 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99593 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99596 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99597 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99598 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99600 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99601 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99602 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99604 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99606 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99608 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99609 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99611 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99613 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99614 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99616 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99617 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99618 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99619 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99620 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99624 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99625 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99626 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99627 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99629 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99632 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99633 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99635 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99637 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99638 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99642 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99643 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99644 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99646 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99647 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99650 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99651 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99652 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99653 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99654 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99655 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99656 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99657 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99658 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99660 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99663 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99664 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99665 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99669 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99670 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99671 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99672 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99673 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99674 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99675 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99676 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99678 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99680 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99682 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99683 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99684 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99685 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99687 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99688 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99690 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99691 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99692 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99693 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99694 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99695 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99696 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99697 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99698 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99701 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99703 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99706 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99708 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99710 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99712 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99713 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99716 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99717 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99718 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99719 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99720 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99721 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99722 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99725 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99729 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99730 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99731 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99732 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99734 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99735 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99736 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99737 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99739 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99740 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99742 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99743 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99744 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99749 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99750 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99751 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99752 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99753 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99755 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99756 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99757 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99760 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99761 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99762 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99763 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99764 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99765 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99766 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99768 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99770 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99771 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99773 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99774 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99775 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99776 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99777 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99780 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99781 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99783 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99784 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99786 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99788 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99790 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99791 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99792 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99793 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99794 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99796 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99797 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2019-15213 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2019-16089 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2019-20794 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2020-14304 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2020-36694 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-31082 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-3397 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-37454 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-6238 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-6240 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-2193 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-24864 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-25740 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-56709 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-21752 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-21949 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-37880 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-38036 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-38311 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-39762 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-39822 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-40146 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-40217 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-40247 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-68304 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71117 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71188 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71202 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71302 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71315 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-23152 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-23265 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-23348 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31435 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31537 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31591 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31692 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31777 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43029 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43115 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43301 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43326 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43416 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46017 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46096 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46147 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46153 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46314 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46317 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-52953 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-52994 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-53106 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-53107 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-53246 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63805 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63819 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63858 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63941 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64066 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64067 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64078 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64160 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64212 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64255 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64520 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-68086 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-68382 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-72355 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-72365 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-72454 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74314 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74324 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74337 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74342 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74354 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74638 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80579 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80580 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80670 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80721 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80785 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80872 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80899 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89610 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89611 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89632 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89637 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89639 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89722 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89826 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89935 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90040 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90098 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90237 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90317 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90379 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90401 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-92500 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-92518 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93044 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93047 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93099 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93135 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93154 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93237 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93270 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93276 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97499 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97526 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97563 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97565 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98087 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98115 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98119 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98125 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98162 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98273 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98277 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98279 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98284 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98286 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98288 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98292 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98294 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98296 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98313 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98330 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98333 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98341 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98353 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98355 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98376 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98420 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98444 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98471 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98556 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98558 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98570 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98589 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98598 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98599 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98616 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98652 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98740 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98747 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98789 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98795 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98799 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98800 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98803 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98810 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98813 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98814 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98815 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98816 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98820 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98824 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98829 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98834 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98839 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98843 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98875 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98878 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98883 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98894 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98897 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98914 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98917 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98924 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98926 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98932 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98942 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98946 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98954 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98958 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98972 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98983 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98999 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99125 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99189 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99208 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99209 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99215 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99275 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99294 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99308 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99314 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99315 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99316 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99317 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99318 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99319 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99320 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99335 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99336 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99345 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99347 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99350 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99363 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99369 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99377 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99379 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99380 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99383 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99384 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99394 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99426 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99447 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99472 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99484 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99493 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99495 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99522 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99566 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99567 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99570 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99571 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99573 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99574 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99576 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99577 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99578 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99582 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99586 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99587 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99588 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99589 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99593 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99596 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99597 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99598 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99600 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99601 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99602 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99604 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99606 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99608 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99609 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99611 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99613 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99614 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99616 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99617 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99618 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99619 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99620 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99624 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99625 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99626 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99627 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99629 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99632 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99633 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99635 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99637 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99638 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99642 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99643 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99644 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99646 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99647 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99650 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99651 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99652 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99653 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99654 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99655 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99656 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99657 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99658 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99660 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99663 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99664 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99665 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99669 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99670 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99671 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99672 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99673 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99674 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99675 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99676 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99678 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99680 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99682 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99683 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99684 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99685 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99687 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99688 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99690 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99691 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99692 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99693 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99694 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99695 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99696 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99697 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99698 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99701 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99703 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99706 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99708 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99710 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99712 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99713 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99716 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99717 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99718 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99719 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99720 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99721 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99722 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99725 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99729 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99730 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99731 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99732 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99734 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99735 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99736 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99737 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99739 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99740 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99742 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99743 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99744 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99749 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99750 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99751 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99752 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99753 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99755 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99756 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99757 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99760 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99761 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99762 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99763 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99764 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99765 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99766 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99768 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99770 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99771 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99773 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99774 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99775 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99776 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99777 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99780 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99781 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99783 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99784 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99786 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99788 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99790 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99791 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99792 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99793 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99794 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99796 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99797 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2019-15213 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2019-16089 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2019-20794 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2020-14304 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2020-36694 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-31082 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-3397 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-37454 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-6238 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2023-6240 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-2193 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-24864 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-25740 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2024-56709 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-21752 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-21949 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-37880 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-38036 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-38311 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-39762 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-39822 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-40146 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-40217 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-40247 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-68304 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71117 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71188 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71202 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71302 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2025-71315 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-23152 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-23265 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-23348 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31435 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31537 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31591 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31692 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-31777 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43029 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43115 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43301 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43326 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-43416 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46017 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46096 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46147 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46153 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46314 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-46317 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-52953 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-52994 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-53106 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-53107 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-53246 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63805 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63819 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63858 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-63941 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64066 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64067 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64078 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64160 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64212 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64255 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-64520 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-68086 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-68382 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-72355 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-72365 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-72454 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74314 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74324 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74337 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74342 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74354 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-74638 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80579 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80580 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80670 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80721 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80785 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80872 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-80899 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89610 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89611 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89632 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89637 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89639 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89722 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89826 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89935 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90040 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90098 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90237 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90317 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90379 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-90401 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-92500 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-92518 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93044 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93047 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93099 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93135 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93154 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93237 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93270 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-93276 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97499 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97526 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97563 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-97565 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98087 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98115 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98119 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98125 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98162 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98273 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98277 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98279 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98284 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98286 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98288 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98292 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98294 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98296 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98313 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98330 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98333 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98341 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98353 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98355 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98376 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98420 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98444 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98471 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98556 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98558 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98570 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98589 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98598 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98599 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98616 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98652 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98740 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98747 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98789 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98795 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98799 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98800 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98803 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98810 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98813 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98814 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98815 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98816 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98820 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98824 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98829 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98834 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98839 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98843 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98875 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98878 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98883 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98894 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98897 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98914 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98917 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98924 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98926 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98932 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98942 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98946 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98954 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98958 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98972 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98983 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-98999 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99125 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99189 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99208 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99209 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99215 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99275 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99294 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99308 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99314 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99315 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99316 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99317 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99318 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99319 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99320 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99335 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99336 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99345 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99347 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99350 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99363 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99369 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99377 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99379 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99380 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99383 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99384 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99394 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99426 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99447 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99472 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99484 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99493 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99495 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99522 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99566 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99567 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99570 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99571 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99573 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99574 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99576 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99577 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99578 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99582 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99586 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99587 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99588 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99589 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99593 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99596 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99597 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99598 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99600 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99601 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99602 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99604 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99606 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99608 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99609 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99611 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99613 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99614 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99616 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99617 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99618 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99619 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99620 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99624 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99625 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99626 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99627 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99629 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99632 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99633 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99635 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99637 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99638 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99642 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99643 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99644 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99646 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99647 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99650 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99651 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99652 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99653 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99654 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99655 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99656 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99657 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99658 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99660 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99663 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99664 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99665 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99669 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99670 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99671 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99672 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99673 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99674 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99675 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99676 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99678 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99680 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99682 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99683 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99684 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99685 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99687 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99688 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99690 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99691 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99692 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99693 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99694 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99695 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99696 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99697 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99698 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99701 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99703 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99706 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99708 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99710 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99712 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99713 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99716 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99717 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99718 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99719 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99720 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99721 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99722 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99725 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99729 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99730 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99731 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99732 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99734 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99735 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99736 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99737 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99739 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99740 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99742 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99743 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99744 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99749 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99750 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99751 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99752 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99753 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99755 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99756 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99757 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99760 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99761 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99762 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99763 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99764 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99765 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99766 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99768 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99770 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99771 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99773 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99774 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99775 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99776 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99777 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99780 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99781 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99783 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99784 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99786 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99788 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99790 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99791 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99792 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99793 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99794 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99796 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-99797 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-115819 | locales | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Medium | CVE-2026-84243 | locales | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Medium | CVE-2026-13595 | login | 1:4.16.0-2+really2.41-5 | 2.41.5-0+deb13u1 | Per policy |
| Medium | CVE-2026-27456 | login | 1:4.16.0-2+really2.41-5 | 2.41.5-0+deb13u1 | Per policy |
| Medium | CVE-2026-3184 | login | 1:4.16.0-2+really2.41-5 | No fix yet | Per policy |
| Medium | CVE-2026-13595 | mount | 2.41-5 | 2.41.5-0+deb13u1 | Per policy |
| Medium | CVE-2026-27456 | mount | 2.41-5 | 2.41.5-0+deb13u1 | Per policy |
| Medium | CVE-2026-3184 | mount | 2.41-5 | No fix yet | Per policy |
| Medium | CVE-2026-6390 | nano | 8.4-1+deb13u1 | No fix yet | Per policy |
| Medium | CVE-2026-10805 | network-manager | 1.52.1-1+rpt4 | No fix yet | Per policy |
| Medium | CVE-2026-10805 | network-manager-l10n | 1.52.1-1+rpt4 | No fix yet | Per policy |
| Medium | CVE-2026-46571 | ntfs-3g | 1:2022.10.3-5+deb13u1 | 1:2022.10.3-5+deb13u2 | Per policy |
| Medium | CVE-2026-56136 | ntfs-3g | 1:2022.10.3-5+deb13u1 | 1:2022.10.3-5+deb13u2 | Per policy |
| Medium | CVE-2026-106552 | openssh-client | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Medium | CVE-2026-106585 | openssh-client | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Medium | CVE-2026-106586 | openssh-client | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Medium | CVE-2026-59995 | openssh-client | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Medium | CVE-2026-59996 | openssh-client | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Medium | CVE-2026-59997 | openssh-client | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Medium | CVE-2026-59998 | openssh-client | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Medium | CVE-2026-60001 | openssh-client | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Medium | CVE-2026-73282 | openssh-client | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Medium | CVE-2026-73283 | openssh-client | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Medium | CVE-2026-106552 | openssh-server | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Medium | CVE-2026-106585 | openssh-server | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Medium | CVE-2026-106586 | openssh-server | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Medium | CVE-2026-59995 | openssh-server | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Medium | CVE-2026-59996 | openssh-server | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Medium | CVE-2026-59997 | openssh-server | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Medium | CVE-2026-59998 | openssh-server | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Medium | CVE-2026-60001 | openssh-server | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Medium | CVE-2026-73282 | openssh-server | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Medium | CVE-2026-73283 | openssh-server | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Medium | CVE-2026-106552 | openssh-sftp-server | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Medium | CVE-2026-106585 | openssh-sftp-server | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Medium | CVE-2026-106586 | openssh-sftp-server | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Medium | CVE-2026-59995 | openssh-sftp-server | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Medium | CVE-2026-59996 | openssh-sftp-server | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Medium | CVE-2026-59997 | openssh-sftp-server | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Medium | CVE-2026-59998 | openssh-sftp-server | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Medium | CVE-2026-60001 | openssh-sftp-server | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Medium | CVE-2026-73282 | openssh-sftp-server | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Medium | CVE-2026-73283 | openssh-sftp-server | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Medium | CVE-2026-107496 | openssl | 3.5.6-1~deb13u2+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-121482 | openssl | 3.5.6-1~deb13u2+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-18798 | openssl | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u2 | Per policy |
| Medium | CVE-2026-35190 | openssl | 3.5.6-1~deb13u2+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-42772 | openssl | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u3 | Per policy |
| Medium | CVE-2026-54872 | openssl | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u3 | Per policy |
| Medium | CVE-2026-54873 | openssl | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u3 | Per policy |
| Medium | CVE-2026-54875 | openssl | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u3 | Per policy |
| Medium | CVE-2026-63072 | openssl | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u2 | Per policy |
| Medium | CVE-2026-63076 | openssl | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u2 | Per policy |
| Medium | CVE-2026-72897 | openssl | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u3 | Per policy |
| Medium | CVE-2026-75804 | openssl | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u3 | Per policy |
| Medium | CVE-2026-75805 | openssl | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u3 | Per policy |
| Medium | CVE-2026-75806 | openssl | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u3 | Per policy |
| Medium | CVE-2026-77696 | openssl | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u3 | Per policy |
| Medium | CVE-2026-84784 | openssl | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u3 | Per policy |
| Medium | CVE-2026-84786 | openssl | 3.5.6-1~deb13u2+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-95690 | openssl | 3.5.6-1~deb13u2+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-95691 | openssl | 3.5.6-1~deb13u2+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-95692 | openssl | 3.5.6-1~deb13u2+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-107496 | openssl-provider-legacy | 3.5.6-1~deb13u2+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-121482 | openssl-provider-legacy | 3.5.6-1~deb13u2+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-18798 | openssl-provider-legacy | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u2 | Per policy |
| Medium | CVE-2026-35190 | openssl-provider-legacy | 3.5.6-1~deb13u2+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-42772 | openssl-provider-legacy | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u3 | Per policy |
| Medium | CVE-2026-54872 | openssl-provider-legacy | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u3 | Per policy |
| Medium | CVE-2026-54873 | openssl-provider-legacy | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u3 | Per policy |
| Medium | CVE-2026-54875 | openssl-provider-legacy | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u3 | Per policy |
| Medium | CVE-2026-63072 | openssl-provider-legacy | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u2 | Per policy |
| Medium | CVE-2026-63076 | openssl-provider-legacy | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u2 | Per policy |
| Medium | CVE-2026-72897 | openssl-provider-legacy | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u3 | Per policy |
| Medium | CVE-2026-75804 | openssl-provider-legacy | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u3 | Per policy |
| Medium | CVE-2026-75805 | openssl-provider-legacy | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u3 | Per policy |
| Medium | CVE-2026-75806 | openssl-provider-legacy | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u3 | Per policy |
| Medium | CVE-2026-77696 | openssl-provider-legacy | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u3 | Per policy |
| Medium | CVE-2026-84784 | openssl-provider-legacy | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u3 | Per policy |
| Medium | CVE-2026-84786 | openssl-provider-legacy | 3.5.6-1~deb13u2+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-95690 | openssl-provider-legacy | 3.5.6-1~deb13u2+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-95691 | openssl-provider-legacy | 3.5.6-1~deb13u2+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-95692 | openssl-provider-legacy | 3.5.6-1~deb13u2+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-89085 | parted | 3.6-5 | 3.6-5+deb13u1 | Per policy |
| Medium | CVE-2026-89088 | parted | 3.6-5 | 3.6-5+deb13u1 | Per policy |
| Medium | CVE-2026-115207 | patch | 2.8-2 | 2.8-2+deb13u1 | Per policy |
| Medium | CVE-2025-15649 | perl | 5.40.1-6 | 5.40.1-6+deb13u1 | Per policy |
| Medium | CVE-2026-12087 | perl | 5.40.1-6 | 5.40.1-6+deb13u1 | Per policy |
| Medium | CVE-2026-15534 | perl | 5.40.1-6 | No fix yet | Per policy |
| Medium | CVE-2026-19487 | perl | 5.40.1-6 | 5.40.1-6+deb13u1 | Per policy |
| Medium | CVE-2026-48959 | perl | 5.40.1-6 | 5.40.1-6+deb13u1 | Per policy |
| Medium | CVE-2026-48961 | perl | 5.40.1-6 | 5.40.1-6+deb13u1 | Per policy |
| Medium | CVE-2026-7010 | perl | 5.40.1-6 | 5.40.1-6+deb13u1 | Per policy |
| Medium | CVE-2026-7017 | perl | 5.40.1-6 | 5.40.1-6+deb13u1 | Per policy |
| Medium | CVE-2026-82560 | perl | 5.40.1-6 | No fix yet | Per policy |
| Medium | CVE-2025-15649 | perl-base | 5.40.1-6 | 5.40.1-6+deb13u1 | Per policy |
| Medium | CVE-2026-12087 | perl-base | 5.40.1-6 | 5.40.1-6+deb13u1 | Per policy |
| Medium | CVE-2026-15534 | perl-base | 5.40.1-6 | No fix yet | Per policy |
| Medium | CVE-2026-19487 | perl-base | 5.40.1-6 | 5.40.1-6+deb13u1 | Per policy |
| Medium | CVE-2026-48959 | perl-base | 5.40.1-6 | 5.40.1-6+deb13u1 | Per policy |
| Medium | CVE-2026-48961 | perl-base | 5.40.1-6 | 5.40.1-6+deb13u1 | Per policy |
| Medium | CVE-2026-7010 | perl-base | 5.40.1-6 | 5.40.1-6+deb13u1 | Per policy |
| Medium | CVE-2026-7017 | perl-base | 5.40.1-6 | 5.40.1-6+deb13u1 | Per policy |
| Medium | CVE-2026-82560 | perl-base | 5.40.1-6 | No fix yet | Per policy |
| Medium | CVE-2025-15649 | perl-modules-5.40 | 5.40.1-6 | 5.40.1-6+deb13u1 | Per policy |
| Medium | CVE-2026-12087 | perl-modules-5.40 | 5.40.1-6 | 5.40.1-6+deb13u1 | Per policy |
| Medium | CVE-2026-15534 | perl-modules-5.40 | 5.40.1-6 | No fix yet | Per policy |
| Medium | CVE-2026-19487 | perl-modules-5.40 | 5.40.1-6 | 5.40.1-6+deb13u1 | Per policy |
| Medium | CVE-2026-48959 | perl-modules-5.40 | 5.40.1-6 | 5.40.1-6+deb13u1 | Per policy |
| Medium | CVE-2026-48961 | perl-modules-5.40 | 5.40.1-6 | 5.40.1-6+deb13u1 | Per policy |
| Medium | CVE-2026-7010 | perl-modules-5.40 | 5.40.1-6 | 5.40.1-6+deb13u1 | Per policy |
| Medium | CVE-2026-7017 | perl-modules-5.40 | 5.40.1-6 | 5.40.1-6+deb13u1 | Per policy |
| Medium | CVE-2026-82560 | perl-modules-5.40 | 5.40.1-6 | No fix yet | Per policy |
| Medium | CVE-2026-4897 | polkitd | 126-2 | No fix yet | Per policy |
| Medium | CVE-2026-75883 | ppp | 2.5.2-1+1 | No fix yet | Per policy |
| Medium | CVE-2025-6966 | python-apt-common | 3.0.0 | No fix yet | Per policy |
| Medium | CVE-2025-6966 | python3-apt | 3.0.0 | No fix yet | Per policy |
| Medium | CVE-2026-34073 | python3-cryptography | 43.0.0-3+deb13u1 | No fix yet | Per policy |
| Medium | CVE-2026-69248 | python3-cryptography | 43.0.0-3+deb13u1 | No fix yet | Per policy |
| Medium | CVE-2026-45409 | python3-idna | 3.10-1 | 3.10-1+deb13u1 | Per policy |
| Medium | CVE-2026-102265 | python3-jwt | 2.10.1-2+deb13u1 | No fix yet | Per policy |
| Medium | CVE-2026-102269 | python3-jwt | 2.10.1-2+deb13u1 | No fix yet | Per policy |
| Medium | CVE-2026-102270 | python3-jwt | 2.10.1-2+deb13u1 | No fix yet | Per policy |
| Medium | CVE-2026-48522 | python3-jwt | 2.10.1-2+deb13u1 | No fix yet | Per policy |
| Medium | CVE-2026-48523 | python3-jwt | 2.10.1-2+deb13u1 | No fix yet | Per policy |
| Medium | CVE-2026-48524 | python3-jwt | 2.10.1-2+deb13u1 | No fix yet | Per policy |
| Medium | CVE-2026-48525 | python3-jwt | 2.10.1-2+deb13u1 | No fix yet | Per policy |
| Medium | CVE-2026-49264 | python3-oauthlib | 3.2.2-3 | No fix yet | Per policy |
| Medium | CVE-2026-49265 | python3-oauthlib | 3.2.2-3 | No fix yet | Per policy |
| Medium | CVE-2025-8869 | python3-pip-whl | 25.1.1+dfsg-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-13346 | python3-pip-whl | 25.1.1+dfsg-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-3219 | python3-pip-whl | 25.1.1+dfsg-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-6357 | python3-pip-whl | 25.1.1+dfsg-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-8643 | python3-pip-whl | 25.1.1+dfsg-1+rpt1 | No fix yet | Per policy |
| Medium | CVE-2026-25645 | python3-requests | 2.32.3+dfsg-5+deb13u1 | No fix yet | Per policy |
| Medium | CVE-2026-44431 | python3-urllib3 | 2.3.0-3+deb13u1 | 2.3.0-3+deb13u2 | Per policy |
| Medium | CVE-2025-12781 | python3.13 | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2025-15366 | python3.13 | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2025-15367 | python3.13 | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-0864 | python3.13 | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u5 | Per policy |
| Medium | CVE-2026-103995 | python3.13 | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-114583 | python3.13 | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-116566 | python3.13 | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-11972 | python3.13 | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u5 | Per policy |
| Medium | CVE-2026-12345 | python3.13 | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-124249 | python3.13 | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-1502 | python3.13 | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u3 | Per policy |
| Medium | CVE-2026-15310 | python3.13 | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-15806 | python3.13 | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-16052 | python3.13 | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-17084 | python3.13 | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-19672 | python3.13 | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-3276 | python3.13 | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u3 | Per policy |
| Medium | CVE-2026-4360 | python3.13 | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u5 | Per policy |
| Medium | CVE-2026-7774 | python3.13 | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u3 | Per policy |
| Medium | CVE-2026-87910 | python3.13 | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-9669 | python3.13 | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u3 | Per policy |
| Medium | CVE-2025-12781 | python3.13-minimal | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2025-15366 | python3.13-minimal | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2025-15367 | python3.13-minimal | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-0864 | python3.13-minimal | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u5 | Per policy |
| Medium | CVE-2026-103995 | python3.13-minimal | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-114583 | python3.13-minimal | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-116566 | python3.13-minimal | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-11972 | python3.13-minimal | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u5 | Per policy |
| Medium | CVE-2026-12345 | python3.13-minimal | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-124249 | python3.13-minimal | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-1502 | python3.13-minimal | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u3 | Per policy |
| Medium | CVE-2026-15310 | python3.13-minimal | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-15806 | python3.13-minimal | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-16052 | python3.13-minimal | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-17084 | python3.13-minimal | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-19672 | python3.13-minimal | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-3276 | python3.13-minimal | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u3 | Per policy |
| Medium | CVE-2026-4360 | python3.13-minimal | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u5 | Per policy |
| Medium | CVE-2026-7774 | python3.13-minimal | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u3 | Per policy |
| Medium | CVE-2026-87910 | python3.13-minimal | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-9669 | python3.13-minimal | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u3 | Per policy |
| Medium | CVE-2025-12781 | python3.13-venv | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2025-15366 | python3.13-venv | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2025-15367 | python3.13-venv | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-0864 | python3.13-venv | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u5 | Per policy |
| Medium | CVE-2026-103995 | python3.13-venv | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-114583 | python3.13-venv | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-116566 | python3.13-venv | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-11972 | python3.13-venv | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u5 | Per policy |
| Medium | CVE-2026-12345 | python3.13-venv | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-124249 | python3.13-venv | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-1502 | python3.13-venv | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u3 | Per policy |
| Medium | CVE-2026-15310 | python3.13-venv | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-15806 | python3.13-venv | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-16052 | python3.13-venv | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-17084 | python3.13-venv | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-19672 | python3.13-venv | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-3276 | python3.13-venv | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u3 | Per policy |
| Medium | CVE-2026-4360 | python3.13-venv | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u5 | Per policy |
| Medium | CVE-2026-7774 | python3.13-venv | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u3 | Per policy |
| Medium | CVE-2026-87910 | python3.13-venv | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Medium | CVE-2026-9669 | python3.13-venv | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u3 | Per policy |
| Medium | CVE-2026-13595 | rfkill | 2.41-5 | 2.41.5-0+deb13u1 | Per policy |
| Medium | CVE-2026-27456 | rfkill | 2.41-5 | 2.41.5-0+deb13u1 | Per policy |
| Medium | CVE-2026-3184 | rfkill | 2.41-5 | No fix yet | Per policy |
| Medium | CVE-2026-53786 | rsync | 3.4.1+ds1-5+deb13u3 | 3.5.0+ds1-0+deb13u1 | Per policy |
| Medium | CVE-2026-53788 | rsync | 3.4.1+ds1-5+deb13u3 | 3.5.0+ds1-0+deb13u1 | Per policy |
| Medium | CVE-2026-53792 | rsync | 3.4.1+ds1-5+deb13u3 | 3.5.0+ds1-0+deb13u1 | Per policy |
| Medium | CVE-2026-53794 | rsync | 3.4.1+ds1-5+deb13u3 | 3.5.0+ds1-0+deb13u1 | Per policy |
| Medium | CVE-2026-53796 | rsync | 3.4.1+ds1-5+deb13u3 | 3.5.0+ds1-0+deb13u1 | Per policy |
| Medium | CVE-2026-53797 | rsync | 3.4.1+ds1-5+deb13u3 | 3.5.0+ds1-0+deb13u1 | Per policy |
| Medium | CVE-2026-53798 | rsync | 3.4.1+ds1-5+deb13u3 | 3.5.0+ds1-0+deb13u1 | Per policy |
| Medium | CVE-2026-53799 | rsync | 3.4.1+ds1-5+deb13u3 | 3.5.0+ds1-0+deb13u1 | Per policy |
| Medium | CVE-2026-53800 | rsync | 3.4.1+ds1-5+deb13u3 | 3.5.0+ds1-0+deb13u1 | Per policy |
| Medium | CVE-2026-53801 | rsync | 3.4.1+ds1-5+deb13u3 | 3.5.0+ds1-0+deb13u1 | Per policy |
| Medium | CVE-2026-70453 | rsync | 3.4.1+ds1-5+deb13u3 | 3.5.0+ds1-0+deb13u1 | Per policy |
| Medium | CVE-2026-70454 | rsync | 3.4.1+ds1-5+deb13u3 | 3.5.0+ds1-0+deb13u1 | Per policy |
| Medium | CVE-2026-70459 | rsync | 3.4.1+ds1-5+deb13u3 | 3.5.0+ds1-0+deb13u1 | Per policy |
| Medium | CVE-2026-70462 | rsync | 3.4.1+ds1-5+deb13u3 | 3.5.0+ds1-0+deb13u1 | Per policy |
| Medium | CVE-2026-106552 | ssh | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Medium | CVE-2026-106585 | ssh | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Medium | CVE-2026-106586 | ssh | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Medium | CVE-2026-59995 | ssh | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Medium | CVE-2026-59996 | ssh | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Medium | CVE-2026-59997 | ssh | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Medium | CVE-2026-59998 | ssh | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Medium | CVE-2026-60001 | ssh | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Medium | CVE-2026-73282 | ssh | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Medium | CVE-2026-73283 | ssh | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Medium | CVE-2026-15059 | systemd | 257.13-1~deb13u1 | No fix yet | Per policy |
| Medium | CVE-2026-15059 | systemd-sysv | 257.13-1~deb13u1 | No fix yet | Per policy |
| Medium | CVE-2026-15059 | systemd-timesyncd | 257.13-1~deb13u1 | No fix yet | Per policy |
| Medium | CVE-2026-18477 | tar | 1.35+dfsg-3.1 | No fix yet | Per policy |
| Medium | CVE-2026-18508 | tar | 1.35+dfsg-3.1 | No fix yet | Per policy |
| Medium | CVE-2026-5704 | tar | 1.35+dfsg-3.1 | No fix yet | Per policy |
| Medium | CVE-2026-15059 | udev | 257.13-1~deb13u1 | No fix yet | Per policy |
| Medium | CVE-2026-13595 | util-linux | 2.41-5 | 2.41.5-0+deb13u1 | Per policy |
| Medium | CVE-2026-27456 | util-linux | 2.41-5 | 2.41.5-0+deb13u1 | Per policy |
| Medium | CVE-2026-3184 | util-linux | 2.41-5 | No fix yet | Per policy |
| Medium | CVE-2025-53905 | vim-common | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | Per policy |
| Medium | CVE-2025-53906 | vim-common | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | Per policy |
| Medium | CVE-2026-25749 | vim-common | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | Per policy |
| Medium | CVE-2026-28418 | vim-common | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | Per policy |
| Medium | CVE-2026-28419 | vim-common | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | Per policy |
| Medium | CVE-2026-28420 | vim-common | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | Per policy |
| Medium | CVE-2026-32249 | vim-common | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | Per policy |
| Medium | CVE-2026-41411 | vim-common | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | Per policy |
| Medium | CVE-2026-42307 | vim-common | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | Per policy |
| Medium | CVE-2026-44656 | vim-common | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | Per policy |
| Medium | CVE-2026-45130 | vim-common | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | Per policy |
| Medium | CVE-2026-47167 | vim-common | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | Per policy |
| Medium | CVE-2026-55892 | vim-common | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | Per policy |
| Medium | CVE-2026-57452 | vim-common | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | Per policy |
| Medium | CVE-2026-59857 | vim-common | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | Per policy |
| Medium | CVE-2026-73070 | vim-common | 2:9.1.1230-2 | No fix yet | Per policy |
| Medium | CVE-2026-73074 | vim-common | 2:9.1.1230-2 | No fix yet | Per policy |
| Medium | CVE-2025-53905 | vim-tiny | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | Per policy |
| Medium | CVE-2025-53906 | vim-tiny | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | Per policy |
| Medium | CVE-2026-25749 | vim-tiny | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | Per policy |
| Medium | CVE-2026-28418 | vim-tiny | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | Per policy |
| Medium | CVE-2026-28419 | vim-tiny | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | Per policy |
| Medium | CVE-2026-28420 | vim-tiny | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | Per policy |
| Medium | CVE-2026-32249 | vim-tiny | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | Per policy |
| Medium | CVE-2026-41411 | vim-tiny | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | Per policy |
| Medium | CVE-2026-42307 | vim-tiny | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | Per policy |
| Medium | CVE-2026-44656 | vim-tiny | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | Per policy |
| Medium | CVE-2026-45130 | vim-tiny | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | Per policy |
| Medium | CVE-2026-47167 | vim-tiny | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | Per policy |
| Medium | CVE-2026-55892 | vim-tiny | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | Per policy |
| Medium | CVE-2026-57452 | vim-tiny | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | Per policy |
| Medium | CVE-2026-59857 | vim-tiny | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | Per policy |
| Medium | CVE-2026-73070 | vim-tiny | 2:9.1.1230-2 | No fix yet | Per policy |
| Medium | CVE-2026-73074 | vim-tiny | 2:9.1.1230-2 | No fix yet | Per policy |
| Medium | CVE-2021-31879 | wget | 1.25.0-2 | No fix yet | Per policy |
| Medium | CVE-2026-15146 | wget | 1.25.0-2 | No fix yet | Per policy |
| Medium | CVE-2026-58469 | wget | 1.25.0-2 | No fix yet | Per policy |
| Medium | CVE-2026-58470 | wget | 1.25.0-2 | No fix yet | Per policy |
| Medium | CVE-2026-34743 | xz-utils | 5.8.1-1 | 5.8.1-1+deb13u1 | Per policy |
| Medium | CVE-2026-27171 | zlib1g | 1:1.3.dfsg+really1.3.1-1+b1 | 1:1.3.dfsg+really1.3.1-1+deb13u1 | Per policy |
| Medium | CVE-2026-56855 | golang.org/x/crypto | v0.53.0 | 0.56.0 | Per policy |
| Medium | CVE-2026-78662 | golang.org/x/crypto | v0.53.0 | 0.56.0 | Per policy |
| Medium | CVE-2026-78659 | golang.org/x/net | v0.55.0 | 0.60.0 | Per policy |
| Medium | CVE-2026-78660 | golang.org/x/net | v0.55.0 | 0.60.0 | Per policy |
| Medium | CVE-2026-78663 | golang.org/x/net | v0.55.0 | 0.60.0 | Per policy |
| Medium | CVE-2026-97032 | golang.org/x/net | v0.55.0 | 0.60.0 | Per policy |
| Medium | CVE-2026-97045 | golang.org/x/net | v0.55.0 | 0.62.0 | Per policy |
| Medium | CVE-2026-42505 | stdlib | 1.26.4 | 1.25.12, 1.26.5, 1.27.0-rc.2 | Per policy |
| Medium | CVE-2026-56866 | stdlib | 1.26.4 | 1.26.9, 1.27.2 | Per policy |
| Medium | CVE-2026-78659 | stdlib | 1.26.4 | 1.26.9, 1.27.2 | Per policy |
| Medium | CVE-2026-78660 | stdlib | 1.26.4 | 1.26.9, 1.27.2 | Per policy |
| Medium | CVE-2026-78663 | stdlib | 1.26.4 | 1.26.9, 1.27.2 | Per policy |
| Medium | CVE-2026-94439 | stdlib | 1.26.4 | 1.26.9, 1.27.2 | Per policy |
| Medium | CVE-2026-94440 | stdlib | 1.26.4 | 1.26.9, 1.27.2 | Per policy |
| Medium | CVE-2026-94448 | stdlib | 1.26.4 | 1.26.9, 1.27.2 | Per policy |
| Medium | CVE-2026-97030 | stdlib | 1.26.4 | 1.26.9, 1.27.2 | Per policy |
| Medium | CVE-2026-97032 | stdlib | 1.26.4 | 1.26.9, 1.27.2 | Per policy |
| Medium | CVE-2026-97054 | stdlib | 1.26.4 | 1.26.11, 1.27.4 | Per policy |
| Medium | GHSA-h4gh-qq45-vh27 | cryptography | 43.0.0 | 43.0.1 | Per policy |
| Medium | CVE-2026-45409 | idna | 3.10 | 3.15 | Per policy |
| Medium | CVE-2026-49264 | oauthlib | 3.2.2 | 4.0.0 | Per policy |
| Medium | CVE-2026-49265 | oauthlib | 3.2.2 | 4.0.0 | Per policy |
| Medium | CVE-2025-8869 | pip | 25.1.1 | 25.3 | Per policy |
| Medium | CVE-2026-13346 | pip | 25.1.1 | 26.2.0 | Per policy |
| Medium | CVE-2026-3219 | pip | 25.1.1 | 26.1 | Per policy |
| Medium | CVE-2026-6357 | pip | 25.1.1 | 26.1 | Per policy |
| Medium | CVE-2026-8643 | pip | 25.1.1 | 26.1.2 | Per policy |
| Medium | CVE-2026-101917 | pyjwt | 2.10.1 | 2.14.0 | Per policy |
| Medium | CVE-2026-101918 | pyjwt | 2.10.1 | 2.15.0 | Per policy |
| Medium | CVE-2026-102269 | pyjwt | 2.10.1 | 2.14.0 | Per policy |
| Medium | CVE-2026-102270 | pyjwt | 2.10.1 | 2.14.0 | Per policy |
| Medium | CVE-2026-102274 | pyjwt | 2.10.1 | 2.14.0 | Per policy |
| Medium | CVE-2026-102275 | pyjwt | 2.10.1 | 2.15.0 | Per policy |
| Medium | CVE-2026-48522 | pyjwt | 2.10.1 | 2.13.0 | Per policy |
| Medium | CVE-2026-48523 | pyjwt | 2.10.1 | 2.13.0 | Per policy |
| Medium | CVE-2026-48525 | pyjwt | 2.10.1 | 2.13.0 | Per policy |
| Medium | CVE-2024-47081 | requests | 2.32.3 | 2.32.4 | Per policy |
| Medium | CVE-2026-25645 | requests | 2.32.3 | 2.33.0 | Per policy |
| Medium | CVE-2026-59890 | setuptools | 78.1.1 | 83.0.0 | Per policy |
| Medium | CVE-2025-50181 | urllib3 | 2.3.0 | 2.5.0 | Per policy |
| Medium | CVE-2025-50182 | urllib3 | 2.3.0 | 2.5.0 | Per policy |
| Medium | CVE-1999-0524 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-1999-0656 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2006-2932 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2007-4998 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2008-2544 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2010-4563 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2014-8171 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2016-0774 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2016-3695 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2017-1000255 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2017-1000377 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2018-10840 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2018-10876 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2018-10882 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2018-14625 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2019-3016 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2019-3819 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2019-3887 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2020-10742 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2020-16119 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2020-8834 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2021-20265 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2021-3564 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2021-3669 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2021-3714 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2021-3759 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2021-4218 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2022-0286 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2022-1462 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2022-2308 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2022-2663 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2022-3435 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2022-3523 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2022-3567 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2022-3621 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2022-3636 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2022-36402 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2022-38096 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2022-42895 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2022-4382 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2022-4543 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2023-1073 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2023-1074 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2023-1076 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2023-2898 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2023-3772 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2023-3773 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2023-39180 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2023-4155 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2023-52904 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2023-6176 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2023-6238 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2023-6240 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2023-6535 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2023-6679 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2023-7042 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2025-71308 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2025-71313 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-100070 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-100071 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-100073 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-100074 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-100076 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-100077 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-100078 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-100079 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-23328 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-23371 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-23374 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-23377 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-23442 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-31420 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-31560 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-31777 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-43022 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-43045 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-43053 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-43095 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-43115 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-43131 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-43174 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-43191 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-43204 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-43228 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-43299 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-43308 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-43310 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-43311 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-43326 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-43344 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-43443 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-45850 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-45897 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-45901 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-45930 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-45961 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-45963 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-46008 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-46017 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-46032 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-46092 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-46153 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-46245 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-46252 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-46298 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-46302 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-52930 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-52939 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-52940 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-52944 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-52948 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-52949 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-52965 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53007 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53008 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53017 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53027 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53080 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53102 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53106 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53108 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53113 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53124 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53134 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53135 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53139 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53140 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53141 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53142 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53144 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53150 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53152 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53154 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53158 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53163 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53164 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53167 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53168 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53177 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53181 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53190 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53196 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53197 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53207 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53208 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53210 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53211 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53213 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53214 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53218 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53219 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53220 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53222 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53226 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53227 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53236 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53237 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53238 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53241 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53245 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53249 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53251 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53252 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53257 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53258 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53261 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53263 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53269 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53271 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53274 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53285 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53292 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53308 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53313 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53325 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53327 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53328 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53331 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53332 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53333 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53334 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53335 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53336 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53337 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53338 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53339 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53340 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53342 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53343 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53345 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53347 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53349 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53350 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53352 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53353 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53364 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53382 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53385 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53393 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-53403 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-63798 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-63811 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-63821 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-63835 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-63836 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-63839 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-63868 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-63871 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-63873 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-63876 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-63877 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-63878 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-63880 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-63882 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-63890 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-63891 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-63896 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-63897 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-63900 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-63908 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-63929 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-63931 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-63932 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-63933 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-63936 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-63948 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-63958 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-63959 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-63960 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-63961 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-63962 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-63963 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-63964 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-63965 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-63966 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-63969 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-63973 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-63983 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-63986 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-63988 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-63989 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-63990 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-63991 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-63997 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-63998 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-63999 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64006 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64012 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64013 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64019 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64040 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64070 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64079 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64146 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64154 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64159 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64187 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64190 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64192 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64205 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64207 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64227 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64229 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64233 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64234 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64236 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64240 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64241 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64244 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64248 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64250 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64252 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64253 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64254 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64256 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64258 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64262 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64263 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64264 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64267 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64275 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64278 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64282 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64288 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64289 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64290 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64291 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64292 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64294 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64295 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64297 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64301 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64302 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64306 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64307 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64308 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64309 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64310 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64314 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64316 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64321 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64325 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64326 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64327 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64328 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64331 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64332 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64334 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64335 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64336 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64337 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64338 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64345 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64347 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64349 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64350 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64351 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64353 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64356 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64357 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64358 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64359 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64360 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64369 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64370 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64371 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64373 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64376 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64404 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64405 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64409 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64415 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64416 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64417 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64419 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64425 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64426 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64428 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64429 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64454 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64457 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64458 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64461 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64462 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64464 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64465 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64466 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64472 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64473 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64474 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64476 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64478 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64480 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64482 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64483 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64484 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64486 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64488 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64489 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64492 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64493 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64500 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64503 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64504 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64505 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64507 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64508 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64509 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64511 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64512 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64513 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64514 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64525 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64526 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64527 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64528 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64537 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64538 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64542 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64553 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-64569 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98049 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98051 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98053 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98054 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98055 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98057 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98058 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98059 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98061 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98062 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98063 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98064 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98067 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98068 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98072 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98074 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98075 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98078 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98079 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98080 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98081 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98082 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98084 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98086 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98087 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98089 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98090 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98091 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98092 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98094 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98095 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98097 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98098 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98099 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98101 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98102 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98104 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98105 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98106 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98109 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98113 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98114 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98119 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98120 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98121 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98123 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98124 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98125 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98126 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98127 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98128 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98129 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98131 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98134 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98142 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98146 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98147 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98148 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98151 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98153 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98157 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98158 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98159 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98160 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98161 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Medium | CVE-2026-98162 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Low | CVE-2022-47111 | 7zip | 25.01+dfsg-1~deb13u2 | No fix yet | Per policy |
| Low | CVE-2022-47112 | 7zip | 25.01+dfsg-1~deb13u2 | No fix yet | Per policy |
| Low | CVE-2026-104086 | 7zip | 25.01+dfsg-1~deb13u2 | No fix yet | Per policy |
| Low | CVE-2026-48092 | 7zip | 25.01+dfsg-1~deb13u2 | No fix yet | Per policy |
| Low | CVE-2026-48101 | 7zip | 25.01+dfsg-1~deb13u2 | No fix yet | Per policy |
| Low | CVE-2026-48102 | 7zip | 25.01+dfsg-1~deb13u2 | No fix yet | Per policy |
| Low | CVE-2026-48103 | 7zip | 25.01+dfsg-1~deb13u2 | No fix yet | Per policy |
| Low | CVE-2026-48104 | 7zip | 25.01+dfsg-1~deb13u2 | No fix yet | Per policy |
| Low | CVE-2026-48111 | 7zip | 25.01+dfsg-1~deb13u2 | No fix yet | Per policy |
| Low | CVE-2011-3374 | apt | 3.0.3 | No fix yet | Per policy |
| Low | CVE-2011-3374 | apt-utils | 3.0.3 | No fix yet | Per policy |
| Low | TEMP-0841856-B18BAF | bash | 5.2.37-2+b9 | No fix yet | Per policy |
| Low | CVE-2018-7738 | bash-completion | 1:2.16.0-7 | No fix yet | Per policy |
| Low | CVE-2017-13716 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2018-20673 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2018-20712 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2018-9996 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2021-32256 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11081 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11082 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11083 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11412 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11413 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11414 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1147 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1148 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1149 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11494 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11495 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1150 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1151 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1152 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1153 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1176 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1178 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1180 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1181 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1182 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11839 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11840 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-3198 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-5244 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-5245 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-66861 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-66862 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-66863 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-66864 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-66865 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-66866 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69644 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69645 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69646 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69647 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69648 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69649 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69650 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69651 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69652 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-7545 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-7546 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-8225 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-15003 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-18220 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-19548 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-3441 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-3442 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-4647 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-6844 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-6845 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-6846 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90801 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90802 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90803 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90804 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90828 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90829 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90830 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90831 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-91779 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-91780 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-91781 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-91782 | binutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2017-13716 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2018-20673 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2018-20712 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2018-9996 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2021-32256 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11081 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11082 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11083 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11412 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11413 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11414 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1147 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1148 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1149 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11494 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11495 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1150 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1151 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1152 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1153 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1176 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1178 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1180 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1181 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1182 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11839 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11840 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-3198 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-5244 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-5245 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-66861 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-66862 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-66863 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-66864 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-66865 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-66866 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69644 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69645 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69646 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69647 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69648 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69649 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69650 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69651 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69652 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-7545 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-7546 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-8225 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-15003 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-18220 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-19548 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-3441 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-3442 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-4647 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-6844 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-6845 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-6846 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90801 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90802 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90803 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90804 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90828 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90829 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90830 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90831 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-91779 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-91780 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-91781 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-91782 | binutils-aarch64-linux-gnu | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2017-13716 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2018-20673 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2018-20712 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2018-9996 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2021-32256 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11081 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11082 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11083 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11412 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11413 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11414 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1147 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1148 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1149 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11494 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11495 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1150 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1151 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1152 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1153 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1176 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1178 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1180 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1181 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1182 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11839 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11840 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-3198 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-5244 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-5245 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-66861 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-66862 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-66863 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-66864 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-66865 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-66866 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69644 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69645 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69646 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69647 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69648 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69649 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69650 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69651 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69652 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-7545 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-7546 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-8225 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-15003 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-18220 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-19548 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-3441 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-3442 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-4647 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-6844 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-6845 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-6846 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90801 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90802 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90803 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90804 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90828 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90829 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90830 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90831 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-91779 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-91780 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-91781 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-91782 | binutils-common | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2016-9797 | bluez | 5.82-1.1+rpt1 | No fix yet | Per policy |
| Low | CVE-2016-9798 | bluez | 5.82-1.1+rpt1 | No fix yet | Per policy |
| Low | CVE-2016-9799 | bluez | 5.82-1.1+rpt1 | No fix yet | Per policy |
| Low | CVE-2016-9800 | bluez | 5.82-1.1+rpt1 | No fix yet | Per policy |
| Low | CVE-2016-9801 | bluez | 5.82-1.1+rpt1 | No fix yet | Per policy |
| Low | CVE-2016-9802 | bluez | 5.82-1.1+rpt1 | No fix yet | Per policy |
| Low | CVE-2016-9803 | bluez | 5.82-1.1+rpt1 | No fix yet | Per policy |
| Low | CVE-2016-9804 | bluez | 5.82-1.1+rpt1 | No fix yet | Per policy |
| Low | CVE-2016-9917 | bluez | 5.82-1.1+rpt1 | No fix yet | Per policy |
| Low | CVE-2016-9918 | bluez | 5.82-1.1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-105460 | bluez | 5.82-1.1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-0563 | bsdextrautils | 2.41-5 | No fix yet | Per policy |
| Low | CVE-2025-14104 | bsdextrautils | 2.41-5 | 2.41.3-1 | Per policy |
| Low | CVE-2022-0563 | bsdutils | 1:2.41-5 | No fix yet | Per policy |
| Low | CVE-2025-14104 | bsdutils | 1:2.41-5 | 2.41.3-1 | Per policy |
| Low | CVE-2018-1000500 | busybox | 1:1.37.0-6+b8 | No fix yet | Per policy |
| Low | CVE-2025-46394 | busybox | 1:1.37.0-6+b8 | No fix yet | Per policy |
| Low | CVE-2025-60876 | busybox | 1:1.37.0-6+b8 | No fix yet | Per policy |
| Low | CVE-2026-124740 | busybox | 1:1.37.0-6+b8 | No fix yet | Per policy |
| Low | CVE-2026-124742 | busybox | 1:1.37.0-6+b8 | No fix yet | Per policy |
| Low | CVE-2026-124743 | busybox | 1:1.37.0-6+b8 | No fix yet | Per policy |
| Low | CVE-2026-124746 | busybox | 1:1.37.0-6+b8 | No fix yet | Per policy |
| Low | CVE-2026-76014 | busybox | 1:1.37.0-6+b8 | No fix yet | Per policy |
| Low | CVE-2026-88834 | busybox | 1:1.37.0-6+b8 | No fix yet | Per policy |
| Low | CVE-2026-88835 | busybox | 1:1.37.0-6+b8 | No fix yet | Per policy |
| Low | CVE-2026-88841 | busybox | 1:1.37.0-6+b8 | No fix yet | Per policy |
| Low | CVE-2026-88842 | busybox | 1:1.37.0-6+b8 | No fix yet | Per policy |
| Low | CVE-2014-2830 | cifs-utils | 2:7.4-1 | No fix yet | Per policy |
| Low | CVE-2017-18018 | coreutils | 9.7-3 | No fix yet | Per policy |
| Low | CVE-2025-5278 | coreutils | 9.7-3 | No fix yet | Per policy |
| Low | CVE-2026-56391 | coreutils | 9.7-3 | No fix yet | Per policy |
| Low | CVE-2026-56392 | coreutils | 9.7-3 | No fix yet | Per policy |
| Low | CVE-2026-126820 | cpio | 2.15+dfsg-2 | No fix yet | Per policy |
| Low | CVE-2026-126831 | cpio | 2.15+dfsg-2 | No fix yet | Per policy |
| Low | CVE-2026-66484 | cpio | 2.15+dfsg-2 | No fix yet | Per policy |
| Low | CVE-2026-115456 | cpp-14 | 14.2.0-19 | No fix yet | Per policy |
| Low | CVE-2026-115456 | cpp-14-aarch64-linux-gnu | 14.2.0-19 | No fix yet | Per policy |
| Low | CVE-2026-115456 | cpp-14-for-host | 14.2.0-19 | No fix yet | Per policy |
| Low | CVE-2025-10966 | curl | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2025-14017 | curl | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2025-14524 | curl | 8.14.1-2+deb13u3 | 8.14.1-2+deb13u4 | Per policy |
| Low | CVE-2025-14819 | curl | 8.14.1-2+deb13u3 | 8.14.1-2+deb13u4 | Per policy |
| Low | CVE-2025-15079 | curl | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2025-15224 | curl | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-107928 | curl | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-107929 | curl | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-13608 | curl | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-18924 | curl | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-80229 | curl | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-80230 | curl | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-80255 | curl | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-82208 | curl | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-82209 | curl | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-86409 | curl | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-86410 | curl | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-86414 | curl | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-87862 | curl | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-87863 | curl | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-87864 | curl | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-87865 | curl | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-87866 | curl | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-92386 | curl | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-92387 | curl | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-92389 | curl | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-92390 | curl | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-92391 | curl | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-94266 | curl | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-9547 | curl | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-102473 | dash | 0.5.12-12 | No fix yet | Per policy |
| Low | CVE-2026-102474 | dash | 0.5.12-12 | No fix yet | Per policy |
| Low | CVE-2026-128885 | dbus | 1.16.2-2 | No fix yet | Per policy |
| Low | CVE-2026-128885 | dbus-bin | 1.16.2-2 | No fix yet | Per policy |
| Low | CVE-2026-128885 | dbus-daemon | 1.16.2-2 | No fix yet | Per policy |
| Low | CVE-2026-128885 | dbus-session-bus-common | 1.16.2-2 | No fix yet | Per policy |
| Low | CVE-2026-128885 | dbus-system-bus-common | 1.16.2-2 | No fix yet | Per policy |
| Low | CVE-2026-128885 | dbus-user-session | 1.16.2-2 | No fix yet | Per policy |
| Low | CVE-2026-53910 | diffutils | 1:3.10-4 | No fix yet | Per policy |
| Low | CVE-2022-3219 | dirmngr | 2.4.7-21+deb13u1+b3 | No fix yet | Per policy |
| Low | CVE-2026-105712 | dirmngr | 2.4.7-21+deb13u1+b3 | No fix yet | Per policy |
| Low | CVE-2026-57062 | dirmngr | 2.4.7-21+deb13u1+b3 | No fix yet | Per policy |
| Low | CVE-2026-19617 | dmsetup | 2:1.02.205-2 | No fix yet | Per policy |
| Low | CVE-2026-12969 | dnsmasq-base | 2.91-1+deb13u1 | 2.91-1+deb13u2 | Per policy |
| Low | CVE-2026-93009 | dnsmasq-base | 2.91-1+deb13u1 | No fix yet | Per policy |
| Low | CVE-2022-0563 | eject | 2.41-5 | No fix yet | Per policy |
| Low | CVE-2025-14104 | eject | 2.41-5 | 2.41.3-1 | Per policy |
| Low | CVE-2022-0563 | fdisk | 2.41-5 | No fix yet | Per policy |
| Low | CVE-2025-14104 | fdisk | 2.41-5 | 2.41.3-1 | Per policy |
| Low | CVE-2026-115456 | g++-14 | 14.2.0-19 | No fix yet | Per policy |
| Low | CVE-2026-115456 | g++-14-aarch64-linux-gnu | 14.2.0-19 | No fix yet | Per policy |
| Low | CVE-2026-115456 | gcc-14 | 14.2.0-19 | No fix yet | Per policy |
| Low | CVE-2026-115456 | gcc-14-aarch64-linux-gnu | 14.2.0-19 | No fix yet | Per policy |
| Low | CVE-2026-115456 | gcc-14-base | 14.2.0-19 | No fix yet | Per policy |
| Low | CVE-2026-115456 | gcc-14-for-host | 14.2.0-19 | No fix yet | Per policy |
| Low | CVE-2014-8501 | gdb | 16.3-1 | No fix yet | Per policy |
| Low | CVE-2023-39128 | gdb | 16.3-1 | No fix yet | Per policy |
| Low | CVE-2023-39129 | gdb | 16.3-1 | No fix yet | Per policy |
| Low | CVE-2023-39130 | gdb | 16.3-1 | No fix yet | Per policy |
| Low | CVE-2026-121994 | gdb | 16.3-1 | No fix yet | Per policy |
| Low | CVE-2026-121995 | gdb | 16.3-1 | No fix yet | Per policy |
| Low | CVE-2026-121996 | gdb | 16.3-1 | No fix yet | Per policy |
| Low | CVE-2026-121997 | gdb | 16.3-1 | No fix yet | Per policy |
| Low | CVE-2026-123151 | gdb | 16.3-1 | No fix yet | Per policy |
| Low | CVE-2026-13732 | gdb | 16.3-1 | No fix yet | Per policy |
| Low | CVE-2022-3219 | gnupg | 2.4.7-21+deb13u1 | No fix yet | Per policy |
| Low | CVE-2026-105712 | gnupg | 2.4.7-21+deb13u1 | No fix yet | Per policy |
| Low | CVE-2026-57062 | gnupg | 2.4.7-21+deb13u1 | No fix yet | Per policy |
| Low | CVE-2022-3219 | gnupg-l10n | 2.4.7-21+deb13u1 | No fix yet | Per policy |
| Low | CVE-2026-105712 | gnupg-l10n | 2.4.7-21+deb13u1 | No fix yet | Per policy |
| Low | CVE-2026-57062 | gnupg-l10n | 2.4.7-21+deb13u1 | No fix yet | Per policy |
| Low | CVE-2022-3219 | gnupg-utils | 2.4.7-21+deb13u1+b3 | No fix yet | Per policy |
| Low | CVE-2026-105712 | gnupg-utils | 2.4.7-21+deb13u1+b3 | No fix yet | Per policy |
| Low | CVE-2026-57062 | gnupg-utils | 2.4.7-21+deb13u1+b3 | No fix yet | Per policy |
| Low | CVE-2022-3219 | gpg | 2.4.7-21+deb13u1+b3 | No fix yet | Per policy |
| Low | CVE-2026-105712 | gpg | 2.4.7-21+deb13u1+b3 | No fix yet | Per policy |
| Low | CVE-2026-57062 | gpg | 2.4.7-21+deb13u1+b3 | No fix yet | Per policy |
| Low | CVE-2022-3219 | gpg-agent | 2.4.7-21+deb13u1+b3 | No fix yet | Per policy |
| Low | CVE-2026-105712 | gpg-agent | 2.4.7-21+deb13u1+b3 | No fix yet | Per policy |
| Low | CVE-2026-57062 | gpg-agent | 2.4.7-21+deb13u1+b3 | No fix yet | Per policy |
| Low | CVE-2022-3219 | gpg-wks-client | 2.4.7-21+deb13u1+b3 | No fix yet | Per policy |
| Low | CVE-2026-105712 | gpg-wks-client | 2.4.7-21+deb13u1+b3 | No fix yet | Per policy |
| Low | CVE-2026-57062 | gpg-wks-client | 2.4.7-21+deb13u1+b3 | No fix yet | Per policy |
| Low | CVE-2022-3219 | gpgconf | 2.4.7-21+deb13u1+b3 | No fix yet | Per policy |
| Low | CVE-2026-105712 | gpgconf | 2.4.7-21+deb13u1+b3 | No fix yet | Per policy |
| Low | CVE-2026-57062 | gpgconf | 2.4.7-21+deb13u1+b3 | No fix yet | Per policy |
| Low | CVE-2022-3219 | gpgsm | 2.4.7-21+deb13u1+b3 | No fix yet | Per policy |
| Low | CVE-2026-105712 | gpgsm | 2.4.7-21+deb13u1+b3 | No fix yet | Per policy |
| Low | CVE-2026-57062 | gpgsm | 2.4.7-21+deb13u1+b3 | No fix yet | Per policy |
| Low | CVE-2022-3219 | gpgv | 2.4.7-21+deb13u1+b3 | No fix yet | Per policy |
| Low | CVE-2026-105712 | gpgv | 2.4.7-21+deb13u1+b3 | No fix yet | Per policy |
| Low | CVE-2026-57062 | gpgv | 2.4.7-21+deb13u1+b3 | No fix yet | Per policy |
| Low | CVE-2008-4996 | initramfs-tools | 0.148.4+rpt2 | No fix yet | Per policy |
| Low | CVE-2008-4996 | initramfs-tools-bin | 0.148.4+rpt2 | No fix yet | Per policy |
| Low | CVE-2008-4996 | initramfs-tools-core | 0.148.4+rpt2 | No fix yet | Per policy |
| Low | CVE-2025-47268 | iputils-arping | 3:20240905-3 | No fix yet | Per policy |
| Low | CVE-2025-47268 | iputils-ping | 3:20240905-3 | No fix yet | Per policy |
| Low | CVE-2011-3374 | libapt-pkg7.0 | 3.0.3 | No fix yet | Per policy |
| Low | CVE-2026-115456 | libasan8 | 14.2.0-19 | No fix yet | Per policy |
| Low | CVE-2026-56109 | libasound2-data | 1.2.14-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-56109 | libasound2t64 | 1.2.14-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-115456 | libatomic1 | 14.2.0-19 | No fix yet | Per policy |
| Low | CVE-2026-56109 | libatopology2t64 | 1.2.14-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2017-13716 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2018-20673 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2018-20712 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2018-9996 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2021-32256 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11081 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11082 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11083 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11412 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11413 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11414 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1147 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1148 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1149 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11494 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11495 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1150 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1151 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1152 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1153 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1176 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1178 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1180 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1181 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1182 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11839 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11840 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-3198 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-5244 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-5245 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-66861 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-66862 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-66863 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-66864 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-66865 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-66866 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69644 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69645 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69646 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69647 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69648 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69649 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69650 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69651 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69652 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-7545 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-7546 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-8225 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-15003 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-18220 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-19548 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-3441 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-3442 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-4647 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-6844 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-6845 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-6846 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90801 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90802 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90803 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90804 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90828 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90829 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90830 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90831 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-91779 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-91780 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-91781 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-91782 | libbinutils | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2022-0563 | libblkid1 | 2.41-5 | No fix yet | Per policy |
| Low | CVE-2025-14104 | libblkid1 | 2.41-5 | 2.41.3-1 | Per policy |
| Low | CVE-2026-111581 | libblockdev-crypto3 | 3.3.0-2.1 | No fix yet | Per policy |
| Low | CVE-2026-111581 | libblockdev-fs3 | 3.3.0-2.1 | No fix yet | Per policy |
| Low | CVE-2026-111581 | libblockdev-loop3 | 3.3.0-2.1 | No fix yet | Per policy |
| Low | CVE-2026-111581 | libblockdev-mdraid3 | 3.3.0-2.1 | No fix yet | Per policy |
| Low | CVE-2026-111581 | libblockdev-nvme3 | 3.3.0-2.1 | No fix yet | Per policy |
| Low | CVE-2026-111581 | libblockdev-part3 | 3.3.0-2.1 | No fix yet | Per policy |
| Low | CVE-2026-111581 | libblockdev-swap3 | 3.3.0-2.1 | No fix yet | Per policy |
| Low | CVE-2026-111581 | libblockdev-utils3 | 3.3.0-2.1 | No fix yet | Per policy |
| Low | CVE-2026-111581 | libblockdev3 | 3.3.0-2.1 | No fix yet | Per policy |
| Low | CVE-2016-9797 | libbluetooth3 | 5.82-1.1+rpt1 | No fix yet | Per policy |
| Low | CVE-2016-9798 | libbluetooth3 | 5.82-1.1+rpt1 | No fix yet | Per policy |
| Low | CVE-2016-9799 | libbluetooth3 | 5.82-1.1+rpt1 | No fix yet | Per policy |
| Low | CVE-2016-9800 | libbluetooth3 | 5.82-1.1+rpt1 | No fix yet | Per policy |
| Low | CVE-2016-9801 | libbluetooth3 | 5.82-1.1+rpt1 | No fix yet | Per policy |
| Low | CVE-2016-9802 | libbluetooth3 | 5.82-1.1+rpt1 | No fix yet | Per policy |
| Low | CVE-2016-9803 | libbluetooth3 | 5.82-1.1+rpt1 | No fix yet | Per policy |
| Low | CVE-2016-9804 | libbluetooth3 | 5.82-1.1+rpt1 | No fix yet | Per policy |
| Low | CVE-2016-9917 | libbluetooth3 | 5.82-1.1+rpt1 | No fix yet | Per policy |
| Low | CVE-2016-9918 | libbluetooth3 | 5.82-1.1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-105460 | libbluetooth3 | 5.82-1.1+rpt1 | No fix yet | Per policy |
| Low | CVE-2010-4756 | libc-bin | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2018-20796 | libc-bin | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2019-1010022 | libc-bin | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2019-1010023 | libc-bin | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2019-1010024 | libc-bin | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2019-1010025 | libc-bin | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2019-9192 | libc-bin | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-100290 | libc-bin | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-126765 | libc-bin | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2010-4756 | libc-dev-bin | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2018-20796 | libc-dev-bin | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2019-1010022 | libc-dev-bin | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2019-1010023 | libc-dev-bin | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2019-1010024 | libc-dev-bin | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2019-1010025 | libc-dev-bin | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2019-9192 | libc-dev-bin | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-100290 | libc-dev-bin | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-126765 | libc-dev-bin | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2010-4756 | libc-l10n | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2018-20796 | libc-l10n | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2019-1010022 | libc-l10n | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2019-1010023 | libc-l10n | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2019-1010024 | libc-l10n | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2019-1010025 | libc-l10n | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2019-9192 | libc-l10n | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-100290 | libc-l10n | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-126765 | libc-l10n | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2010-4756 | libc6 | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2018-20796 | libc6 | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2019-1010022 | libc6 | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2019-1010023 | libc6 | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2019-1010024 | libc6 | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2019-1010025 | libc6 | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2019-9192 | libc6 | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-100290 | libc6 | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-126765 | libc6 | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2010-4756 | libc6-dev | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2018-20796 | libc6-dev | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2019-1010022 | libc6-dev | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2019-1010023 | libc6-dev | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2019-1010024 | libc6-dev | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2019-1010025 | libc6-dev | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2019-9192 | libc6-dev | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-100290 | libc6-dev | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-126765 | libc6-dev | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-115456 | libcc1-0 | 14.2.0-19 | No fix yet | Per policy |
| Low | CVE-2017-13716 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2018-20673 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2018-20712 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2018-9996 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2021-32256 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11081 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11082 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11083 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11412 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11413 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11414 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1147 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1148 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1149 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11494 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11495 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1150 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1151 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1152 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1153 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1176 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1178 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1180 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1181 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1182 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11839 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11840 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-3198 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-5244 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-5245 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-66861 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-66862 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-66863 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-66864 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-66865 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-66866 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69644 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69645 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69646 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69647 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69648 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69649 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69650 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69651 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69652 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-7545 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-7546 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-8225 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-15003 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-18220 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-19548 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-3441 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-3442 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-4647 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-6844 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-6845 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-6846 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90801 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90802 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90803 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90804 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90828 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90829 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90830 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90831 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-91779 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-91780 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-91781 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-91782 | libctf-nobfd0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2017-13716 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2018-20673 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2018-20712 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2018-9996 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2021-32256 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11081 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11082 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11083 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11412 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11413 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11414 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1147 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1148 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1149 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11494 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11495 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1150 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1151 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1152 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1153 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1176 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1178 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1180 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1181 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1182 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11839 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11840 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-3198 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-5244 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-5245 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-66861 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-66862 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-66863 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-66864 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-66865 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-66866 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69644 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69645 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69646 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69647 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69648 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69649 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69650 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69651 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69652 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-7545 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-7546 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-8225 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-15003 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-18220 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-19548 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-3441 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-3442 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-4647 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-6844 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-6845 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-6846 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90801 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90802 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90803 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90804 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90828 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90829 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90830 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90831 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-91779 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-91780 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-91781 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-91782 | libctf0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-10966 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2025-14017 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2025-14524 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | 8.14.1-2+deb13u4 | Per policy |
| Low | CVE-2025-14819 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | 8.14.1-2+deb13u4 | Per policy |
| Low | CVE-2025-15079 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2025-15224 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-107928 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-107929 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-13608 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-18924 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-80229 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-80230 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-80255 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-82208 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-82209 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-86409 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-86410 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-86414 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-87862 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-87863 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-87864 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-87865 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-87866 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-92386 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-92387 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-92389 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-92390 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-92391 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-94266 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-9547 | libcurl3t64-gnutls | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2025-10966 | libcurl4t64 | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2025-14017 | libcurl4t64 | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2025-14524 | libcurl4t64 | 8.14.1-2+deb13u3 | 8.14.1-2+deb13u4 | Per policy |
| Low | CVE-2025-14819 | libcurl4t64 | 8.14.1-2+deb13u3 | 8.14.1-2+deb13u4 | Per policy |
| Low | CVE-2025-15079 | libcurl4t64 | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2025-15224 | libcurl4t64 | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-107928 | libcurl4t64 | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-107929 | libcurl4t64 | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-13608 | libcurl4t64 | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-18924 | libcurl4t64 | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-80229 | libcurl4t64 | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-80230 | libcurl4t64 | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-80255 | libcurl4t64 | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-82208 | libcurl4t64 | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-82209 | libcurl4t64 | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-86409 | libcurl4t64 | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-86410 | libcurl4t64 | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-86414 | libcurl4t64 | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-87862 | libcurl4t64 | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-87863 | libcurl4t64 | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-87864 | libcurl4t64 | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-87865 | libcurl4t64 | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-87866 | libcurl4t64 | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-92386 | libcurl4t64 | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-92387 | libcurl4t64 | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-92389 | libcurl4t64 | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-92390 | libcurl4t64 | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-92391 | libcurl4t64 | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-94266 | libcurl4t64 | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-9547 | libcurl4t64 | 8.14.1-2+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-128885 | libdbus-1-3 | 1.16.2-2 | No fix yet | Per policy |
| Low | CVE-2024-25260 | libdebuginfod-common | 0.192-4 | No fix yet | Per policy |
| Low | CVE-2025-1352 | libdebuginfod-common | 0.192-4 | No fix yet | Per policy |
| Low | CVE-2025-1365 | libdebuginfod-common | 0.192-4 | No fix yet | Per policy |
| Low | CVE-2025-1371 | libdebuginfod-common | 0.192-4 | No fix yet | Per policy |
| Low | CVE-2025-1372 | libdebuginfod-common | 0.192-4 | No fix yet | Per policy |
| Low | CVE-2025-1376 | libdebuginfod-common | 0.192-4 | No fix yet | Per policy |
| Low | CVE-2025-1377 | libdebuginfod-common | 0.192-4 | No fix yet | Per policy |
| Low | CVE-2024-25260 | libdebuginfod1t64 | 0.192-4 | No fix yet | Per policy |
| Low | CVE-2025-1352 | libdebuginfod1t64 | 0.192-4 | No fix yet | Per policy |
| Low | CVE-2025-1365 | libdebuginfod1t64 | 0.192-4 | No fix yet | Per policy |
| Low | CVE-2025-1371 | libdebuginfod1t64 | 0.192-4 | No fix yet | Per policy |
| Low | CVE-2025-1372 | libdebuginfod1t64 | 0.192-4 | No fix yet | Per policy |
| Low | CVE-2025-1376 | libdebuginfod1t64 | 0.192-4 | No fix yet | Per policy |
| Low | CVE-2025-1377 | libdebuginfod1t64 | 0.192-4 | No fix yet | Per policy |
| Low | CVE-2026-19617 | libdevmapper1.02.1 | 2:1.02.205-2 | No fix yet | Per policy |
| Low | CVE-2024-25260 | libdw1t64 | 0.192-4 | No fix yet | Per policy |
| Low | CVE-2025-1352 | libdw1t64 | 0.192-4 | No fix yet | Per policy |
| Low | CVE-2025-1365 | libdw1t64 | 0.192-4 | No fix yet | Per policy |
| Low | CVE-2025-1371 | libdw1t64 | 0.192-4 | No fix yet | Per policy |
| Low | CVE-2025-1372 | libdw1t64 | 0.192-4 | No fix yet | Per policy |
| Low | CVE-2025-1376 | libdw1t64 | 0.192-4 | No fix yet | Per policy |
| Low | CVE-2025-1377 | libdw1t64 | 0.192-4 | No fix yet | Per policy |
| Low | CVE-2024-25260 | libelf1t64 | 0.192-4 | No fix yet | Per policy |
| Low | CVE-2025-1352 | libelf1t64 | 0.192-4 | No fix yet | Per policy |
| Low | CVE-2025-1365 | libelf1t64 | 0.192-4 | No fix yet | Per policy |
| Low | CVE-2025-1371 | libelf1t64 | 0.192-4 | No fix yet | Per policy |
| Low | CVE-2025-1372 | libelf1t64 | 0.192-4 | No fix yet | Per policy |
| Low | CVE-2025-1376 | libelf1t64 | 0.192-4 | No fix yet | Per policy |
| Low | CVE-2025-1377 | libelf1t64 | 0.192-4 | No fix yet | Per policy |
| Low | CVE-2026-24515 | libexpat1 | 2.7.1-2 | 2.8.2-1~deb13u1 | Per policy |
| Low | CVE-2026-41080 | libexpat1 | 2.7.1-2 | 2.8.2-1~deb13u1 | Per policy |
| Low | CVE-2022-0563 | libfdisk1 | 2.41-5 | No fix yet | Per policy |
| Low | CVE-2025-14104 | libfdisk1 | 2.41-5 | 2.41.3-1 | Per policy |
| Low | CVE-2026-115456 | libgcc-14-dev | 14.2.0-19 | No fix yet | Per policy |
| Low | CVE-2026-115456 | libgcc-s1 | 14.2.0-19 | No fix yet | Per policy |
| Low | CVE-2018-6829 | libgcrypt20 | 1.11.0-7+deb13u1 | No fix yet | Per policy |
| Low | CVE-2024-2236 | libgcrypt20 | 1.11.0-7+deb13u1 | No fix yet | Per policy |
| Low | CVE-2012-0039 | libglib2.0-0t64 | 2.84.4-3~deb13u3 | No fix yet | Per policy |
| Low | CVE-2012-0039 | libglib2.0-data | 2.84.4-3~deb13u3 | No fix yet | Per policy |
| Low | CVE-2011-3389 | libgnutls30t64 | 3.8.9-3+deb13u4 | No fix yet | Per policy |
| Low | CVE-2026-67693 | libgnutls30t64 | 3.8.9-3+deb13u4 | No fix yet | Per policy |
| Low | CVE-2026-88647 | libgnutls30t64 | 3.8.9-3+deb13u4 | No fix yet | Per policy |
| Low | CVE-2026-88648 | libgnutls30t64 | 3.8.9-3+deb13u4 | No fix yet | Per policy |
| Low | CVE-2026-95184 | libgnutls30t64 | 3.8.9-3+deb13u4 | No fix yet | Per policy |
| Low | CVE-2026-95210 | libgnutls30t64 | 3.8.9-3+deb13u4 | No fix yet | Per policy |
| Low | CVE-2026-115456 | libgomp1 | 14.2.0-19 | No fix yet | Per policy |
| Low | CVE-2017-13716 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2018-20673 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2018-20712 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2018-9996 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2021-32256 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11081 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11082 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11083 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11412 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11413 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11414 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1147 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1148 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1149 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11494 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11495 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1150 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1151 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1152 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1153 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1176 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1178 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1180 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1181 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1182 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11839 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11840 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-3198 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-5244 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-5245 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-66861 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-66862 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-66863 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-66864 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-66865 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-66866 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69644 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69645 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69646 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69647 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69648 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69649 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69650 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69651 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69652 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-7545 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-7546 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-8225 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-15003 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-18220 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-19548 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-3441 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-3442 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-4647 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-6844 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-6845 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-6846 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90801 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90802 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90803 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90804 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90828 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90829 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90830 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90831 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-91779 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-91780 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-91781 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-91782 | libgprofng0 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2018-5709 | libgssapi-krb5-2 | 1.21.3-5+deb13u1 | No fix yet | Per policy |
| Low | CVE-2024-26458 | libgssapi-krb5-2 | 1.21.3-5+deb13u1 | No fix yet | Per policy |
| Low | CVE-2024-26461 | libgssapi-krb5-2 | 1.21.3-5+deb13u1 | No fix yet | Per policy |
| Low | CVE-2026-11850 | libgssapi-krb5-2 | 1.21.3-5+deb13u1 | No fix yet | Per policy |
| Low | CVE-2026-115456 | libhwasan0 | 14.2.0-19 | No fix yet | Per policy |
| Low | CVE-2026-115456 | libitm1 | 14.2.0-19 | No fix yet | Per policy |
| Low | CVE-2017-9937 | libjbig0 | 2.1-6.1+b2 | No fix yet | Per policy |
| Low | CVE-2018-5709 | libk5crypto3 | 1.21.3-5+deb13u1 | No fix yet | Per policy |
| Low | CVE-2024-26458 | libk5crypto3 | 1.21.3-5+deb13u1 | No fix yet | Per policy |
| Low | CVE-2024-26461 | libk5crypto3 | 1.21.3-5+deb13u1 | No fix yet | Per policy |
| Low | CVE-2026-11850 | libk5crypto3 | 1.21.3-5+deb13u1 | No fix yet | Per policy |
| Low | CVE-2018-5709 | libkrb5-3 | 1.21.3-5+deb13u1 | No fix yet | Per policy |
| Low | CVE-2024-26458 | libkrb5-3 | 1.21.3-5+deb13u1 | No fix yet | Per policy |
| Low | CVE-2024-26461 | libkrb5-3 | 1.21.3-5+deb13u1 | No fix yet | Per policy |
| Low | CVE-2026-11850 | libkrb5-3 | 1.21.3-5+deb13u1 | No fix yet | Per policy |
| Low | CVE-2018-5709 | libkrb5support0 | 1.21.3-5+deb13u1 | No fix yet | Per policy |
| Low | CVE-2024-26458 | libkrb5support0 | 1.21.3-5+deb13u1 | No fix yet | Per policy |
| Low | CVE-2024-26461 | libkrb5support0 | 1.21.3-5+deb13u1 | No fix yet | Per policy |
| Low | CVE-2026-11850 | libkrb5support0 | 1.21.3-5+deb13u1 | No fix yet | Per policy |
| Low | CVE-2022-0563 | liblastlog2-2 | 2.41-5 | No fix yet | Per policy |
| Low | CVE-2025-14104 | liblastlog2-2 | 2.41-5 | 2.41.3-1 | Per policy |
| Low | CVE-2015-3276 | libldap-common | 2.6.10+dfsg-1 | No fix yet | Per policy |
| Low | CVE-2017-14159 | libldap-common | 2.6.10+dfsg-1 | No fix yet | Per policy |
| Low | CVE-2017-17740 | libldap-common | 2.6.10+dfsg-1 | No fix yet | Per policy |
| Low | CVE-2020-15719 | libldap-common | 2.6.10+dfsg-1 | No fix yet | Per policy |
| Low | CVE-2026-22185 | libldap-common | 2.6.10+dfsg-1 | No fix yet | Per policy |
| Low | CVE-2015-3276 | libldap2 | 2.6.10+dfsg-1 | No fix yet | Per policy |
| Low | CVE-2017-14159 | libldap2 | 2.6.10+dfsg-1 | No fix yet | Per policy |
| Low | CVE-2017-17740 | libldap2 | 2.6.10+dfsg-1 | No fix yet | Per policy |
| Low | CVE-2020-15719 | libldap2 | 2.6.10+dfsg-1 | No fix yet | Per policy |
| Low | CVE-2026-22185 | libldap2 | 2.6.10+dfsg-1 | No fix yet | Per policy |
| Low | CVE-2026-115456 | liblsan0 | 14.2.0-19 | No fix yet | Per policy |
| Low | CVE-2022-0563 | libmount1 | 2.41-5 | No fix yet | Per policy |
| Low | CVE-2025-14104 | libmount1 | 2.41-5 | 2.41.3-1 | Per policy |
| Low | CVE-2025-6141 | libncursesw6 | 6.5+20250216-2 | No fix yet | Per policy |
| Low | CVE-2025-9615 | libnm0 | 1.52.1-1+rpt4 | No fix yet | Per policy |
| Low | CVE-2017-11695 | libnss3 | 2:3.110-1+deb13u2 | No fix yet | Per policy |
| Low | CVE-2017-11696 | libnss3 | 2:3.110-1+deb13u2 | No fix yet | Per policy |
| Low | CVE-2017-11697 | libnss3 | 2:3.110-1+deb13u2 | No fix yet | Per policy |
| Low | CVE-2017-11698 | libnss3 | 2:3.110-1+deb13u2 | No fix yet | Per policy |
| Low | CVE-2026-12318 | libnss3 | 2:3.110-1+deb13u2 | 2:3.110-1+deb13u3 | Per policy |
| Low | CVE-2013-4392 | libpam-systemd | 257.13-1~deb13u1 | No fix yet | Per policy |
| Low | CVE-2023-31437 | libpam-systemd | 257.13-1~deb13u1 | No fix yet | Per policy |
| Low | CVE-2023-31438 | libpam-systemd | 257.13-1~deb13u1 | No fix yet | Per policy |
| Low | CVE-2023-31439 | libpam-systemd | 257.13-1~deb13u1 | No fix yet | Per policy |
| Low | CVE-2026-40228 | libpam-systemd | 257.13-1~deb13u1 | No fix yet | Per policy |
| Low | CVE-2025-11961 | libpcap0.8t64 | 1.10.5-2 | No fix yet | Per policy |
| Low | CVE-2026-18238 | libpcap0.8t64 | 1.10.5-2 | No fix yet | Per policy |
| Low | CVE-2026-18313 | libpcap0.8t64 | 1.10.5-2 | No fix yet | Per policy |
| Low | CVE-2026-89162 | libpcre2-16-0 | 10.46-1~deb13u1 | 10.46-1~deb13u2 | Per policy |
| Low | CVE-2026-89162 | libpcre2-8-0 | 10.46-1~deb13u1 | 10.46-1~deb13u2 | Per policy |
| Low | CVE-2011-4116 | libperl5.40 | 5.40.1-6 | No fix yet | Per policy |
| Low | CVE-2021-4214 | libpng16-16t64 | 1.6.48-1+deb13u5 | No fix yet | Per policy |
| Low | CVE-2026-3713 | libpng16-16t64 | 1.6.48-1+deb13u5 | No fix yet | Per policy |
| Low | CVE-2025-7519 | libpolkit-agent-1-0 | 126-2 | No fix yet | Per policy |
| Low | CVE-2025-7519 | libpolkit-gobject-1-0 | 126-2 | No fix yet | Per policy |
| Low | CVE-2026-18739 | libpopt0 | 1.19+dfsg-2 | No fix yet | Per policy |
| Low | CVE-2026-18743 | libpopt0 | 1.19+dfsg-2 | No fix yet | Per policy |
| Low | CVE-2026-18839 | libpopt0 | 1.19+dfsg-2 | No fix yet | Per policy |
| Low | CVE-2026-115557 | libpython3.13 | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Low | CVE-2026-115559 | libpython3.13 | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Low | CVE-2026-12003 | libpython3.13 | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Low | CVE-2026-18503 | libpython3.13 | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Low | CVE-2026-3479 | libpython3.13 | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Low | CVE-2026-6879 | libpython3.13 | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u5 | Per policy |
| Low | CVE-2026-115557 | libpython3.13-minimal | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Low | CVE-2026-115559 | libpython3.13-minimal | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Low | CVE-2026-12003 | libpython3.13-minimal | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Low | CVE-2026-18503 | libpython3.13-minimal | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Low | CVE-2026-3479 | libpython3.13-minimal | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Low | CVE-2026-6879 | libpython3.13-minimal | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u5 | Per policy |
| Low | CVE-2026-115557 | libpython3.13-stdlib | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Low | CVE-2026-115559 | libpython3.13-stdlib | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Low | CVE-2026-12003 | libpython3.13-stdlib | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Low | CVE-2026-18503 | libpython3.13-stdlib | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Low | CVE-2026-3479 | libpython3.13-stdlib | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Low | CVE-2026-6879 | libpython3.13-stdlib | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u5 | Per policy |
| Low | CVE-2023-45935 | libqt6core6t64 | 6.8.2+dfsg-9+deb13u2 | No fix yet | Per policy |
| Low | CVE-2026-107157 | libqt6core6t64 | 6.8.2+dfsg-9+deb13u2 | No fix yet | Per policy |
| Low | CVE-2026-116337 | libqt6core6t64 | 6.8.2+dfsg-9+deb13u2 | No fix yet | Per policy |
| Low | CVE-2026-129483 | libsasl2-2 | 2.1.28+dfsg1-9 | No fix yet | Per policy |
| Low | CVE-2026-129483 | libsasl2-modules | 2.1.28+dfsg1-9 | No fix yet | Per policy |
| Low | CVE-2026-129483 | libsasl2-modules-db | 2.1.28+dfsg1-9 | No fix yet | Per policy |
| Low | CVE-2017-13716 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2018-20673 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2018-20712 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2018-9996 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2021-32256 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11081 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11082 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11083 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11412 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11413 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11414 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1147 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1148 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1149 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11494 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11495 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1150 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1151 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1152 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1153 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1176 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1178 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1180 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1181 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-1182 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11839 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-11840 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-3198 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-5244 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-5245 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-66861 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-66862 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-66863 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-66864 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-66865 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-66866 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69644 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69645 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69646 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69647 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69648 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69649 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69650 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69651 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-69652 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-7545 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-7546 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2025-8225 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-15003 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-18220 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-19548 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-3441 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-3442 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-4647 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-6844 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-6845 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-6846 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90801 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90802 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90803 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90804 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90828 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90829 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90830 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-90831 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-91779 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-91780 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-91781 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2026-91782 | libsframe1 | 2.44-3 | No fix yet | Per policy |
| Low | CVE-2023-45927 | libslang2 | 2.3.3-5+b2 | No fix yet | Per policy |
| Low | CVE-2023-45929 | libslang2 | 2.3.3-5+b2 | No fix yet | Per policy |
| Low | CVE-2022-0563 | libsmartcols1 | 2.41-5 | No fix yet | Per policy |
| Low | CVE-2025-14104 | libsmartcols1 | 2.41-5 | 2.41.3-1 | Per policy |
| Low | CVE-2021-45346 | libsqlite3-0 | 3.46.1-7+deb13u1 | No fix yet | Per policy |
| Low | CVE-2025-70873 | libsqlite3-0 | 3.46.1-7+deb13u1 | No fix yet | Per policy |
| Low | CVE-2026-119377 | libsqlite3-0 | 3.46.1-7+deb13u1 | No fix yet | Per policy |
| Low | CVE-2026-107493 | libssl3t64 | 3.5.6-1~deb13u2+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-121481 | libssl3t64 | 3.5.6-1~deb13u2+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-14457 | libssl3t64 | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u2 | Per policy |
| Low | CVE-2026-35189 | libssl3t64 | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u3 | Per policy |
| Low | CVE-2026-35191 | libssl3t64 | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u3 | Per policy |
| Low | CVE-2026-54874 | libssl3t64 | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u2 | Per policy |
| Low | CVE-2026-63073 | libssl3t64 | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u2 | Per policy |
| Low | CVE-2026-63074 | libssl3t64 | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u2 | Per policy |
| Low | CVE-2026-63075 | libssl3t64 | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u2 | Per policy |
| Low | CVE-2026-75803 | libssl3t64 | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u2 | Per policy |
| Low | CVE-2026-88822 | libssl3t64 | 3.5.6-1~deb13u2+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-88823 | libssl3t64 | 3.5.6-1~deb13u2+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-115456 | libstdc++-14-dev | 14.2.0-19 | No fix yet | Per policy |
| Low | CVE-2026-115456 | libstdc++6 | 14.2.0-19 | No fix yet | Per policy |
| Low | CVE-2013-4392 | libsystemd-shared | 257.13-1~deb13u1 | No fix yet | Per policy |
| Low | CVE-2023-31437 | libsystemd-shared | 257.13-1~deb13u1 | No fix yet | Per policy |
| Low | CVE-2023-31438 | libsystemd-shared | 257.13-1~deb13u1 | No fix yet | Per policy |
| Low | CVE-2023-31439 | libsystemd-shared | 257.13-1~deb13u1 | No fix yet | Per policy |
| Low | CVE-2026-40228 | libsystemd-shared | 257.13-1~deb13u1 | No fix yet | Per policy |
| Low | CVE-2013-4392 | libsystemd0 | 257.13-1~deb13u1 | No fix yet | Per policy |
| Low | CVE-2023-31437 | libsystemd0 | 257.13-1~deb13u1 | No fix yet | Per policy |
| Low | CVE-2023-31438 | libsystemd0 | 257.13-1~deb13u1 | No fix yet | Per policy |
| Low | CVE-2023-31439 | libsystemd0 | 257.13-1~deb13u1 | No fix yet | Per policy |
| Low | CVE-2026-40228 | libsystemd0 | 257.13-1~deb13u1 | No fix yet | Per policy |
| Low | CVE-2025-13151 | libtasn1-6 | 4.20.0-2 | 4.20.0-2+deb13u1 | Per policy |
| Low | CVE-2017-16232 | libtiff6 | 4.7.0-3+deb13u2 | No fix yet | Per policy |
| Low | CVE-2018-10126 | libtiff6 | 4.7.0-3+deb13u2 | No fix yet | Per policy |
| Low | CVE-2022-1210 | libtiff6 | 4.7.0-3+deb13u2 | No fix yet | Per policy |
| Low | CVE-2025-61143 | libtiff6 | 4.7.0-3+deb13u2 | No fix yet | Per policy |
| Low | CVE-2025-61144 | libtiff6 | 4.7.0-3+deb13u2 | No fix yet | Per policy |
| Low | CVE-2025-61145 | libtiff6 | 4.7.0-3+deb13u2 | No fix yet | Per policy |
| Low | CVE-2025-8176 | libtiff6 | 4.7.0-3+deb13u2 | No fix yet | Per policy |
| Low | CVE-2025-8177 | libtiff6 | 4.7.0-3+deb13u2 | No fix yet | Per policy |
| Low | CVE-2025-8534 | libtiff6 | 4.7.0-3+deb13u2 | No fix yet | Per policy |
| Low | CVE-2026-52491 | libtiff6 | 4.7.0-3+deb13u2 | No fix yet | Per policy |
| Low | CVE-2026-52492 | libtiff6 | 4.7.0-3+deb13u2 | No fix yet | Per policy |
| Low | CVE-2025-6141 | libtinfo6 | 6.5+20250216-2 | No fix yet | Per policy |
| Low | CVE-2026-115456 | libtsan2 | 14.2.0-19 | No fix yet | Per policy |
| Low | CVE-2026-115456 | libubsan1 | 14.2.0-19 | No fix yet | Per policy |
| Low | CVE-2013-4392 | libudev1 | 257.13-1~deb13u1 | No fix yet | Per policy |
| Low | CVE-2023-31437 | libudev1 | 257.13-1~deb13u1 | No fix yet | Per policy |
| Low | CVE-2023-31438 | libudev1 | 257.13-1~deb13u1 | No fix yet | Per policy |
| Low | CVE-2023-31439 | libudev1 | 257.13-1~deb13u1 | No fix yet | Per policy |
| Low | CVE-2026-40228 | libudev1 | 257.13-1~deb13u1 | No fix yet | Per policy |
| Low | CVE-2022-0563 | libuuid1 | 2.41-5 | No fix yet | Per policy |
| Low | CVE-2025-14104 | libuuid1 | 2.41-5 | 2.41.3-1 | Per policy |
| Low | CVE-2025-8732 | libxml2 | 2.12.7+dfsg+really2.9.14-2.1+deb13u2 | 2.12.7+dfsg+really2.9.14-2.1+deb13u3 | Per policy |
| Low | CVE-2026-0989 | libxml2 | 2.12.7+dfsg+really2.9.14-2.1+deb13u2 | 2.12.7+dfsg+really2.9.14-2.1+deb13u3 | Per policy |
| Low | CVE-2026-0992 | libxml2 | 2.12.7+dfsg+really2.9.14-2.1+deb13u2 | 2.12.7+dfsg+really2.9.14-2.1+deb13u3 | Per policy |
| Low | CVE-2026-11979 | libxml2 | 2.12.7+dfsg+really2.9.14-2.1+deb13u2 | No fix yet | Per policy |
| Low | CVE-2026-1757 | libxml2 | 2.12.7+dfsg+really2.9.14-2.1+deb13u2 | 2.12.7+dfsg+really2.9.14-2.1+deb13u3 | Per policy |
| Low | CVE-2026-86141 | libxml2 | 2.12.7+dfsg+really2.9.14-2.1+deb13u2 | No fix yet | Per policy |
| Low | CVE-2012-2663 | libxtables12 | 1.8.11-2 | No fix yet | Per policy |
| Low | CVE-2004-0230 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2005-3660 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2007-3719 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2008-2544 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2008-4609 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2010-4563 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2010-5321 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2011-4915 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2011-4916 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2011-4917 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2012-4542 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2014-9892 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2014-9900 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2015-2877 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2016-10723 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2016-8660 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2017-0630 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2017-13693 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2017-13694 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2018-1121 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2018-12928 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2018-17977 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-11191 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12378 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12379 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12380 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12381 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12382 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12455 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12456 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16229 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16230 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16231 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16232 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16233 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16234 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-19070 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-19378 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2020-11725 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2020-35501 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2021-26934 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2021-3714 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-0400 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-1247 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-25265 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-2961 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-3238 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-41848 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-44032 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-44033 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-4543 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-45884 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-45885 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-23039 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-26242 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-31081 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-31085 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-3640 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2024-0564 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2025-40025 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2025-68751 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-31536 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-74560 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-89862 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-90211 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-90261 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-90306 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-92493 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98285 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98289 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98304 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98317 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98321 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98332 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98338 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98389 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98393 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98424 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98427 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98431 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98436 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98551 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98628 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98802 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98874 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98929 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98951 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98966 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99348 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99349 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99376 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99381 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99382 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99496 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99569 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99575 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99579 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99594 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99599 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99607 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99610 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99615 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99622 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99628 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99689 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99704 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99711 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99723 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99741 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99759 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99778 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99779 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | TEMP-0000000-F7A20F | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2004-0230 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2005-3660 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2007-3719 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2008-2544 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2008-4609 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2010-4563 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2010-5321 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2011-4915 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2011-4916 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2011-4917 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2012-4542 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2014-9892 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2014-9900 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2015-2877 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2016-10723 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2016-8660 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2017-0630 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2017-13693 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2017-13694 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2018-1121 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2018-12928 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2018-17977 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-11191 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12378 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12379 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12380 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12381 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12382 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12455 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12456 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16229 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16230 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16231 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16232 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16233 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16234 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-19070 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-19378 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2020-11725 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2020-35501 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2021-26934 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2021-3714 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-0400 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-1247 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-25265 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-2961 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-3238 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-41848 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-44032 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-44033 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-4543 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-45884 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-45885 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-23039 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-26242 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-31081 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-31085 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-3640 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2024-0564 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2025-40025 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2025-68751 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-31536 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-74560 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-89862 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-90211 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-90261 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-90306 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-92493 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98285 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98289 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98304 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98317 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98321 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98332 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98338 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98389 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98393 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98424 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98427 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98431 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98436 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98551 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98628 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98802 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98874 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98929 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98951 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98966 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99348 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99349 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99376 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99381 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99382 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99496 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99569 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99575 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99579 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99594 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99599 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99607 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99610 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99615 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99622 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99628 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99689 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99704 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99711 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99723 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99741 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99759 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99778 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99779 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | TEMP-0000000-F7A20F | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2004-0230 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2005-3660 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2007-3719 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2008-2544 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2008-4609 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2010-4563 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2010-5321 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2011-4915 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2011-4916 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2011-4917 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2012-4542 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2014-9892 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2014-9900 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2015-2877 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2016-10723 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2016-8660 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2017-0630 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2017-13693 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2017-13694 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2018-1121 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2018-12928 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2018-17977 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-11191 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12378 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12379 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12380 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12381 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12382 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12455 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12456 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16229 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16230 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16231 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16232 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16233 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16234 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-19070 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-19378 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2020-11725 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2020-35501 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2021-26934 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2021-3714 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-0400 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-1247 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-25265 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-2961 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-3238 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-41848 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-44032 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-44033 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-4543 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-45884 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-45885 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-23039 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-26242 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-31081 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-31085 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-3640 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2024-0564 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2025-40025 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2025-68751 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-31536 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-74560 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-89862 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-90211 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-90261 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-90306 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-92493 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98285 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98289 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98304 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98317 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98321 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98332 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98338 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98389 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98393 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98424 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98427 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98431 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98436 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98551 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98628 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98802 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98874 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98929 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98951 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98966 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99348 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99349 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99376 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99381 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99382 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99496 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99569 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99575 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99579 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99594 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99599 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99607 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99610 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99615 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99622 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99628 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99689 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99704 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99711 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99723 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99741 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99759 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99778 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99779 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | TEMP-0000000-F7A20F | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2004-0230 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2005-3660 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2007-3719 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2008-2544 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2008-4609 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2010-4563 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2010-5321 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2011-4915 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2011-4916 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2011-4917 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2012-4542 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2014-9892 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2014-9900 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2015-2877 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2016-10723 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2016-8660 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2017-0630 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2017-13693 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2017-13694 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2018-1121 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2018-12928 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2018-17977 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-11191 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12378 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12379 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12380 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12381 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12382 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12455 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12456 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16229 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16230 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16231 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16232 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16233 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16234 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-19070 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-19378 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2020-11725 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2020-35501 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2021-26934 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2021-3714 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-0400 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-1247 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-25265 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-2961 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-3238 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-41848 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-44032 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-44033 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-4543 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-45884 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-45885 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-23039 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-26242 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-31081 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-31085 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-3640 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2024-0564 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2025-40025 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2025-68751 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-31536 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-74560 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-89862 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-90211 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-90261 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-90306 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-92493 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98285 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98289 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98304 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98317 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98321 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98332 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98338 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98389 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98393 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98424 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98427 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98431 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98436 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98551 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98628 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98802 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98874 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98929 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98951 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98966 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99348 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99349 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99376 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99381 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99382 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99496 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99569 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99575 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99579 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99594 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99599 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99607 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99610 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99615 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99622 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99628 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99689 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99704 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99711 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99723 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99741 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99759 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99778 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99779 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | TEMP-0000000-F7A20F | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2004-0230 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2005-3660 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2007-3719 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2008-2544 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2008-4609 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2010-4563 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2010-5321 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2011-4915 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2011-4916 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2011-4917 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2012-4542 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2014-9892 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2014-9900 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2015-2877 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2016-10723 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2016-8660 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2017-0630 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2017-13693 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2017-13694 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2018-1121 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2018-12928 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2018-17977 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-11191 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12378 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12379 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12380 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12381 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12382 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12455 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12456 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16229 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16230 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16231 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16232 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16233 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16234 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-19070 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-19378 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2020-11725 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2020-35501 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2021-26934 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2021-3714 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-0400 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-1247 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-25265 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-2961 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-3238 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-41848 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-44032 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-44033 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-4543 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-45884 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-45885 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-23039 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-26242 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-31081 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-31085 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-3640 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2024-0564 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2025-40025 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2025-68751 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-31536 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-74560 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-89862 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-90211 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-90261 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-90306 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-92493 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98285 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98289 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98304 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98317 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98321 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98332 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98338 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98389 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98393 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98424 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98427 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98431 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98436 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98551 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98628 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98802 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98874 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98929 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98951 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98966 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99348 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99349 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99376 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99381 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99382 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99496 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99569 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99575 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99579 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99594 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99599 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99607 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99610 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99615 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99622 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99628 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99689 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99704 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99711 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99723 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99741 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99759 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99778 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99779 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | TEMP-0000000-F7A20F | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2004-0230 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2005-3660 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2007-3719 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2008-2544 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2008-4609 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2010-4563 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2010-5321 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2011-4915 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2011-4916 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2011-4917 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2012-4542 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2014-9892 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2014-9900 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2015-2877 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2016-10723 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2016-8660 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2017-0630 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2017-13693 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2017-13694 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2018-1121 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2018-12928 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2018-17977 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-11191 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12378 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12379 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12380 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12381 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12382 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12455 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12456 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16229 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16230 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16231 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16232 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16233 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16234 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-19070 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-19378 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2020-11725 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2020-35501 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2021-26934 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2021-3714 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-0400 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-1247 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-25265 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-2961 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-3238 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-41848 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-44032 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-44033 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-4543 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-45884 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-45885 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-23039 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-26242 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-31081 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-31085 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-3640 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2024-0564 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2025-40025 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2025-68751 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-31536 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-74560 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-89862 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-90211 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-90261 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-90306 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-92493 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98285 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98289 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98304 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98317 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98321 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98332 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98338 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98389 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98393 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98424 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98427 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98431 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98436 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98551 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98628 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98802 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98874 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98929 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98951 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98966 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99348 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99349 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99376 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99381 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99382 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99496 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99569 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99575 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99579 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99594 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99599 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99607 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99610 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99615 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99622 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99628 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99689 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99704 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99711 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99723 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99741 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99759 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99778 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99779 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | TEMP-0000000-F7A20F | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2004-0230 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2005-3660 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2007-3719 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2008-2544 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2008-4609 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2010-4563 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2010-5321 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2011-4915 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2011-4916 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2011-4917 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2012-4542 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2014-9892 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2014-9900 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2015-2877 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2016-10723 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2016-8660 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2017-0630 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2017-13693 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2017-13694 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2018-1121 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2018-12928 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2018-17977 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-11191 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12378 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12379 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12380 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12381 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12382 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12455 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12456 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16229 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16230 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16231 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16232 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16233 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16234 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-19070 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-19378 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2020-11725 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2020-35501 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2021-26934 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2021-3714 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-0400 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-1247 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-25265 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-2961 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-3238 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-41848 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-44032 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-44033 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-4543 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-45884 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-45885 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-23039 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-26242 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-31081 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-31085 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-3640 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2024-0564 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2025-40025 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2025-68751 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-31536 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-74560 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-89862 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-90211 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-90261 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-90306 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-92493 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98285 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98289 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98304 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98317 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98321 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98332 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98338 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98389 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98393 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98424 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98427 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98431 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98436 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98551 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98628 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98802 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98874 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98929 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98951 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98966 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99348 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99349 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99376 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99381 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99382 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99496 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99569 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99575 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99579 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99594 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99599 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99607 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99610 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99615 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99622 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99628 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99689 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99704 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99711 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99723 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99741 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99759 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99778 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99779 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | TEMP-0000000-F7A20F | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2004-0230 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2005-3660 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2007-3719 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2008-2544 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2008-4609 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2010-4563 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2010-5321 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2011-4915 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2011-4916 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2011-4917 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2012-4542 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2014-9892 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2014-9900 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2015-2877 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2016-10723 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2016-8660 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2017-0630 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2017-13693 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2017-13694 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2018-1121 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2018-12928 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2018-17977 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-11191 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12378 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12379 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12380 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12381 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12382 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12455 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12456 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16229 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16230 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16231 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16232 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16233 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16234 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-19070 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-19378 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2020-11725 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2020-35501 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2021-26934 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2021-3714 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-0400 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-1247 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-25265 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-2961 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-3238 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-41848 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-44032 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-44033 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-4543 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-45884 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-45885 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-23039 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-26242 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-31081 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-31085 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-3640 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2024-0564 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2025-40025 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2025-68751 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-31536 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-74560 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-89862 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-90211 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-90261 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-90306 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-92493 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98285 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98289 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98304 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98317 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98321 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98332 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98338 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98389 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98393 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98424 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98427 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98431 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98436 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98551 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98628 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98802 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98874 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98929 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98951 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98966 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99348 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99349 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99376 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99381 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99382 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99496 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99569 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99575 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99579 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99594 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99599 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99607 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99610 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99615 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99622 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99628 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99689 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99704 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99711 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99723 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99741 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99759 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99778 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99779 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | TEMP-0000000-F7A20F | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2004-0230 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2005-3660 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2007-3719 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2008-2544 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2008-4609 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2010-4563 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2010-5321 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2011-4915 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2011-4916 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2011-4917 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2012-4542 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2014-9892 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2014-9900 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2015-2877 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2016-10723 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2016-8660 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2017-0630 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2017-13693 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2017-13694 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2018-1121 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2018-12928 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2018-17977 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-11191 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12378 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12379 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12380 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12381 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12382 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12455 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12456 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16229 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16230 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16231 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16232 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16233 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16234 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-19070 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-19378 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2020-11725 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2020-35501 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2021-26934 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2021-3714 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-0400 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-1247 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-25265 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-2961 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-3238 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-41848 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-44032 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-44033 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-4543 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-45884 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-45885 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-23039 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-26242 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-31081 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-31085 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-3640 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2024-0564 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2025-40025 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2025-68751 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-31536 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-74560 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-89862 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-90211 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-90261 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-90306 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-92493 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98285 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98289 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98304 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98317 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98321 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98332 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98338 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98389 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98393 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98424 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98427 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98431 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98436 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98551 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98628 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98802 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98874 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98929 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98951 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98966 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99348 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99349 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99376 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99381 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99382 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99496 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99569 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99575 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99579 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99594 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99599 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99607 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99610 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99615 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99622 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99628 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99689 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99704 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99711 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99723 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99741 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99759 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99778 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99779 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | TEMP-0000000-F7A20F | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2004-0230 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2005-3660 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2007-3719 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2008-2544 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2008-4609 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2010-4563 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2010-5321 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2011-4915 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2011-4916 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2011-4917 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2012-4542 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2014-9892 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2014-9900 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2015-2877 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2016-10723 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2016-8660 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2017-0630 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2017-13693 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2017-13694 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2018-1121 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2018-12928 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2018-17977 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-11191 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12378 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12379 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12380 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12381 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12382 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12455 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12456 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16229 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16230 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16231 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16232 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16233 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16234 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-19070 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-19378 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2020-11725 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2020-35501 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2021-26934 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2021-3714 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-0400 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-1247 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-25265 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-2961 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-3238 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-41848 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-44032 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-44033 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-4543 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-45884 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-45885 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-23039 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-26242 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-31081 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-31085 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-3640 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2024-0564 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2025-40025 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2025-68751 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-31536 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-74560 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-89862 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-90211 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-90261 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-90306 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-92493 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98285 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98289 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98304 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98317 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98321 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98332 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98338 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98389 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98393 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98424 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98427 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98431 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98436 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98551 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98628 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98802 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98874 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98929 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98951 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98966 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99348 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99349 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99376 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99381 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99382 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99496 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99569 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99575 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99579 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99594 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99599 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99607 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99610 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99615 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99622 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99628 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99689 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99704 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99711 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99723 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99741 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99759 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99778 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99779 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | TEMP-0000000-F7A20F | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2004-0230 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2005-3660 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2007-3719 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2008-2544 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2008-4609 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2010-4563 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2010-5321 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2011-4915 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2011-4916 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2011-4917 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2012-4542 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2014-9892 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2014-9900 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2015-2877 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2016-10723 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2016-8660 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2017-0630 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2017-13693 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2017-13694 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2018-1121 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2018-12928 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2018-17977 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-11191 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12378 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12379 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12380 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12381 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12382 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12455 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12456 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16229 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16230 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16231 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16232 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16233 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16234 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-19070 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-19378 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2020-11725 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2020-35501 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2021-26934 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2021-3714 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-0400 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-1247 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-25265 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-2961 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-3238 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-41848 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-44032 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-44033 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-4543 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-45884 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-45885 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-23039 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-26242 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-31081 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-31085 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-3640 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2024-0564 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2025-40025 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2025-68751 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-31536 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-74560 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-89862 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-90211 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-90261 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-90306 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-92493 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98285 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98289 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98304 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98317 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98321 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98332 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98338 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98389 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98393 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98424 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98427 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98431 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98436 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98551 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98628 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98802 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98874 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98929 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98951 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98966 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99348 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99349 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99376 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99381 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99382 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99496 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99569 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99575 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99579 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99594 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99599 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99607 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99610 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99615 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99622 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99628 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99689 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99704 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99711 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99723 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99741 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99759 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99778 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99779 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | TEMP-0000000-F7A20F | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2004-0230 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2005-3660 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2007-3719 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2008-2544 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2008-4609 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2010-4563 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2010-5321 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2011-4915 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2011-4916 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2011-4917 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2012-4542 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2014-9892 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2014-9900 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2015-2877 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2016-10723 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2016-8660 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2017-0630 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2017-13693 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2017-13694 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2018-1121 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2018-12928 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2018-17977 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-11191 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12378 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12379 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12380 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12381 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12382 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12455 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12456 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16229 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16230 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16231 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16232 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16233 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16234 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-19070 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-19378 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2020-11725 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2020-35501 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2021-26934 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2021-3714 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-0400 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-1247 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-25265 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-2961 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-3238 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-41848 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-44032 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-44033 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-4543 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-45884 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-45885 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-23039 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-26242 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-31081 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-31085 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-3640 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2024-0564 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2025-40025 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2025-68751 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-31536 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-74560 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-89862 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-90211 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-90261 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-90306 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-92493 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98285 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98289 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98304 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98317 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98321 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98332 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98338 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98389 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98393 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98424 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98427 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98431 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98436 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98551 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98628 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98802 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98874 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98929 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98951 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98966 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99348 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99349 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99376 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99381 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99382 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99496 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99569 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99575 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99579 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99594 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99599 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99607 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99610 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99615 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99622 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99628 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99689 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99704 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99711 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99723 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99741 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99759 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99778 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99779 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | TEMP-0000000-F7A20F | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2004-0230 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2005-3660 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2007-3719 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2008-2544 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2008-4609 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2010-4563 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2010-5321 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2011-4915 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2011-4916 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2011-4917 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2012-4542 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2014-9892 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2014-9900 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2015-2877 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2016-10723 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2016-8660 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2017-0630 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2017-13693 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2017-13694 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2018-1121 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2018-12928 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2018-17977 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-11191 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12378 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12379 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12380 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12381 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12382 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12455 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12456 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16229 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16230 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16231 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16232 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16233 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16234 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-19070 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-19378 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2020-11725 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2020-35501 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2021-26934 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2021-3714 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-0400 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-1247 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-25265 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-2961 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-3238 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-41848 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-44032 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-44033 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-4543 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-45884 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-45885 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-23039 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-26242 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-31081 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-31085 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-3640 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2024-0564 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2025-40025 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2025-68751 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-31536 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-74560 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-89862 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-90211 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-90261 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-90306 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-92493 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98285 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98289 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98304 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98317 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98321 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98332 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98338 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98389 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98393 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98424 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98427 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98431 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98436 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98551 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98628 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98802 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98874 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98929 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98951 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98966 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99348 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99349 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99376 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99381 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99382 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99496 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99569 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99575 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99579 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99594 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99599 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99607 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99610 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99615 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99622 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99628 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99689 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99704 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99711 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99723 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99741 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99759 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99778 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99779 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | TEMP-0000000-F7A20F | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2004-0230 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2005-3660 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2007-3719 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2008-2544 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2008-4609 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2010-4563 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2010-5321 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2011-4915 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2011-4916 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2011-4917 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2012-4542 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2014-9892 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2014-9900 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2015-2877 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2016-10723 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2016-8660 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2017-0630 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2017-13693 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2017-13694 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2018-1121 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2018-12928 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2018-17977 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-11191 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12378 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12379 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12380 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12381 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12382 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12455 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12456 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16229 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16230 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16231 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16232 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16233 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16234 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-19070 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-19378 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2020-11725 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2020-35501 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2021-26934 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2021-3714 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-0400 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-1247 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-25265 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-2961 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-3238 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-41848 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-44032 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-44033 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-4543 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-45884 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-45885 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-23039 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-26242 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-31081 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-31085 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-3640 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2024-0564 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2025-40025 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2025-68751 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-31536 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-74560 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-89862 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-90211 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-90261 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-90306 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-92493 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98285 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98289 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98304 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98317 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98321 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98332 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98338 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98389 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98393 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98424 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98427 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98431 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98436 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98551 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98628 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98802 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98874 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98929 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98951 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98966 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99348 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99349 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99376 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99381 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99382 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99496 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99569 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99575 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99579 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99594 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99599 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99607 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99610 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99615 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99622 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99628 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99689 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99704 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99711 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99723 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99741 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99759 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99778 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99779 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | TEMP-0000000-F7A20F | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2004-0230 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2005-3660 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2007-3719 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2008-2544 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2008-4609 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2010-4563 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2010-5321 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2011-4915 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2011-4916 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2011-4917 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2012-4542 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2014-9892 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2014-9900 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2015-2877 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2016-10723 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2016-8660 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2017-0630 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2017-13693 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2017-13694 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2018-1121 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2018-12928 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2018-17977 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-11191 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12378 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12379 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12380 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12381 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12382 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12455 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-12456 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16229 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16230 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16231 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16232 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16233 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-16234 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-19070 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2019-19378 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2020-11725 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2020-35501 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2021-26934 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2021-3714 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-0400 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-1247 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-25265 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-2961 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-3238 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-41848 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-44032 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-44033 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-4543 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-45884 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2022-45885 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-23039 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-26242 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-31081 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-31085 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2023-3640 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2024-0564 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2025-40025 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2025-68751 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-31536 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-74560 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-89862 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-90211 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-90261 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-90306 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-92493 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98285 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98289 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98304 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98317 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98321 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98332 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98338 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98389 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98393 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98424 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98427 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98431 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98436 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98551 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98628 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98802 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98874 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98929 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98951 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-98966 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99348 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99349 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99376 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99381 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99382 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99496 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99569 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99575 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99579 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99594 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99599 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99607 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99610 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99615 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99622 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99628 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99689 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99704 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99711 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99723 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99741 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99759 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99778 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-99779 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | TEMP-0000000-F7A20F | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2010-4756 | locales | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2018-20796 | locales | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2019-1010022 | locales | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2019-1010023 | locales | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2019-1010024 | locales | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2019-1010025 | locales | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2019-9192 | locales | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-100290 | locales | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2026-126765 | locales | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Low | CVE-2022-0563 | login | 1:4.16.0-2+really2.41-5 | No fix yet | Per policy |
| Low | CVE-2025-14104 | login | 1:4.16.0-2+really2.41-5 | 2.41.3-1 | Per policy |
| Low | CVE-2007-5686 | login.defs | 1:4.17.4-2 | No fix yet | Per policy |
| Low | CVE-2024-56433 | login.defs | 1:4.17.4-2 | No fix yet | Per policy |
| Low | TEMP-0628843-DBAD28 | login.defs | 1:4.17.4-2 | No fix yet | Per policy |
| Low | CVE-2022-0563 | mount | 2.41-5 | No fix yet | Per policy |
| Low | CVE-2025-14104 | mount | 2.41-5 | 2.41.3-1 | Per policy |
| Low | CVE-2025-6141 | ncurses-base | 6.5+20250216-2 | No fix yet | Per policy |
| Low | CVE-2025-6141 | ncurses-bin | 6.5+20250216-2 | No fix yet | Per policy |
| Low | CVE-2025-6141 | ncurses-term | 6.5+20250216-2 | No fix yet | Per policy |
| Low | CVE-2002-1976 | net-tools | 2.10-1.3 | No fix yet | Per policy |
| Low | CVE-2025-9615 | network-manager | 1.52.1-1+rpt4 | No fix yet | Per policy |
| Low | CVE-2025-9615 | network-manager-l10n | 1.52.1-1+rpt4 | No fix yet | Per policy |
| Low | CVE-2007-2243 | openssh-client | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2007-2768 | openssh-client | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2008-3234 | openssh-client | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2016-20012 | openssh-client | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2018-15919 | openssh-client | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2019-6110 | openssh-client | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2020-14145 | openssh-client | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2020-15778 | openssh-client | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2026-106582 | openssh-client | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2026-106584 | openssh-client | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2026-106587 | openssh-client | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2026-123158 | openssh-client | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2026-55654 | openssh-client | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2026-73281 | openssh-client | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2007-2243 | openssh-server | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2007-2768 | openssh-server | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2008-3234 | openssh-server | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2016-20012 | openssh-server | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2018-15919 | openssh-server | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2019-6110 | openssh-server | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2020-14145 | openssh-server | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2020-15778 | openssh-server | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2026-106582 | openssh-server | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2026-106584 | openssh-server | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2026-106587 | openssh-server | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2026-123158 | openssh-server | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2026-55654 | openssh-server | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2026-73281 | openssh-server | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2007-2243 | openssh-sftp-server | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2007-2768 | openssh-sftp-server | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2008-3234 | openssh-sftp-server | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2016-20012 | openssh-sftp-server | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2018-15919 | openssh-sftp-server | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2019-6110 | openssh-sftp-server | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2020-14145 | openssh-sftp-server | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2020-15778 | openssh-sftp-server | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2026-106582 | openssh-sftp-server | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2026-106584 | openssh-sftp-server | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2026-106587 | openssh-sftp-server | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2026-123158 | openssh-sftp-server | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2026-55654 | openssh-sftp-server | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2026-73281 | openssh-sftp-server | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2026-107493 | openssl | 3.5.6-1~deb13u2+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-121481 | openssl | 3.5.6-1~deb13u2+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-14457 | openssl | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u2 | Per policy |
| Low | CVE-2026-35189 | openssl | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u3 | Per policy |
| Low | CVE-2026-35191 | openssl | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u3 | Per policy |
| Low | CVE-2026-54874 | openssl | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u2 | Per policy |
| Low | CVE-2026-63073 | openssl | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u2 | Per policy |
| Low | CVE-2026-63074 | openssl | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u2 | Per policy |
| Low | CVE-2026-63075 | openssl | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u2 | Per policy |
| Low | CVE-2026-75803 | openssl | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u2 | Per policy |
| Low | CVE-2026-88822 | openssl | 3.5.6-1~deb13u2+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-88823 | openssl | 3.5.6-1~deb13u2+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-107493 | openssl-provider-legacy | 3.5.6-1~deb13u2+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-121481 | openssl-provider-legacy | 3.5.6-1~deb13u2+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-14457 | openssl-provider-legacy | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u2 | Per policy |
| Low | CVE-2026-35189 | openssl-provider-legacy | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u3 | Per policy |
| Low | CVE-2026-35191 | openssl-provider-legacy | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u3 | Per policy |
| Low | CVE-2026-54874 | openssl-provider-legacy | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u2 | Per policy |
| Low | CVE-2026-63073 | openssl-provider-legacy | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u2 | Per policy |
| Low | CVE-2026-63074 | openssl-provider-legacy | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u2 | Per policy |
| Low | CVE-2026-63075 | openssl-provider-legacy | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u2 | Per policy |
| Low | CVE-2026-75803 | openssl-provider-legacy | 3.5.6-1~deb13u2+rpt1 | 3.5.7-1~deb13u2 | Per policy |
| Low | CVE-2026-88822 | openssl-provider-legacy | 3.5.6-1~deb13u2+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-88823 | openssl-provider-legacy | 3.5.6-1~deb13u2+rpt1 | No fix yet | Per policy |
| Low | CVE-2007-5686 | passwd | 1:4.17.4-2 | No fix yet | Per policy |
| Low | CVE-2024-56433 | passwd | 1:4.17.4-2 | No fix yet | Per policy |
| Low | TEMP-0628843-DBAD28 | passwd | 1:4.17.4-2 | No fix yet | Per policy |
| Low | CVE-2010-4651 | patch | 2.8-2 | No fix yet | Per policy |
| Low | CVE-2018-6951 | patch | 2.8-2 | No fix yet | Per policy |
| Low | CVE-2018-6952 | patch | 2.8-2 | No fix yet | Per policy |
| Low | CVE-2021-45261 | patch | 2.8-2 | No fix yet | Per policy |
| Low | CVE-2026-56288 | patch | 2.8-2 | No fix yet | Per policy |
| Low | CVE-2026-56289 | patch | 2.8-2 | No fix yet | Per policy |
| Low | CVE-2011-4116 | perl | 5.40.1-6 | No fix yet | Per policy |
| Low | CVE-2011-4116 | perl-base | 5.40.1-6 | No fix yet | Per policy |
| Low | CVE-2011-4116 | perl-modules-5.40 | 5.40.1-6 | No fix yet | Per policy |
| Low | CVE-2025-7519 | polkitd | 126-2 | No fix yet | Per policy |
| Low | CVE-2008-5366 | ppp | 2.5.2-1+1 | No fix yet | Per policy |
| Low | CVE-2008-5367 | ppp | 2.5.2-1+1 | No fix yet | Per policy |
| Low | CVE-2026-112300 | python3-configobj | 5.0.9-1 | No fix yet | Per policy |
| Low | CVE-2019-8341 | python3-jinja2 | 3.1.6-1 | No fix yet | Per policy |
| Low | CVE-2025-45768 | python3-jwt | 2.10.1-2+deb13u1 | No fix yet | Per policy |
| Low | CVE-2026-1703 | python3-pip-whl | 25.1.1+dfsg-1+rpt1 | No fix yet | Per policy |
| Low | CVE-2026-4539 | python3-pygments | 2.18.0+dfsg-2 | 2.18.0+dfsg-2+deb13u1 | Per policy |
| Low | CVE-2026-115557 | python3.13 | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Low | CVE-2026-115559 | python3.13 | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Low | CVE-2026-12003 | python3.13 | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Low | CVE-2026-18503 | python3.13 | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Low | CVE-2026-3479 | python3.13 | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Low | CVE-2026-6879 | python3.13 | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u5 | Per policy |
| Low | CVE-2026-115557 | python3.13-minimal | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Low | CVE-2026-115559 | python3.13-minimal | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Low | CVE-2026-12003 | python3.13-minimal | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Low | CVE-2026-18503 | python3.13-minimal | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Low | CVE-2026-3479 | python3.13-minimal | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Low | CVE-2026-6879 | python3.13-minimal | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u5 | Per policy |
| Low | CVE-2026-115557 | python3.13-venv | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Low | CVE-2026-115559 | python3.13-venv | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Low | CVE-2026-12003 | python3.13-venv | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Low | CVE-2026-18503 | python3.13-venv | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Low | CVE-2026-3479 | python3.13-venv | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Low | CVE-2026-6879 | python3.13-venv | 3.13.5-2+deb13u2 | 3.13.5-2+deb13u5 | Per policy |
| Low | CVE-2022-0563 | rfkill | 2.41-5 | No fix yet | Per policy |
| Low | CVE-2025-14104 | rfkill | 2.41-5 | 2.41.3-1 | Per policy |
| Low | CVE-2026-45232 | rsync | 3.4.1+ds1-5+deb13u3 | 3.4.1+ds1-5+deb13u4 | Per policy |
| Low | CVE-2007-2243 | ssh | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2007-2768 | ssh | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2008-3234 | ssh | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2016-20012 | ssh | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2018-15919 | ssh | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2019-6110 | ssh | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2020-14145 | ssh | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2020-15778 | ssh | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2026-106582 | ssh | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2026-106584 | ssh | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2026-106587 | ssh | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2026-123158 | ssh | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2026-55654 | ssh | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2026-73281 | ssh | 1:10.0p1-7+deb13u4 | No fix yet | Per policy |
| Low | CVE-2005-1119 | sudo | 1.9.16p2-3+deb13u2 | No fix yet | Per policy |
| Low | CVE-2026-82474 | sudo | 1.9.16p2-3+deb13u2 | No fix yet | Per policy |
| Low | CVE-2013-4392 | systemd | 257.13-1~deb13u1 | No fix yet | Per policy |
| Low | CVE-2023-31437 | systemd | 257.13-1~deb13u1 | No fix yet | Per policy |
| Low | CVE-2023-31438 | systemd | 257.13-1~deb13u1 | No fix yet | Per policy |
| Low | CVE-2023-31439 | systemd | 257.13-1~deb13u1 | No fix yet | Per policy |
| Low | CVE-2026-40228 | systemd | 257.13-1~deb13u1 | No fix yet | Per policy |
| Low | CVE-2013-4392 | systemd-sysv | 257.13-1~deb13u1 | No fix yet | Per policy |
| Low | CVE-2023-31437 | systemd-sysv | 257.13-1~deb13u1 | No fix yet | Per policy |
| Low | CVE-2023-31438 | systemd-sysv | 257.13-1~deb13u1 | No fix yet | Per policy |
| Low | CVE-2023-31439 | systemd-sysv | 257.13-1~deb13u1 | No fix yet | Per policy |
| Low | CVE-2026-40228 | systemd-sysv | 257.13-1~deb13u1 | No fix yet | Per policy |
| Low | CVE-2013-4392 | systemd-timesyncd | 257.13-1~deb13u1 | No fix yet | Per policy |
| Low | CVE-2023-31437 | systemd-timesyncd | 257.13-1~deb13u1 | No fix yet | Per policy |
| Low | CVE-2023-31438 | systemd-timesyncd | 257.13-1~deb13u1 | No fix yet | Per policy |
| Low | CVE-2023-31439 | systemd-timesyncd | 257.13-1~deb13u1 | No fix yet | Per policy |
| Low | CVE-2026-40228 | systemd-timesyncd | 257.13-1~deb13u1 | No fix yet | Per policy |
| Low | TEMP-0517018-A83CE6 | sysvinit-utils | 3.14-4 | No fix yet | Per policy |
| Low | CVE-2005-2541 | tar | 1.35+dfsg-3.1 | No fix yet | Per policy |
| Low | TEMP-0290435-0B57B5 | tar | 1.35+dfsg-3.1 | No fix yet | Per policy |
| Low | CVE-2013-4392 | udev | 257.13-1~deb13u1 | No fix yet | Per policy |
| Low | CVE-2023-31437 | udev | 257.13-1~deb13u1 | No fix yet | Per policy |
| Low | CVE-2023-31438 | udev | 257.13-1~deb13u1 | No fix yet | Per policy |
| Low | CVE-2023-31439 | udev | 257.13-1~deb13u1 | No fix yet | Per policy |
| Low | CVE-2026-40228 | udev | 257.13-1~deb13u1 | No fix yet | Per policy |
| Low | CVE-2021-4217 | unzip | 6.0-29 | No fix yet | Per policy |
| Low | TEMP-1142904-117334 | unzip | 6.0-29 | 6.0-29+deb13u1 | Per policy |
| Low | TEMP-1142905-081994 | unzip | 6.0-29 | 6.0-29+deb13u1 | Per policy |
| Low | CVE-2022-0563 | util-linux | 2.41-5 | No fix yet | Per policy |
| Low | CVE-2025-14104 | util-linux | 2.41-5 | 2.41.3-1 | Per policy |
| Low | CVE-2008-4677 | vim-common | 2:9.1.1230-2 | No fix yet | Per policy |
| Low | CVE-2017-1000382 | vim-common | 2:9.1.1230-2 | No fix yet | Per policy |
| Low | CVE-2026-28422 | vim-common | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | Per policy |
| Low | CVE-2008-4677 | vim-tiny | 2:9.1.1230-2 | No fix yet | Per policy |
| Low | CVE-2017-1000382 | vim-tiny | 2:9.1.1230-2 | No fix yet | Per policy |
| Low | CVE-2026-28422 | vim-tiny | 2:9.1.1230-2 | 2:9.1.1230-2+deb13u1 | Per policy |
| Low | CVE-2026-16599 | wget | 1.25.0-2 | No fix yet | Per policy |
| Low | CVE-2017-13084 | wpasupplicant | 2:2.10-24 | No fix yet | Per policy |
| Low | CVE-2019-5062 | wpasupplicant | 2:2.10-24 | No fix yet | Per policy |
| Low | CVE-2017-15131 | xdg-user-dirs | 0.18-2 | No fix yet | Per policy |
| Low | CVE-2026-56857 | stdlib | 1.26.4 | 1.26.9, 1.27.2 | Per policy |
| Low | CVE-2024-12797 | cryptography | 43.0.0 | 44.0.1 | Per policy |
| Low | CVE-2026-34073 | cryptography | 43.0.0 | 46.0.6 | Per policy |
| Low | CVE-2026-1703 | pip | 25.1.1 | 26.0 | Per policy |
| Low | CVE-2026-4539 | pygments | 2.18.0 | 2.20.0 | Per policy |
| Low | CVE-2026-48524 | pyjwt | 2.10.1 | 2.13.0 | Per policy |
| Low | GHSA-xmj3-9gf7-h52w | setuptools | 78.1.1 | 84.1.0 | Per policy |
| Low | CVE-2018-6559 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Low | CVE-2022-3619 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Low | CVE-2022-3624 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Low | CVE-2022-3629 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Low | CVE-2022-3630 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Low | CVE-2022-3633 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Low | CVE-2022-3646 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Low | CVE-2023-1075 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Low | CVE-2026-63895 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Low | CVE-2026-64479 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Low | CVE-2026-64494 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Low | CVE-2026-64497 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Low | CVE-2026-64499 | linux_kernel | 6.18.34 | No fix yet | Per policy |
| Unknown | CVE-2026-125742 | 7zip | 25.01+dfsg-1~deb13u2 | No fix yet | Per policy |
| Unknown | CVE-2026-130067 | 7zip | 25.01+dfsg-1~deb13u2 | No fix yet | Per policy |
| Unknown | CVE-2026-48112 | 7zip | 25.01+dfsg-1~deb13u2 | No fix yet | Per policy |
| Unknown | TEMP-1153844-83400A | dbus | 1.16.2-2 | No fix yet | Per policy |
| Unknown | TEMP-1153844-83400A | dbus-bin | 1.16.2-2 | No fix yet | Per policy |
| Unknown | TEMP-1153844-83400A | dbus-daemon | 1.16.2-2 | No fix yet | Per policy |
| Unknown | TEMP-1153844-83400A | dbus-session-bus-common | 1.16.2-2 | No fix yet | Per policy |
| Unknown | TEMP-1153844-83400A | dbus-system-bus-common | 1.16.2-2 | No fix yet | Per policy |
| Unknown | TEMP-1153844-83400A | dbus-user-session | 1.16.2-2 | No fix yet | Per policy |
| Unknown | CVE-2026-91094 | dpkg | 1.22.22 | No fix yet | Per policy |
| Unknown | CVE-2026-91094 | dpkg-dev | 1.22.22 | No fix yet | Per policy |
| Unknown | CVE-2025-32735 | firmware-atheros | 1:20250410-2+rpt1 | No fix yet | Per policy |
| Unknown | CVE-2026-40426 | firmware-atheros | 1:20250410-2+rpt1 | No fix yet | Per policy |
| Unknown | CVE-2025-32735 | firmware-brcm80211 | 1:20250410-2+rpt1 | No fix yet | Per policy |
| Unknown | CVE-2026-40426 | firmware-brcm80211 | 1:20250410-2+rpt1 | No fix yet | Per policy |
| Unknown | CVE-2025-32735 | firmware-libertas | 1:20250410-2+rpt1 | No fix yet | Per policy |
| Unknown | CVE-2026-40426 | firmware-libertas | 1:20250410-2+rpt1 | No fix yet | Per policy |
| Unknown | CVE-2025-32735 | firmware-mediatek | 1:20250410-2+rpt1 | No fix yet | Per policy |
| Unknown | CVE-2026-40426 | firmware-mediatek | 1:20250410-2+rpt1 | No fix yet | Per policy |
| Unknown | CVE-2025-32735 | firmware-realtek | 1:20250410-2+rpt1 | No fix yet | Per policy |
| Unknown | CVE-2026-40426 | firmware-realtek | 1:20250410-2+rpt1 | No fix yet | Per policy |
| Unknown | TEMP-0000000-096B8D | groff-base | 1.23.0-9 | No fix yet | Per policy |
| Unknown | CVE-2026-121757 | libc-bin | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Unknown | CVE-2026-121758 | libc-bin | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Unknown | CVE-2026-124024 | libc-bin | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Unknown | CVE-2026-121757 | libc-dev-bin | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Unknown | CVE-2026-121758 | libc-dev-bin | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Unknown | CVE-2026-124024 | libc-dev-bin | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Unknown | CVE-2026-121757 | libc-l10n | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Unknown | CVE-2026-121758 | libc-l10n | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Unknown | CVE-2026-124024 | libc-l10n | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Unknown | CVE-2026-121757 | libc6 | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Unknown | CVE-2026-121758 | libc6 | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Unknown | CVE-2026-124024 | libc6 | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Unknown | CVE-2026-121757 | libc6-dev | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Unknown | CVE-2026-121758 | libc6-dev | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Unknown | CVE-2026-124024 | libc6-dev | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Unknown | TEMP-1153844-83400A | libdbus-1-3 | 1.16.2-2 | No fix yet | Per policy |
| Unknown | CVE-2026-91094 | libdpkg-perl | 1.22.22 | No fix yet | Per policy |
| Unknown | CVE-2026-124317 | libexpat1 | 2.7.1-2 | No fix yet | Per policy |
| Unknown | CVE-2026-128241 | libexpat1 | 2.7.1-2 | No fix yet | Per policy |
| Unknown | CVE-2026-127039 | libgnutls30t64 | 3.8.9-3+deb13u4 | No fix yet | Per policy |
| Unknown | CVE-2026-127040 | libgnutls30t64 | 3.8.9-3+deb13u4 | No fix yet | Per policy |
| Unknown | CVE-2026-127231 | libgnutls30t64 | 3.8.9-3+deb13u4 | No fix yet | Per policy |
| Unknown | CVE-2026-129975 | libgpgme11t64 | 1.24.2-3 | 1.24.2-3+deb13u1 | Per policy |
| Unknown | TEMP-1147318-639065 | liblzma5 | 5.8.1-1 | 5.8.1-1+deb13u2 | Per policy |
| Unknown | TEMP-0000000-001B0E | libntfs-3g89t64 | 1:2022.10.3-5+deb13u1 | 1:2022.10.3-5+deb13u3 | Per policy |
| Unknown | TEMP-0000000-17A9B4 | libntfs-3g89t64 | 1:2022.10.3-5+deb13u1 | 1:2022.10.3-5+deb13u3 | Per policy |
| Unknown | TEMP-0000000-37DA2F | libntfs-3g89t64 | 1:2022.10.3-5+deb13u1 | 1:2022.10.3-5+deb13u3 | Per policy |
| Unknown | TEMP-0000000-52FEFD | libntfs-3g89t64 | 1:2022.10.3-5+deb13u1 | 1:2022.10.3-5+deb13u3 | Per policy |
| Unknown | TEMP-0000000-575F54 | libntfs-3g89t64 | 1:2022.10.3-5+deb13u1 | 1:2022.10.3-5+deb13u3 | Per policy |
| Unknown | TEMP-0000000-724ECC | libntfs-3g89t64 | 1:2022.10.3-5+deb13u1 | 1:2022.10.3-5+deb13u3 | Per policy |
| Unknown | TEMP-0000000-B9374C | libntfs-3g89t64 | 1:2022.10.3-5+deb13u1 | 1:2022.10.3-5+deb13u3 | Per policy |
| Unknown | TEMP-0000000-D7723D | libntfs-3g89t64 | 1:2022.10.3-5+deb13u1 | 1:2022.10.3-5+deb13u3 | Per policy |
| Unknown | CVE-2026-115791 | libpython3.13 | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Unknown | CVE-2026-19552 | libpython3.13 | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Unknown | CVE-2026-115791 | libpython3.13-minimal | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Unknown | CVE-2026-19552 | libpython3.13-minimal | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Unknown | CVE-2026-115791 | libpython3.13-stdlib | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Unknown | CVE-2026-19552 | libpython3.13-stdlib | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Unknown | CVE-2026-99782 | linux-base-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Unknown | CVE-2026-99782 | linux-base-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Unknown | CVE-2026-99782 | linux-base-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Unknown | CVE-2026-99782 | linux-base-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Unknown | CVE-2026-99782 | linux-headers-6.18.34+rpt-common-rpi | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Unknown | CVE-2026-99782 | linux-headers-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Unknown | CVE-2026-99782 | linux-headers-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Unknown | CVE-2026-99782 | linux-headers-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Unknown | CVE-2026-99782 | linux-headers-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Unknown | CVE-2026-99782 | linux-image-6.18.34+rpt-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Unknown | CVE-2026-99782 | linux-image-6.18.34+rpt-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Unknown | CVE-2026-99782 | linux-image-rpi-2712 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Unknown | CVE-2026-99782 | linux-image-rpi-v8 | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Unknown | CVE-2026-99782 | linux-kbuild-6.18.34+rpt | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Unknown | CVE-2026-99782 | linux-libc-dev | 1:6.18.34-1+rpt1 | No fix yet | Per policy |
| Unknown | CVE-2026-121757 | locales | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Unknown | CVE-2026-121758 | locales | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Unknown | CVE-2026-124024 | locales | 2.41-12+rpt1+deb13u3 | No fix yet | Per policy |
| Unknown | TEMP-0000000-001B0E | ntfs-3g | 1:2022.10.3-5+deb13u1 | 1:2022.10.3-5+deb13u3 | Per policy |
| Unknown | TEMP-0000000-17A9B4 | ntfs-3g | 1:2022.10.3-5+deb13u1 | 1:2022.10.3-5+deb13u3 | Per policy |
| Unknown | TEMP-0000000-37DA2F | ntfs-3g | 1:2022.10.3-5+deb13u1 | 1:2022.10.3-5+deb13u3 | Per policy |
| Unknown | TEMP-0000000-52FEFD | ntfs-3g | 1:2022.10.3-5+deb13u1 | 1:2022.10.3-5+deb13u3 | Per policy |
| Unknown | TEMP-0000000-575F54 | ntfs-3g | 1:2022.10.3-5+deb13u1 | 1:2022.10.3-5+deb13u3 | Per policy |
| Unknown | TEMP-0000000-724ECC | ntfs-3g | 1:2022.10.3-5+deb13u1 | 1:2022.10.3-5+deb13u3 | Per policy |
| Unknown | TEMP-0000000-B9374C | ntfs-3g | 1:2022.10.3-5+deb13u1 | 1:2022.10.3-5+deb13u3 | Per policy |
| Unknown | TEMP-0000000-D7723D | ntfs-3g | 1:2022.10.3-5+deb13u1 | 1:2022.10.3-5+deb13u3 | Per policy |
| Unknown | CVE-2026-85495 | ppp | 2.5.2-1+1 | No fix yet | Per policy |
| Unknown | CVE-2026-115791 | python3.13 | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Unknown | CVE-2026-19552 | python3.13 | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Unknown | CVE-2026-115791 | python3.13-minimal | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Unknown | CVE-2026-19552 | python3.13-minimal | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Unknown | CVE-2026-115791 | python3.13-venv | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Unknown | CVE-2026-19552 | python3.13-venv | 3.13.5-2+deb13u2 | No fix yet | Per policy |
| Unknown | TEMP-1142906-2C6C79 | unzip | 6.0-29 | 6.0-29+deb13u1 | Per policy |
| Unknown | TEMP-1153750-98581D | unzip | 6.0-29 | No fix yet | Per policy |
| Unknown | TEMP-1148985-A50803 | wpasupplicant | 2:2.10-24 | No fix yet | Per policy |
| Unknown | TEMP-1147318-639065 | xz-utils | 5.8.1-1 | 5.8.1-1+deb13u2 | Per policy |
| Unknown | CVE-2026-130335 | zip | 3.0-15 | 3.0-15+deb13u1 | Per policy |
| Unknown | GO-2026-5932 | golang.org/x/crypto | v0.53.0 | 0.58.1-0.20261009181718-2f1f834330b2 | Per policy |
Distinct licenses identified: 397 (see the NOTICE artifact for details).
Licenses are what each package declares. A declaration can be missing or wrong, and this is not a legal determination.
Each component is also recorded in the SBOM with a bomlens:licenseClass property. An unrecognized license is left uncategorized rather than assumed permissive.
Components that create copyleft exposure (network/strong, up to 10)
2,276bomlens:licenseClass property for all)