Virtual network warns about address overlap with itself

Azure warns about the address spaces of one virtual network overlapping with the address space of another (such networks cannot be peered). This makes sense.

However, I am noticing that Azure also warns me about the address space of a virtual network overlapping with itself:

Address space 10.2.0.0/16 overlaps with address space 10.2.0.0/16 of virtual network 'poboy_vnet'. [...]

There is only one poboy_vnet in my subscription.

Is this a bug?

P.S. Not sure but it is possible this only occurs with vnets that are peered with some other vnet.

Edit: Since @Imran mentioned address space overlap between different subnets of poboy_vnet as a possible reason, here is the subnet configuration. As far as I can tell there is no address space overlap:

This is a bug and has been resolved. You can navigate to https://ms.portal.azure.com/?feature.canmodifystamps=true&Microsoft_Azure_Network=flight4

This URL wont perm fix the issue but, if you need to peer a vnet, you can login with that URL temporarily to peer the vnets or manage the vnets until the fix is globally deployed, sometime next week.