I’m experiencing a problem during routine security update upgrades. On devices running Rocky Linux 9.5, I want “dnf updateinfo list installed” to give me a list of security updates, and I want to pass the security updates on this list. I get the list and pass it, but when I run the “dnf updateinfo list installed” command again, I get the same output. I can’t figure out why. Here are the steps I followed:
1- dnf updateinfo list installed |grep Sec or dnf updateinfo list all |grep Sec
2- dnf update “packages in list”
3- reboot
4- dnf updateinfo list installed |grep Sec or dnf updateinfo list all |grep Sec
I expect the results to be different from the first step after performing these steps.
In Linux 8, I was able to pull and list updates with “dnf updateinfo list security” and run them with “dnf update --security.” However, I couldn’t do this in Linux 9.5. My goal is to list existing updates on the system, install them on the device, and then see the pending security updates section empty.
Rocky 9 (Code Name “Blue Onyx”) has general support until 31 May 2027 and security support through 31 May 2032. The supported architectures are x86_64-v2, aarch64, ppc64le, and s390x.
Yes, the major version (9) will have support, not all minor versions.
Minor releases add features during the general support phase.
Some security/bug fixes may be released for the current minor version until next minor version is released.
The security support phase will offer only critical security/bug fixes (for the last minor version).
Do you know the difference between the “dnf updateinfo list all” command and the “dnf updateinfo list security” command? dnf updateinfo list security
Last metadata expiration check: 1:02:16 ago on Tue 14 Oct 2025 12:50:18 PM +03.
dnf updateinfo list all
i RLSA-2023:0340 Moderate/Sec. bash-5.1.8-6.el9_1.x86_64
i RLSA-2023:4099 Important/Sec. bind-libs-2:9.16.23-11.el9_2.1.x86_64
i RLSA-2024:2551 Important/Sec. bind-libs-2:9.16.23-18.el9_4.1.x86_64
i RLSA-2024:5231 Important/Sec. bind-libs-2:9.16.23-18.el9_4.6.x86_64
I get two different outputs.
When I get to the case, since I performed a dnf up and all versions were updated on the client, I can’t check with the --security feature. It seems I can check again in a month or when a security update is released.
I’m running these as evidence. Our updates are being audited, and we need to provide evidence of why they were made and what was done. With dnf updateinfo list security
RLSA-2023:0340 Moderate/Sec. bash-5.1.8-6.el9_1.x86_64
RLSA-2023:4099 Important/Sec. bind-libs-2:9.16.23-11.el9_2.1.x86_64
RLSA-2024:2551 Important/Sec. bind-libs-2:9.16.23-18.el9_4.1.x86_64
RLSA-2024:5231 Important/Sec. bind-libs-2:9.16.23-18.el9_4.6.x86_64
I’m printing out the vulnerability and saying I’ll be pushing these updates to the device. Dnf up updates everything very well, but only until there’s a version that shouldn’t be updated
A version of package that is released but should not have been released ought to be a rare (preferably never) exception.
As general rule all updates to a major version of Enterprise Linux should alleviate issues, not create them. Be conservative. However, then one should know&document what to exclude and why (and let the rest update).