For practical purposes, if you're implementing a many-to-many relationship with an intersection table - which is by far the most common way to do it, then you will in effect have a "zero or more to zero or more" relationship.
Relational databases don't have declarative referential constraints that enforce the child end of a one to many relationship. In other words, your
CAR table can't have a constraint (imposed by DRI) that enforces 0, 1 or many owners. DRI works on the table with the foreign key, not the parent (referenced) table.
This means that unless you implement some additional procedural logic in your application, you wouldn't be able to enforce 1 or more, so you in effect get 0, 1 or more to each of
PERSON from the intersection (
Implementing a many-to-many relationship in this way is consistent with correct normalization.