Fedora Account System
Red Hat Associate
Red Hat Customer
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.
I fail to understand how this can be related to NetworkManager. It seems to be a bug in systemd-machined. Abhishek, I am missing something?
(In reply to Íñigo Huguet from comment #1) > I fail to understand how this can be related to NetworkManager. It seems to > be a bug in systemd-machined. Abhishek, I am missing something? I guess it's because the spec file of NM contains: # NetworkManager uses various parts of systemd-networkd internally, including # DHCP client, IPv4 Link-Local address negotiation or LLDP support. # This provide is essentially here so that NetworkManager shows on Security # Response Team's radar in case a flaw is found. The code is frequently # synchronized and thus it's not easy to establish a good version number # here. The version of zero is there just to have something conservative so # that the scripts that would parse the SPEC file naively would be unlikely # to fail. Refer to git log for the real date and commit number of last # synchronization: # https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commits/main/src/ Provides: bundled(systemd) = 0 This specific vulnerability doesn't seem to impact NM.
If that's the reason, the I agree with Beniamino. The part of systemd that NM uses is only about DHCPv6. No code from machined is used.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 45 development cycle. Changing version to 45.