Sorry, no examples, but maybe this can start the discussion.
Think about what "nonconforming product" means. The supplier delivered a product that doesn't conform to the consumer's needs or expectations. In the "normal" context, this could mean that you received something that you intended to use but it doesn't meet your specs *or* you delivered something that doesn't meet your receiver's specs.
All this applies to software. In the case where you received something that you intended to use but found it defective, there are 2 paths. This could be libraries or 'snap-on' components. First, if you have not deployed it you will either return it / get an update with fixes from the vendor or you will shop around and find a new vendor. You would ensure that the nonconforming software doesn't get into a production release via your CM procedures. Second, if you have deployed your software and you find that a bug is in the purchased part, you have an obligation to your customers to correct the problem (even though you didn't cause it, per se). This could be a patch, a workaround, or whatever. It may require extraordinary steps to ensure that corrections are actually deployed at the customer site if there is any risk of harm involved.
The other case means that you (supplier) have delivered software with a bug. Again, you have an obligation to control and correct that issue. So for example, if you have multiple clients and one reported the bug, you would be obligated to inform the other clients about the bug and any temporary measures needed to avoid it or avoid degradation in their quailty. This may include a recommendation to stop using the product completely pending correction. This may also require that you provide direction to the clients on dealing with previous results from using the system.
Hope that makes sense. I also hope to hear others' thoughts on the subject. It's a good subject to discuss since it does seem to fall in that gray area not well addressed by standards or regulations.