I think this is an example of following a design system component by component rather than looking at the whole interface design. It seems like you took two components and put them together and this is the result that you ended up with, which is usually what happens when you work with an existing design system to come up with designs.
However, you can see that there are also clear delineations between what one component does compared to the other. One is clearly associated with the top level navigation and therefore the user understands the context for the kebab icon, while the other is associated with the card and therefore would have other features.
Used at the top level, there are alternatives or variations to the kebab menu (What the difference between the 2 menu icons: 3-dots (kebab) and 3-lines (hamburger)) but used at the card component level there are other alternate icons and design patterns that you can use to hide or reveal additional features.
Depending on the design system that you adopt, adapt or extend, you might find that there are different possibilities that can work if you want to avoid this kind of potential confusion for the users (which you should test rather than assume). As designers we are probably too close to the design system to be able to tell, but it is good that you are identifying potential design issues to investigate and test.