Thank you for the reply.
The updates are present, i checked with "esxupdate -d ftp://... scan" from an esx host of the farm, ad it retrieves all the listed updates.
I've tryed to create and attach just a baseline with only ESX350-201105405-BG, but the scan fails with the same error.
(by the way this patch was not in the baseline i began with, when i had the problem. I had just put in the baseline the following patches
http://www.vmware.com/security/advisories/VMSA-2012-0003.html
ESX350-201203401-SG
http://www.vmware.com/security/advisories/VMSA-2012-0009.html
ESX350-201205401-SG
http://www.vmware.com/security/advisories/VMSA-2012-0011.html
ESX350-201206401-SG
http://www.vmware.com/security/advisories/VMSA-2011-0010.html
ESX350-201203405-SG
http://www.vmware.com/security/advisories/VMSA-2011-0012.html
ESX350-201203403-SG
)
I maybe will be able to install the updates via esxupdate command, but since i can't install them right now due to audit policy, i haven't a way to test this solution.
This occurred while i was testing the update infrastructure, planning the update for the next month.
How is it possible that there is a cyclic dependecy? Maybe it just appears to the update manager, that there is..